Irida J2EE development completely fails
Hi!
Yesterday downloaded IDEA Irida EAP B#3075, imported a (J2EE) project from 4.5.
First, the JBoss plugin from Fuhrer failed... ok, I expected this and removed it (deploying to JSAS anyhow), remoed JBoss DDs and restarted.
Still, J2EE features didn't work, Irida didn't recognize DDs (ejb-jar, application etc.), strange enough, some XML-entities/elements were recognized, some not (???); also, building an EJB module doesn't seem to work when a dependent-upon module is set to "JAR, link via manifest" (fails with "Library.jar is a directory"), "copy to /" works; the module's directory is filled with "crap" (the various library-jars, a "Library.jar" directory (probably from my module "Library", but contains all classes) and the EJB-jar file seems to contain ALL classes of the project (?).
Just a first experience, regards,
Messi
请先登录再写评论。
Anyone had the same problems or was this just my fault? Can I fix it somehow? Will it be fixed in an upcoming EAP build (I mean one of the closer ones)?
regards,
Messi
Hi,
Please, try recreate the project from the scratch. If the problem
persists then in order to fix the problem it would be invaluable to have
tiny project illustrating the problem.
Bernhard Messerer wrote:
--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"
Tried re-creating the project from scratch, same error...
Wondering, on my PC/B#3075 installation this always happens when:
1) Create new Project
2) Create a Java Module (e.g. "Dependency") with at least one class
3) Create an EJB Module (e.g. "DependentEJB")
4) Create whatever-EJB in the EJB module (e.g. "TestSession")
5) Make module "DependentEJB" depend on module "Dependency" in Module settings (via Dependencies in module-settings)
6) In the EJB-module settings select "Jar module, link via manifest and copy to", leave default for target ("/DependencyEJB.jar")
7) Select "Create EJB Module JAR file" in J2EE build settings of "DependentEJB"
8) Make module "DependentEJB" (or project, ...), exception is thrown:
BEGIN EXCEPTION
java.io.FileNotFoundException: /files/projects/DCX/source/DependentEJB/Dependency.jar (Is a directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:179) at java.io.FileOutputStream.]]>(FileOutputStream.java:131)
at com.intellij.j2ee.make.JarAndCopyBuildInstructionImpl.makeJar(JarAndCopyBuildInstructionImpl.java:24)
at com.intellij.j2ee.make.JarAndCopyBuildInstructionImpl.addFilesToExploded(JarAndCopyBuildInstructionImpl.java:27)
at com.intellij.j2ee.make.ModuleBuilder$1.visitFileCopyInstruction(ModuleBuilder.java)
at com.intellij.j2ee.make.BuildInstructionVisitor.visitJarAndCopyBuildInstruction(BuildInstructionVisitor.java:19)
at com.intellij.j2ee.make.JarAndCopyBuildInstructionImpl.accept(JarAndCopyBuildInstructionImpl.java:26)
at com.intellij.j2ee.make.BuildRecipeImpl.visitInstructionsWithExceptions(BuildRecipeImpl.java:19)
at com.intellij.j2ee.make.ModuleBuilder.a(ModuleBuilder.java:61)
at com.intellij.j2ee.make.ModuleBuilder.buildAll(ModuleBuilder.java:72)
at com.intellij.j2ee.make.J2EECompiler$5.run(J2EECompiler.java:3)
at com.intellij.openapi.e.b.c.runReadAction(c.java:166)
at com.intellij.j2ee.make.J2EECompiler.a(J2EECompiler.java:31)
at com.intellij.j2ee.make.J2EECompiler.process(J2EECompiler.java:15)
at com.intellij.compiler.b.o.a(o.java:2)
at com.intellij.compiler.b.f.a(f.java:251)
at com.intellij.compiler.b.f.a(f.java:667)
at com.intellij.compiler.b.f.a(f.java:288)
at com.intellij.compiler.b.f.a(f.java:635)
at com.intellij.compiler.b.f.access$900(f.java:40)
at com.intellij.compiler.b.f$14.run(f$14.java)
at com.intellij.openapi.progress.a.a.runProcess(a.java:36)
at com.intellij.compiler.b.f$25.run(f$25.java:5)
END EXCEPION
Somehow I get the impression that this only happens on my install or does nobody else use EJB modules that depend on a library which is copied as jar? Or does everybody use ANT?
kind regards,
Messi
Sorry, forgot: So the "not-recognizing" of tags in EJB-jar was resolved by recreating the project, now its just the jar-inclusion of dependent-upon modules that doesn't work (as soon as I change "jar & link via manifest" to "do not include", it works). As seen from the exception, the created directory is not jarred so IDEA only finds the dir with the same name. I guess the garbage left in the module-directories (libraries, the jar-directory etc.) would have been cleaned up, if the process was not interrupted by the exception...
regards,
Messi
The exception is fixed in the next build, thanks for report.
--
regards,
Alexey Kudravtsev
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Bernhard Messerer" <no_mail@jetbrains.com> wrote in message
news:29564974.1099040787037.JavaMail.itn@is.intellij.net...
>
>
>