Unless something has changed in the (rather long) time since I looked at this, 
you don't want to use that option because it doesn't use mvn deploy and doesn't 
end up with the right metadata.  Can you adjust hudson to run mvn clean deploy 
instead of mvn clean install?  This can result in only the first few modules of 
a broken build getting deployed, but I'm OK with that happening occasionally.

thanks
david jencks

On Jun 22, 2011, at 4:26 PM, Joseph Bergmark wrote:

> I set up the Hudson builds for both OpenWebBeans-trunk
> and OpenWebBeans_1.0.x.  I suspect I could configure it to also configure it
> to publish them.  I see there is a "Deploy artifacts to Maven repository"
> option that takes a repository URL.
> 
> Sincerely,
> 
> Joe
> 
> On Wed, Jun 22, 2011 at 6:02 PM, David Blevins <david.blev...@gmail.com>wrote:
> 
>> 
>> On Mar 10, 2011, at 1:43 AM, Mark Struberg wrote:
>> 
>>> Not sure if we like to do that. Of course it would be easier to handle,
>> but this might break geronimo snapshot releases which assume that a current
>> SPI doesn't got changed.
>>> 
>>> I think we can leave it as is with our manual deploys. This way, we have
>> the opportunity to tell the geronimo guys that something will change before
>> we break their build ;)
>>> 
>>> @geronimo folks, what is your opinion?
>> 
>> Now that we have CI systems setup for both Geronimo and OpenEJB we're
>> getting a fair amount of build failures due to out of date OWB snaps.
>> 
>> Who has access to setup the OWB snapshots to automatically publish?
>> 
>> 
>> -David
>> 
>>> --- On Thu, 3/10/11, David Blevins <david.blev...@gmail.com> wrote:
>>> 
>>>> From: David Blevins <david.blev...@gmail.com>
>>>> Subject: Snapshots
>>>> To: dev@openwebbeans.apache.org
>>>> Date: Thursday, March 10, 2011, 1:06 AM
>>>> Does our hudson setup deploy
>>>> snapshots?  If not I could set that up in
>>>> buildbot.  It's possible in buildbot to have it only
>>>> deploy after a successful 'mvn clean install'
>>>> 
>>>> -David
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> 
>> 
>> 

Reply via email to