WTP 3.0.4 will be released on Feb 25th as part of Eclipse Ganymede SR2. In Eclipse SDK versioning this means 3.4.2.
Greetings, Kaloyan -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Max Rydahl Andersen Sent: 12 февруари 2009 г. 14:46 ч. To: General discussion of project-wide or architectural issues. Subject: Re: [wtp-dev] JEE lib support > Max, your observations are correct. > It is a bug that the EAR's /lib JARs are not included in the classpath of the > EAR's modules. > This bug was resolved in WTP 3.0.4 RC2: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=255243 > ah thanks, so it did work once and i'm not crazy ;) WTP 3.0.4 is scheduled on same date as Eclipse 3.3.4, right ? /max > There is another open bug that (having 255243 fixed) the classpath does not > updates always automatically and in this case a manual Java EE Tools> Update > EAR Libraries action is required: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=263918 > > Greetings, > Kaloyan > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Max Rydahl Andersen > Sent: 12 февруари 2009 г. 12:30 ч. > To: General discussion of project-wide or architectural issues. > Subject: [wtp-dev] JEE lib support > > Hi, > > Sorry for the 75% user question here - but 25% is dev. > > I was pretty sure/confident that after the latest changes to the EAR/lib > support WTP would now support the JEE5 notion of EAR/lib and > automatically pick these elements up on the classpath....but I simply > cannot figure out how to setup the projects to do this. > > The tools insists on adding the lib/*.jar to the manifest.mf of the ear > and war's when I add the .jars under JEE Module Dependencies. > > Adding the EAR libraries container also only seem to listen to what is > in the manifest.mf and not what is (or should be) automatically exposed > when you have a /lib folder in your EAR. > > Before I go crazy looking for the right combination of setup I would > just like to know if that is the expected behavior or if there is a > magical way to avoid forcing redundant manifest.mf files on users ? > > If it really is not possible then I really really would like to know > what that "Change library directory" on EAR projects is for ? I thought > I understood it last time we had this, but I must have lost it again. > > /max > _______________________________________________ > wtp-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/wtp-dev > _______________________________________________ > wtp-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/wtp-dev > _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
