[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4930) JBoss AS driver, Full Publish on EAR module doesn't publish lib/foo.jar

JBoss AS driver, Full Publish on EAR module doesn't publish lib/foo.jar ----------------------------------------------------------------------- Key: JBIDE-4930 URL: https://jira.jboss.org/jira/browse/JBIDE-4930 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M2 Reporter: Darryl Miles Assignee: Rob Stryker Fix For: 3.1.0.M4 I have an EAR with a WAR inside. I moved an incorrectly placed JAR library from the $WAR/WEB-INF/lib/ to $EAR/lib/ dir. I did this outside of eclipse (with file manager). I then issued a "Refresh" (F5) on the toplevel for the EAR project node (in Project Explorer) and then WAR project node. Eclipse correctly fixed the file structure changes in the view of the Project explorer. I then did a "Full Publish" on the EAR module I have added under the "JBoss 5.1.0.GA Server Runtime" in the "Servers View". This should have corrected the difference between the deploy directory file structure and what the Project Explorer has of the file structure. The JAR file I move was removed from the WAR but it was never published to the EAR. I just tested this and the easiest way to reproduce: * Setup workspace with EAR project and WAR project. WAR is inside EAR. * Setup empty JBoss AS runtime. * Add the EAR module to the JBoss AS runtime. * Click Publish on JBoss AS runtime (no need to start it). * Now outside of Eclipse place a JAR in $EAR/lib/ (/project-ear/EarContent/lib/) from your system file manager / Windows Explorer etc... * Now "Full Publish" on JBoss AS runtime (alright nothing should happen as even the Project Explorer can't see it yet, but go and manually check that is in the deploy/* dir right now. * Now "Refresh" on the toplevel of the EAR "project-ear". Eclipse project explorer should now display the JAR. * Now "Incremental Publish" or "Full Publish" (either will do as nether do the correct thing at this point). Manually check whats in the deploy/* dir and see that you JAR is not there. Workaround: * Now delete the module from the JBoss AS runtime. * Now re-add it and publish. (Confirm that the JAR is not in the deploy/* for the EAR). What is it that adding the module does that a "Full Publish" doesn't. As a user I'd expect a "Full Publish" to re-validate every item on both sides (Eclipse view and deploy/* view of file structure and fix the differences).