[myoungstrom]

I’m using Eclipse 3.0 and ME 3.8b1 on Windows.

Don’t know if this has been noted yet, I did a quick search and didn’t find anything.

I just started using the “Always jar” and “Smart Deployment” features of a Web Module and it is giving me some trouble.

1. The auto jar doesn’t appear to auto jar correctly if I my web app has a dependency on a Java Project that has multiple source folders each with their own output folder for example: java and test and I leave my default output folder as /bin. When I deploy my webapp then myeclipse creates an xxx_bin.jar, an xxx_test.jar, and an xxx_java.jar

If I change my default output folder to /bin/java then no .jar files are created when I deploy my webapp.

2. If webapp #1 depends on webapp #2 then when I deploy webapp #1 then no jar is created containing the classes in webapp #2 of #1 to use.

Regards,
Mike

[Scott Anderson]

a Java Project that has multiple source folders each with their own output folder for example: java and test and I leave my default output folder as /bin. When I deploy my webapp then myeclipse creates an xxx_bin.jar, an xxx_test.jar, and an xxx_java.jar

That’s actually by design. The number of jars created does not affect the functionality or the classloading behavior.

If I change my default output folder to /bin/java then no .jar files are created when I deploy my webapp.

I don’t know that we’ve tried it with arbitrary depth output directories, only with output directories that are direct children of the project. Try setting the output of all src folders to /bin. How does that work for you.

2. If webapp #1 depends on webapp #2 then when I deploy webapp #1 then no jar is created containing the classes in webapp #2 of #1 to use.

Only plain Java projects can be library projects by design. A web project dependency could mean, for instance, that you expect all the web content to also be deployed and web.xml’s to be merged somehow. In order to avoid this confusion, only Java projects are honored as library projects. Since it sounds like you have two web projects that depend on some common java library code, the easy way to suppor it is to create a plain java project to hold the common code and make each web project dependent on it.

[myoungstrom]

That’s actually by design. The number of jars created does not affect the functionality or the classloading behavior.

Sounds good. the xxx_test.jar and xxx_java.jar are fine the strange one was the xxx_bin.jar that contained bo the /bin/test and /bin/java directories. The expected behavior to me would have been:

1. Create a jar for each of the output folders for source folders (which my eclipse does just fine).

2. If output folders for source folders equals the number of source folders then skip creation of a default output folder jar. Else jar up default output folder too.

Any thoughts on that?

I don’t know that we’ve tried it with arbitrary depth output directories, only with output directories that are direct children of the project. Try setting the output of all src folders to /bin. How does that work for you.

This problem came up in the exact same situation as above when I have 2 source folders with their own output folders. If I set the default output to /bin then I get the 3 jars with xxxx_bin.jar containing /bin/java and /bin/test. If ME followed my expected behavior above then the default output folder should just be ignored….but I found it strange that when I changed it then nothing was jared….I haven’t tried enough combinations to determine exactly what is going on here but it doesn’t seem correct. 🙂

Only plain Java projects can be library projects by design. A web project dependency could mean, for instance, that you expect all the web content to also be deployed and web.xml’s to be merged somehow. In order to avoid this confusion, only Java projects are honored as library projects. Since it sounds like you have two web projects that depend on some common java library code, the easy way to suppor it is to create a plain java project to hold the common code and make each web project dependent on it.

Sounds good. That’s kind of what I figured the deal was and that’s fine.

Mike

[Scott Anderson]

Any thoughts on that?

Seems reasonable. It probably didn’t dawn on anyone that someone would explicitly set their output directories to be subdirectories of the default output directory. 🙂 I’ve opened a problem report on it for investigation. Thanks for reporting it.

[Author]

Posts