Vincent, does it break existing behaviour? I.e. if I have a build that uses war now, will it no longer work without changes when the change is done?
One of the things on the todo list for the j2ee plugin has been to clear up where/how things are picked up from, so I'm not against it per se. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers "Vincent Massol" <[EMAIL PROTECTED]> 06/15/02 11:09 PM Please respond to "Turbine Maven Developers List" To: "'Turbine Maven Developers List'" <[EMAIL PROTECTED]> cc: Subject: [j2ee plugin] web-inf files for war + Proposal Hi, There is something that is troubling me in the war target. It is that the web.xml file is being picked from �{maven.conf.dir} and that all other files that go into WEB-INF are picked from ${maven.j2ee.war.src}/${maven.j2ee.war.name} It is not consistent. Everything that goes into WEB-INF should be located in one place only. Either in a ${maven.conf.dir}/${maven.j2ee.war.name}-WEB-INF directory or from ${maven.j2ee.war.src}/${maven.j2ee.war.name}/WEB-INF My proposal would be to have the following properties defined : maven.j2ee.war.content=${maven.j2ee.war.src}/${maven.j2ee.war.name} maven.j2ee.war.webinf=${maven.conf.dir}/${maven.j2ee.war.name}-WEB-INF maven.j2ee.war.webxml=${maven.j2ee.war.webinf}/web.xml For info, I will put my weblogic.xml file into maven.j2ee.war.webinf as it is a file that is supposed to go along with web.xml Some webapps keep content files in WEB-INF (for example Jetspeed has its template files in WEB-INF). This will still work as this is content that could be picked up by maven.j2ee.war.content. You could also view it as configuration files and then it will be picked up by maven.j2ee.war.webinf. I'd like to change this behaviour now. Anyone feels strongly against this ? Thanks -Vincent -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
