On Fri, Sep 18, 2009 at 4:44 PM, Kevin Wright <[email protected]
> wrote:

> Your best bet is probably:
>
> Modifiy the pom in the branch, e.g. by adding a qualifier to the version
> infoManually configure a second build in hudson that points to the branch
>
> I'm pretty sure you can't automate on this one :(
>

Thanks!


>
>
> On Sat, Sep 19, 2009 at 12: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 framework http://liftweb.net
>> Beginning Scala http://www.apress.com/book/view/1430219890
>> Follow me: http://twitter.com/dpp
>> Git some: http://github.com/dpp
>>
>>
>>
>
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://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