b6776 -> Eclipse import cannot import Ear modules

Ear modules are not listed in the projects to import, and clicking next produces an error, because modules try to reference a jar in the SomeServiceEar project. Get an alert and then stops without any action.

Was it supposed to work?

3 comments

Hello Andrew,

EAR modules are not yet supported, but IDEA should not produce an error when
seeing one. Can you give me more details? What is the exact wording of the
error message? If possible, can you send me Eclipse project files for your
EAR project?

Vladislav Kaznacheev
Project Manager, IntelliJ IDEA
http://www.jetbrains.com
"Develop with Pleasure!"

Ear modules are not listed in the projects to import, and clicking
next produces an error, because modules try to reference a jar in the
SomeServiceEar project. Get an alert and then stops without any
action.

Was it supposed to work?



0

Hey Vladislav,

I was away for a week, sorry for the delay. With the new 6799 build, the above problem is solved. And we get to the next one.

Now, the Ear modules are not displayed during the import process. The imports completes fine, though with one message about missing jars, which are physically in EAR modules (see the attached screenshot).

Then after, some classpath entries are broken due to those modules missing.

The catch here is for WSAD, those jars must be under EAR root, otherwise they won't be resolved and deployed, go figure what made them fix on that...



Attachment(s):
unresolved.gif
0

Hello Andrew,

Can you send me a sample of your Eclipse project for EAR module?

Best regards,

Vladislav Kaznacheev
Project Manager, IntelliJ IDEA
http://www.jetbrains.com
"Develop with Pleasure!"

Hey Vladislav,

I was away for a week, sorry for the delay. With the new 6799 build,
the above problem is solved. And we get to the next one.

Now, the Ear modules are not displayed during the import process. The
imports completes fine, though with one message about missing jars,
which are physically in EAR modules (see the attached screenshot).

Then after, some classpath entries are broken due to those modules
missing.

The catch here is for WSAD, those jars must be under EAR root,
otherwise they won't be resolved and deployed, go figure what made
them fix on that...



0

Please sign in to leave a comment.