continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin van den Bemt <mll...@mvdb.net>
Subject Re: svn commit: r667235 - /continuum/trunk/pom.xml
Date Fri, 13 Jun 2008 14:25:19 GMT
Sorry that I just picked an example that is reasonably managed by people (in this case you
specifically) on the project. In this case it was pretty hard to solve it another way (the
static
final doesn't really help) anyhow..

The fix will only work if you public http access, since most companies that setup a maven
proxy
probably don't sync with the snapshot repo of codehaus (not a problem for me in this case
though,
but at a couple of customers I don't have that luxury).

(this is not the first time that SNAPSHOT's are used, it's just that I noticed now one being
added,
that I thought it was a good time to bring the subject up).

Can you agree on the general sentiment even though the example taken was a bad one ?

(I had several problems in the past because of changing SNAPSHOT in continuum, hence the mails..)


Mvgr,
Martin

Olivier Lamy wrote:
> Hi,
> The comment says "upgrade to last p-u SNAPSHOT to test fix for
> CONTINUUM-1360 (semicolon in svn args)".
> There is an issue CONTINUUM-1360 which depends on a fix in p-u [1]
> which has been fixed in the p-u trunk [2] (note the commiter name ;-)
> ).
> And I can't see any build issue because the codehaus snapshots repo is
> declared in the pom due to the snapshot dependency.
> 
> --
> Olivier
> 
> [1] http://jira.codehaus.org/browse/PLXUTILS-78
> [2] http://fisheye.codehaus.org/changelog/plexus/?cs=7367
> 
> 2008/6/13 Martin van den Bemt <mllist@mvdb.net>:
>> This is a mail coming a bit out of the blue probably, since I haven't been really
publicly active
>> yet on continuum.
>>
>> Can we please not depend on SNAPSHOT's anymore that are outside of the continuum
project ? This
>> makes continuum highly unstable and makes maintenance way too hard if you also have
to start
>> monitoring the external snapshots. Continuum is not the place to test a bug fix in
plexus-utils I
>> think (if that is what happened, didn't check the plexus-utils changes).
>>
>>
>> Mvgr,
>> Martin
>>
>> olamy@apache.org wrote:
>>> Author: olamy
>>> Date: Thu Jun 12 14:30:43 2008
>>> New Revision: 667235
>>>
>>> URL: http://svn.apache.org/viewvc?rev=667235&view=rev
>>> Log:
>>> upgrade to last p-u SNAPSHOT to test fix for CONTINUUM-1360 (semicolon in svn
args)
>>>
>>>
>>>
>>> Modified:
>>>     continuum/trunk/pom.xml
>>>
>>> Modified: continuum/trunk/pom.xml
>>> URL: http://svn.apache.org/viewvc/continuum/trunk/pom.xml?rev=667235&r1=667234&r2=667235&view=diff
>>> ==============================================================================
>>> --- continuum/trunk/pom.xml (original)
>>> +++ continuum/trunk/pom.xml Thu Jun 12 14:30:43 2008
>>> @@ -640,7 +640,7 @@
>>>        <dependency>
>>>          <groupId>org.codehaus.plexus</groupId>
>>>          <artifactId>plexus-utils</artifactId>
>>> -        <version>1.5.1</version>
>>> +        <version>1.5.2-SNAPSHOT</version>
>>>        </dependency>
>>>        <dependency>
>>>          <groupId>org.codehaus.plexus</groupId>
>>>
>>>
>>>
>>>
> 
> 

Mime
View raw message