Re: Exploded WAR in exploded EAR
You can also activate that on a module per module basis[1] Cheers, Stéphane [1] http://maven.apache.org/plugins/maven-ear-plugin/examples/unpacking-a-module.html On Wed, Jul 15, 2009 at 6:19 PM, george_bancos george_ban...@yahoo.comwrote: I could achieve this by configuring the ear plugin like this: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ear-plugin/artifactId configuration unpackTypeswar/unpackTypes workDirectoryE:\Programs\JBoss510\server\default\deploy\ejb3Test2.ear/workDirectory /configuration /plugin /plugins /build brianwainwright 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 unwaring 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:brian.wainwri...@burnsecs.com -- View this message in context: http://www.nabble.com/Exploded-WAR-in-exploded-EAR-tp3968873p24501387.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge
Re: Exploded WAR in exploded EAR
I could achieve this by configuring the ear plugin like this: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ear-plugin/artifactId configuration unpackTypeswar/unpackTypes workDirectoryE:\Programs\JBoss510\server\default\deploy\ejb3Test2.ear/workDirectory /configuration /plugin /plugins /build brianwainwright 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 unwaring 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:brian.wainwri...@burnsecs.com -- View this message in context: http://www.nabble.com/Exploded-WAR-in-exploded-EAR-tp3968873p24501387.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Exploded WAR in exploded EAR
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 unwaring 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]
Re: Exploded WAR in exploded EAR
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 unwaring 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]
Re: Exploded WAR in exploded EAR
Thanks for the quick reply Kevin! I feared that the solution may involve hacking the plugins! It's essentially what we had to do with Maven 1.x, but I'd just hoped that there'd be a more complete solution in M2? Although, to be honest, I don't mind hacky too much at the moment, I've had to do that a fair bit to get our M2 build looking anything like our M1, but I'm mainly putting that down to the plugins not being mature enough just yet. I'll take a look at the war and ear plugins and see what I can come up with. I like your movejsp target idea - we had written a similar Maven 1.x goal to perform a similar step, so it's probably something I should add too to keep our developers happy! 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#a3969692 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Exploded WAR in exploded EAR
Attaching a diff for the ear plugin. Its a diff from 380736 to my local vendor branch. There are some extra things, like the deploy repository is our local path, but you should be able to see what I did to the code from the diff file. On 4/18/06, brianwainwright [EMAIL PROTECTED] wrote: Thanks for the quick reply Kevin!I feared that the solution may involve hacking the plugins!It'sessentially what we had to do with Maven 1.x, but I'd just hoped thatthere'd be a more complete solution in M2? Although, to be honest, I don't mind hacky too much at the moment, I'vehad to do that a fair bit to get our M2 build looking anything like our M1,but I'm mainly putting that down to the plugins not being mature enough just yet.I'll take a look at the war and ear plugins and see what I can come up with.I like your movejsp target idea - we had written a similar Maven 1.x goalto perform a similar step, so it's probably something I should add too to keep our developers happy!Brian WainwrightDeveloperBurns E-CommerceMansion House, Manchester Road, Altrincham, Cheshire, WA14 4RJ, UKhttp://www.burnsecs.com mailto:[EMAIL PROTECTED]--View this message in context: http://www.nabble.com/Exploded-WAR-in-exploded-EAR-t1468379.html#a3969692 Sent from the Maven - Users forum at Nabble.com.-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Exploded WAR in exploded EAR
Just FYI Kevin... Either you didn't attach the diff, or it got chopped in transit somewhere. Wayne On 4/18/06, Kevin Galligan [EMAIL PROTECTED] wrote: Attaching a diff for the ear plugin. Its a diff from 380736 to my local vendor branch. There are some extra things, like the deploy repository is our local path, but you should be able to see what I did to the code from the diff file. On 4/18/06, brianwainwright [EMAIL PROTECTED] wrote: Thanks for the quick reply Kevin! I feared that the solution may involve hacking the plugins! It's essentially what we had to do with Maven 1.x, but I'd just hoped that there'd be a more complete solution in M2? Although, to be honest, I don't mind hacky too much at the moment, I've had to do that a fair bit to get our M2 build looking anything like our M1, but I'm mainly putting that down to the plugins not being mature enough just yet. I'll take a look at the war and ear plugins and see what I can come up with. I like your movejsp target idea - we had written a similar Maven 1.x goal to perform a similar step, so it's probably something I should add too to keep our developers happy! 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#a3969692 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Exploded WAR in exploded EAR
, but I'm mainly putting that down to the plugins not being mature enough just yet. I'll take a look at the war and ear plugins and see what I can come up with. I like your movejsp target idea - we had written a similar Maven 1.x goal to perform a similar step, so it's probably something I should add too to keep our developers happy! 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#a3969692 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
