Eclipse Utility Project not included in EAR /lib directory on rebuild --------------------------------------------------------------------- Key: JBIDE-4676 URL: https://jira.jboss.org/jira/browse/JBIDE-4676 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS, UpStream Affects Versions: 3.1.0.M2 Environment: Eclipse 3.5 w/ JBoss Tools 3.1.0 M2. Using the "JBoss v5.0" server instead of the "JBoss AS 5.1". Reporter: Margot Media Attachments: EarTest.tar.gz I have an application with a single MDB .jar file and 3 Utility Module .jar files. The utility projects are set up to appear in the EAR under the /lib directory. The first time the EAR file is deployed to the server, the /lib directory is populated correctly. However, if I change my source code and republish to the server, the /lib directory is not present! If I remove the EAR file from the server, then re-add it, the /lib directory is created properly. The first time, it looks like this: Code: MyEar.ear |- /lib | |- Utility1.jar | |- Utility2.jar | |- Utility3.jar |- /META-INF | |- MANIFEST.MF |- MyMDB.jar If I change the code in MyMDB.jar, the EAR file is generated like: Code: MyEar.ear |- /META-INF | |- MANIFEST.MF |- MyMDB.jar with the obvious class path problems by not having the utility jar files present. Steps to reproduce: 1. Create new "Java EE Enterprise Application Project" called MyEar using default configuration. 2. Create new "Java EE Utility Project" called Utlity 1 using the default configuration and add it to MyEar 3. Create new "Java EJB Project" called MyMdb using the default configuration and add it to MyEar 4. Set the Utility1.jar file to appear in the lib directory of MyEar 5. Create a class in the Utility1 project w/ some code (eg a POJO with one member and setter/getter) 6. Create MDB in the MyMDB project using the "Message-Driven Bean (EJB 3.x)" wizard 7. Add code to the MDB to make it dependent upon the Utility1 project 8. Start JBoss and deploy MyEar to the server. Verify that the EAR file correctly included the Utility1.jar file in the /lib directory 9. Make a change to the code in MyMDB and republish MyEar. Verify that the EAR does not include the /lib directory at all

Eclipse Utility Project not included in EAR /lib directory on rebuild --------------------------------------------------------------------- Key: JBIDE-4676 URL: https://jira.jboss.org/jira/browse/JBIDE-4676 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS, UpStream Affects Versions: 3.1.0.M2 Environment: Eclipse 3.5 w/ JBoss Tools 3.1.0 M2. Using the "JBoss v5.0" server instead of the "JBoss AS 5.1". Reporter: Margot Media Assignee: Rob Stryker Priority: Critical Fix For: 3.1.0.CR2 Attachments: EarTest.tar.gz I have an application with a single MDB .jar file and 3 Utility Module .jar files. The utility projects are set up to appear in the EAR under the /lib directory. The first time the EAR file is deployed to the server, the /lib directory is populated correctly. However, if I change my source code and republish to the server, the /lib directory is not present! If I remove the EAR file from the server, then re-add it, the /lib directory is created properly. The first time, it looks like this: Code: MyEar.ear |- /lib | |- Utility1.jar | |- Utility2.jar | |- Utility3.jar |- /META-INF | |- MANIFEST.MF |- MyMDB.jar If I change the code in MyMDB.jar, the EAR file is generated like: Code: MyEar.ear |- /META-INF | |- MANIFEST.MF |- MyMDB.jar with the obvious class path problems by not having the utility jar files present. Steps to reproduce: 1. Create new "Java EE Enterprise Application Project" called MyEar using default configuration. 2. Create new "Java EE Utility Project" called Utlity 1 using the default configuration and add it to MyEar 3. Create new "Java EJB Project" called MyMdb using the default configuration and add it to MyEar 4. Set the Utility1.jar file to appear in the lib directory of MyEar 5. Create a class in the Utility1 project w/ some code (eg a POJO with one member and setter/getter) 6. Create MDB in the MyMDB project using the "Message-Driven Bean (EJB 3.x)" wizard 7. Add code to the MDB to make it dependent upon the Utility1 project 8. Start JBoss and deploy MyEar to the server. Verify that the EAR file correctly included the Utility1.jar file in the /lib directory 9. Make a change to the code in MyMDB and republish MyEar. Verify that the EAR does not include the /lib directory at all