Mike, Understood, thanks for the explanation. At this point, as you suggest, mvn has done it's trick and I am letting Eclipse use the WEB-INF as expanded by mvn, so it should be working. WTP, I believe, has some notion of dependent projects and it knows (maybe) how to accept contributions from other projects into the final webapp. I'll look into that next.
Of course, I could depend on mvn doing the work after I change a JSP or something in a project, but that defeats the quick response from hot-deploy capabilities of the server. Or, I could edit the JSP in the assembly created by mvn, which would work, but from past experience, I often forget to copy it back to the correct project and end up loosing work! Anyway, will let you know how I fare. Shash AppFuse 2.0 uses the overlay[1] feature of the Maven WAR plugin, which is probably going to be tricky to replicate in an IDE build. Basically it merges the contents of dependent war files with the project to build the final, deployable war. The warpath jar files are created purely to make the contents of the WEB-INF/classes directory of all dependent war files available on the compile classpath for the other steps in the build. They should not form part of the final build, rather the IDE build tools should emulate the war overlay capabilities of the Maven war plugin - the easiest way to do this might be to delegate to Maven to do the build rather than rely on the IDE tools. Mike [1]http://maven.apache.org/plugins/maven-war-plugin/examples/war- overlay.html -- View this message in context: http://www.nabble.com/Appfuse-M3-and-Eclipse-help-tf3245072s2369.html#a9035813 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
