maven allows you to build additional project(s) base on a condition ( ie a external property passinging from command line )
So on your parent pom, the one that host all your project including the assembly, create a profile to do this job http://maven.apache.org/guides/introduction/introduction-to-profiles.html A similar example is here http://svn.codehaus.org/mojo/trunk/mojo/maven-native/native-maven-plugin/src/it/jni/native/pom.xml where it uses a external property to trigger a native project to be built. -D On 9/11/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:
If I have the assembly in a project, how can I trigger a separate project during a release? Sorry I didn't follow that. Also, what do you mean conditional build? D- -----Original Message----- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Monday, September 11, 2006 12:50 PM To: Maven Users List Subject: Re: Binding Assembly Executing to the Release Plugin Use maven profile to do conditional build. In your case, I would suggest to create a separate project to do the assembly, and profile it to run only when a release occurs. -D On 9/11/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote: > > Is it possible to bind the assembly plugin to the release phase? > > > > I want to create a jar with dependencies and have it get released, but I > don't want to have to create that everytime I run install. > > > D- > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
