Re: second zip artifact from the same pom?
I wanted to thank you for responding and giving me a good head start on the
maven-assembly-plugin. The documentation is Excellent and they are powerful
indeed. I also wanted to share the very simple solution to building the zip
file:
--in my profile sections for different env's I have the assembly plugin
activation "attached" to the package phase
maven-assembly-plugin
src/assembly/assembly.xml
make-assembly
package
attached
--and for the descriptor itself, all I needed was a fileSet
static-assembly
zip
false
false
style/**
js/**
images/**
target/${hard-coded-final-name}
/
Thanks again, James
RE: second zip artifact from the same pom?
Additionally, you can use the "attach" option to make it part of the regular build rather than having an extra step... -Original Message- From: matthew sporleder [mailto:[EMAIL PROTECTED] Sent: Friday, May 16, 2008 4:02 PM To: Maven Users List Subject: Re: second zip artifact from the same pom? On Fri, May 16, 2008 at 3:16 PM, ziprman <[EMAIL PROTECTED]> wrote: > Hi, > > I have a typical war webapp which I deploy to tomcat. At the same time I > have the typical static content (images, js, css) that needs to go to my > webservers. It is easy enough to exclude the static content from my war, but > I would like to zip up the static content and also deploy it to my repos as > a separate artifact. Both attached to a phase and as an independent command, > would be optimal, because we often update static content without needing to > deploy the app. > > I have read some older postings about using assemblies (I have not used this > plugin before) and the maven-zip-plugin, as both a standalone archetype and > a build-plugin. Unfortunately, I am unsure which applies to my use case. I > suppose I could also just use an ant task, as well. > > I was just wondering if anyone has done this and what is the best approach. > You can do this with assemblies using sources/fileSets without too much trouble. (this assumes you want all of your resources/ put into the zip in a module called something-front) into your pom: maven-assembly-plugin src/assembly/assembly.xml assembly.xml: front-assembly zip false *-front false src/main/resources/ / - 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: second zip artifact from the same pom?
On Fri, May 16, 2008 at 3:16 PM, ziprman <[EMAIL PROTECTED]> wrote: > Hi, > > I have a typical war webapp which I deploy to tomcat. At the same time I > have the typical static content (images, js, css) that needs to go to my > webservers. It is easy enough to exclude the static content from my war, but > I would like to zip up the static content and also deploy it to my repos as > a separate artifact. Both attached to a phase and as an independent command, > would be optimal, because we often update static content without needing to > deploy the app. > > I have read some older postings about using assemblies (I have not used this > plugin before) and the maven-zip-plugin, as both a standalone archetype and > a build-plugin. Unfortunately, I am unsure which applies to my use case. I > suppose I could also just use an ant task, as well. > > I was just wondering if anyone has done this and what is the best approach. > You can do this with assemblies using sources/fileSets without too much trouble. (this assumes you want all of your resources/ put into the zip in a module called something-front) into your pom: maven-assembly-plugin src/assembly/assembly.xml assembly.xml: front-assembly zip false *-front false src/main/resources/ / - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
second zip artifact from the same pom?
Hi, I have a typical war webapp which I deploy to tomcat. At the same time I have the typical static content (images, js, css) that needs to go to my webservers. It is easy enough to exclude the static content from my war, but I would like to zip up the static content and also deploy it to my repos as a separate artifact. Both attached to a phase and as an independent command, would be optimal, because we often update static content without needing to deploy the app. I have read some older postings about using assemblies (I have not used this plugin before) and the maven-zip-plugin, as both a standalone archetype and a build-plugin. Unfortunately, I am unsure which applies to my use case. I suppose I could also just use an ant task, as well. I was just wondering if anyone has done this and what is the best approach. Thanks, James
