Re: AW: Guidance on the Pluto Portal Gump build

[cdoremus <CD...@hannaford.com>]

I am also a committer to Apache Pluto. We are still getting gump alerts on a
daily basis to the pluto-dev mail list. 

As Elliot has said, these alerts are because we have an incompatible version
of castor that gump uses in a Pluto branch where we will not be upgrading
any dependancies. Can you configure gump to only go against our trunk SVN
repository? Like Elliot, I know nothing about gump, but if you give me
instructions on making this change, I will give it a try.

TIA
/Craig 



Bill Barker-2 wrote:
> 
> 
> "Elliot Metsger" <em...@jhu.edu> wrote in message 
> news:6092360.post@talk.nabble.com...
> 
> 
>>Jan.Materne wrote:
>>>
>>> Gump _could_ use a fix version of Castor. But that's more an intend of a
>>> Continous _Build_ Server,
>>> not a Continous _Integration_ Server like Gump.
>>>
>>
>>Thanks for the clarification Jan.  If my inital email wasn't a dead
>>giveaway, I know next to nothing about Gump.
>>
>>
>>Jan.Materne wrote:
>>>
>>> Gump should show, that a project is failing because it is not compatible
>>> with the latest version of
>>> another project.
>>>
>>
>>I agree with your points.  Indeed, Gump has demonstrated its value to 
>> >Pluto
>>on occaison.  Most recently we upgraded from commons-fileupload 1.0 to 1.1
>>based on Gump messages.
>>
>>However, the failed build due to Castor is somewhat different.  With
>>commons-fileupload, we realized that upgrading to 1.1 was the best course 
>>of
>>action.  But, we probably aren't ever going to change the Pluto 1.0.2's
>>dependency on Castor, so we are going to continue to receive the nag 
>> >emails
>>to pluto-dev indefinitly.
>>
>>I'm wondering if there is a way that we can silence those emails
concerning
>>Castor.  Otherwise people on the list will forward the Gump messages to
>>/dev/null (which is a bad thing of course).
>>
> 
> We can set up a packaged-castor project and change Pluto to <depend /> on 
> it.  If you can send the download URL for the version you want, I can set
> it 
> up (probably tomorrow, unless somebody else on the list feels an itch :).
> 
> Of course, you can turn off the nags at any time, but it doesn't sound
> like 
> this is what you want.
> 
>>Thanks for your help,
>>Elliot
>>
>>Jan
>>
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Guidance-on-the-Pluto-Portal-Gump-build-tf2196839.html#a7447037
Sent from the Gump mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: Guidance on the Pluto Portal Gump build

[Stefan Bodewig <bo...@apache.org>]

On Mon, 20 Nov 2006, <CD...@hannaford.com> wrote:

> As Elliot has said, these alerts are because we have an incompatible
> version of castor that gump uses in a Pluto branch where we will not
> be upgrading any dependancies.

If there is no development on that branch anymore, then we might as
well stop building it and install it as a binary package.  I've
disabled the nag mails as a first step.

> Can you configure gump to only go against our trunk SVN repository?

We could, but since Gump and Maven 2 don't support each other (yet),
we couldn't do anything with it.  This will have to wait until Maven 2
builds are possible in Gump.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org