Quite right, it's "classifier" and not "qualifier".  It was a typo, honest!
:-p


Nice thinking about using profiles, lets you keep the pom in sync between
trunk and the branch, should help nicely with those merges  One change I
would make though is to activate the profile by way of a property:
http://maven.apache.org/guides/introduction/introduction-to-profiles.html

It doesn't make a great deal of difference at this level, but I've found it
can really make things a lot more flexible if you want to start mixing in
configurations based on architecture or JVM version, or if you're working
with multi-module builds.



<http://maven.apache.org/guides/introduction/introduction-to-profiles.html>

On Sat, Sep 19, 2009 at 6:28 PM, Indrajit Raychaudhuri
<[email protected]>wrote:

>
> Dependency classifier might be close to what you'd need.
> See the 'Classifier' section in
> http://maven.apache.org/pom.html#Dependencies
>
> So, you could create a build profile (disabled by default), say
> dppactor as so:
>  <profiles>
>    <profile>
>      <id>dppactor</id>
>      <activation>
>        <activeByDefault>false</activeByDefault>
>      </activation>
>      <dependencies>
>        <dependency>
>          <groupId>net.liftweb</groupId>
>          <artifactId>lift-actor</artifactId>
>          <version>1.1-SNAPSHOT</version>
>          <classifier>dpp</classifier>
>        </dependency>
>      </dependencies>
>    </profile>
>  </profiles>
>
> See http://maven.apache.org/pom.html#Profiles for more.
>
> Now if you invoke mvn -Pdppactor compile, the dependency would be on
> lift-actor-1.1-SNAPSHOT-dpp.jar!
>
> To create lift-actor-1.1-SNAPSHOT-dpp.jar, you can follow the same
> technique (another profile). Just use the optional config parameter
> 'classifier'
> See:
> http://maven.apache.org/plugins/maven-jar-plugin/jar-mojo.html#classifier
>
> Now Hudson build would just need the extra param (-P) to do the
> needful.
>
> Hope this helps.
>
> Cheers, Indrajit
>
>
> On Sep 19, 4:38 am, David Pollak <[email protected]>
> wrote:
> > Folks,
> > Is there a clean and easy way that anyone knows of to have Hudson do
> > alternate builds from different Git branches and put them in SNAPSHOTS
> with
> > different versions (e.g., 1.1-SNAPSHOT_DPP_ACTOR)?
> >
> > I am making some wholesale changes to Lift's use of Actors (basically
> > getting rid of all Scala Actors and creating some simple traits that Akka
> or
> > other systems can implement so that Lift-based systems can choose
> different
> > Actor implementations.
> >
> > Given that these changes are non-trivial, I'd like to run a parallel
> version
> > of Lift for at least a few weeks and get feedback on the API changes and
> > performance before committing the code to the main branch, but I want the
> > code to available in Hudson.
> >
> > So... any ideas?
> >
> > Thanks,
> >
> > David
> >
> > --
> > Lift, the simply functional web frameworkhttp://liftweb.net
> > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > Follow me:http://twitter.com/dpp
> > Git some:http://github.com/dpp
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to