For our build, I hacked the ear plugin. I added an 'explodedUri' attribute to the web artifact configuration. When the application.xml file is built, it sets the web component to the exploded url on the file system.
The down side is that you have to have a relative reference to your web xml project directory. Its "dirty". The upside is that you only need to run "war:exploded" on that project. Not the full ear build. Now, even more hacky, I added a "movejsp" target to the war plugin. This bypasses everything in the war plugin build except moving the jsps to the target dir. This is when you're just updating jsps and other static files. Hacky? Yeah, sure. But it works. I haven't spent too much time coming up with a more formal "mavenized" version of this, but I'd like to. I think there is a serious issue with the way the ear and war plugins work. I mean, they work great, but for builds. Development gets to be difficult in some environments. On 4/18/06, brianwainwright <[EMAIL PROTECTED]> wrote: > > > Hi, > > I am currently trying to move my teams large > multi-project/multi-webapp/multi-ear application from Maven 1.x to Maven > 2, > and overcome most of the problems I've had on the way, but there's one > issue > I can't work out. > > Our current (Maven 1.x) build, we have a customized goal which produces an > exploded ear which in turn contains an exploded war - (our current > practise > is for developers to deploy fully exploded ears/wars on their own JBoss > servers while developing.). We do this by "unwar"ing any bundled war > dependencies in the exploded ear. > > Is there any (simple) way to produce the same kind of fully exploded ear > in > M2? > > I've looked at war:exploded, which will build the exploded war, but then > the > ear plugin will look for the .war artifact in the repository when trying > to > bundle it's dependencies, so the exploded war wouldn't be used when > packaging the ear? > > I've also looked at the maven-explosion plugin, which could possibly work > for us, but it seems inefficient to war/ear the original artifacts and > then > unpack them to explode them when their exploded directories already exist. > > Thanks for your help, > > Brian Wainwright > Developer > Burns E-Commerce > Mansion House, Manchester Road, Altrincham, Cheshire, WA14 4RJ, UK > http://www.burnsecs.com > mailto:[EMAIL PROTECTED] > > > -- > View this message in context: > http://www.nabble.com/Exploded-WAR-in-exploded-EAR-t1468379.html#a3968873 > Sent from the Maven - Users forum at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
