you have the same as brett and me.
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 26 May 2011 21:33, Arnaud Héritier aherit...@gmail.com wrote:
I don't remember which
Daniel,
This commit breaks jenkins:
https://builds.apache.org//view/M-R/view/Maven/job/maven-plugins-ITs-2.x/
and I also see it locally, can you review?
Thanks,
-Lukas
dk...@apache.org wrote:
Author: dkulp
Date: Thu May 26 14:30:55 2011
New Revision: 1127943
URL:
On Friday, May 27, 2011 4:37:45 AM Lukas Theussl wrote:
Daniel,
This commit breaks jenkins:
https://builds.apache.org//view/M-R/view/Maven/job/maven-plugins-ITs-2.x/
and I also see it locally, can you review?
I committed a fix and re-triggered a Jenkins build and it looks OK now.
That's interesting. *how* did it break that build?
On Fri, May 27, 2011 at 8:49 AM, Daniel Kulp dk...@apache.org wrote:
On Friday, May 27, 2011 4:37:45 AM Lukas Theussl wrote:
Daniel,
This commit breaks jenkins:
https://builds.apache.org//view/M-R/view/Maven/job/maven-plugins-ITs-2.x/
and
On Friday, May 27, 2011 9:32:20 AM Benson Margulies wrote:
That's interesting. *how* did it break that build?
Honestly, I didn't really dig into it. I just noticed in the pom that you
updated the asm version to 3.3.1, but you didn't update the asm-common version
to match it.On a whim, I
Daniel Kulp wrote:
On Friday, May 27, 2011 9:32:20 AM Benson Margulies wrote:
That's interesting. *how* did it break that build?
Honestly, I didn't really dig into it. I just noticed in the pom that you
updated the asm version to 3.3.1, but you didn't update the asm-common version
to
Maven 3 currently treats unrecognised version qualifiers as newer
releases than the GA release. For example:
1.0 is older than 1.0-xyz
It also looks like this was reversed at some point, since there is a
test case commented out on line 117 that expects the opposite behaviour
[1]. So is the
Hi
I'm Mohsen, a PhD student working with Prof. Ralph Johnson at the University of
Illinois at Urbana-Champaign (UIUC). Together with my team mates [1], we are
conducting a research study to better understand how developers, across
different
projects, interact with the Eclipse IDE for
On 5/27/11 12:02 PM, Paul Gier wrote:
Maven 3 currently treats unrecognised version qualifiers as newer
releases than the GA release. For example:
1.0 is older than 1.0-xyz
It also looks like this was reversed at some point, since there is a
test case commented out on line 117 that expects
It's about
1.0
vs
1.0-RC (Release Candidate)
vs
1.0-MR (Maintenance Release)
right?
I think one solution is in general equally good as the other since there is no
generally working solution.
Thus I'd also strongly +1 for re-establishing the old behaviour. Otherwise we'd
break
This seems to me to call out for an 'extension point' that supplies an
object that implements a protocol for making version decisions.
On Fri, May 27, 2011 at 12:31 PM, John Casey jdca...@commonjava.org wrote:
On 5/27/11 12:02 PM, Paul Gier wrote:
Maven 3 currently treats unrecognised
not sure if that would scale.
One dependency is using CR as acronym for 'candidate release' another is using
it for 'correctional release' or something.
Since there is no fixed list, this would really be hard to impl.
In fact it's mostly about sub-numbers (split with a '-').
LieGrue,
strub
On 5/27/11 1:16 PM, Mark Struberg wrote:
not sure if that would scale.
One dependency is using CR as acronym for 'candidate release' another is using
it for 'correctional release' or something.
Since there is no fixed list, this would really be hard to impl.
In fact it's mostly about
On 5/27/11 1:03 PM, Benson Margulies wrote:
This seems to me to call out for an 'extension point' that supplies an
object that implements a protocol for making version decisions.
That would bring up the issue of how Maven switches between version
schemes on the fly when resolving transitive
On 05/27/2011 11:44 AM, Mark Struberg wrote:
It's about
1.0
vs
1.0-RC (Release Candidate)
vs
1.0-MR (Maintenance Release)
right?
Yes. RC is recognized by Maven 3 as earlier than GA (or no qualifier).
MR is not recognized by Maven 3 and is assumed to be later than GA.
I
Hi Stephen,
I accidentally raw your message and noticed you need to shade
commons-* stuff; I don't know if it could help for your purposes, but
I suggest you jarjar'ing[1] commons-* jars via the proposed plugin
because you can even relocate classes inside packages and really avoid
any kind of
hi simo!
the maven-shade-plugin can do the same thing:
http://maven.apache.org/plugins/maven-shade-plugin/
LieGrue,
strub
--- On Fri, 5/27/11, Simone Tripodi simonetrip...@apache.org wrote:
From: Simone Tripodi simonetrip...@apache.org
Subject: Re: svn commit: r1127446 - in
yeah m-shade-p was my plan anyway!
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 27 May 2011 22:14, Mark Struberg strub...@yahoo.de wrote:
hi simo!
the
18 matches
Mail list logo
