) because it requires apple
hardware in the license. (who's the monopoly now)
-Original Message-
From: Vincent Siveton [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2008 6:45 PM
To: Maven Developers List
Subject: Vmware (Was: Maven 2.0.10-RC3 - Please Test!)
Hi guys,
2008/7/31 John
List
Subject: Re: Vmware (Was: Maven 2.0.10-RC3 - Please Test!)
if we had a beefy mactel with vmware running on that, then it might be
feasible to have build environments for just about everything but
solaris, I guess...
...and actually, I'm pretty sure even solaris runs on x86
-john
Brian E
Hi John,
With RC-3, Javadoc ITs (MJAVADOC-172 and MJAVADOC-194) failed.
Sounds like an issue in the invoker-plugin (defined as 1.2 in the
pom). Unfortunately, I tried with 1.2.1-snap without success. So it is
probably in the core.
Could you have a glance? Last step before calling a vote ;)
Is there a chance to get maven-2.0.10 running with maven-scm-1.1?
You know, I'd like to see native git support in maven ;)
LieGrü,
strub
--- Vincent Siveton [EMAIL PROTECTED] schrieb am Do, 31.7.2008:
Von: Vincent Siveton [EMAIL PROTECTED]
Betreff: Re: Maven 2.0.10-RC3 - Please Test
We're already started the RC process so only blocking issues and regressions
are being included.
-Original Message-
From: Mark Struberg [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2008 10:28 AM
To: Maven Developers List
Subject: Re: Maven 2.0.10-RC3 - Please Test
Hi Vincent,
I can't even get the javadoc plugin to run on my machine under Maven
2.0.9, not with JDK 1.4 or JDK 1.6...so I'm afraid I'm of little use on
these issues. I can give you some time to distill a failing test case
that I can pursue, if you like...
Let me know. Maybe I'll cut the
check if the CLASSPATH environment variable is set. it blows up
javadoc if it is
Sent from my iPod
On 31 Jul 2008, at 18:06, John Casey [EMAIL PROTECTED] wrote:
Hi Vincent,
I can't even get the javadoc plugin to run on my machine under Maven
2.0.9, not with JDK 1.4 or JDK 1.6...so I'm
support in maven ;)
LieGrü,
strub
--- Vincent Siveton [EMAIL PROTECTED] schrieb am Do,
31.7.2008:
Von: Vincent Siveton [EMAIL PROTECTED]
Betreff: Re: Maven 2.0.10-RC3 - Please Test!
An: Maven Developers List dev@maven.apache.org
Datum: Donnerstag, 31. Juli 2008, 14:36
Hi John,
With RC-3, Javadoc
Would it behoove the Javadoc plugin developers to test for the CLASSPATH
variable? Issue a warning instead of blowing up? I know it's not a plugin
problem, per se, but it obviously leads some people to believe it is.
Paul
On Thu, Jul 31, 2008 at 12:43 PM, Stephen Connolly
[EMAIL PROTECTED]
Hi Paul,
2008/7/31 Paul Benedict [EMAIL PROTECTED]:
Would it behoove the Javadoc plugin developers to test for the CLASSPATH
variable? Issue a warning instead of blowing up? I know it's not a plugin
problem, per se, but it obviously leads some people to believe it is.
The last entry in the
Hi John,
Maybe your pb was related to CLASSPATH as said by Stephen.
FYI I am able to built it with 1.4, 1.5 and 1.6 and mvn 2.0.9 on two
stations and Hudson was happy yesterday.
Unfortunately, with rc3, it's failing on twice.
The twice javadoc ITs seem to not call javadoc goal, and so apidocs
This is not the case on my machine. I've been very careful NOT to set
M2_HOME, JAVA_HOME, or CLASSPATH on my machine. The first two are set
using a mvn delegating script in ~/bin that sets the maven version and
jdk version before calling the real maven script. I've just verified
that CLASSPATH
Hi guys,
2008/7/31 John Casey [EMAIL PROTECTED]:
[SNIP]
BTW, I'm running on OS X.
Maybe a dummy question but do we have in Apache world some Vmware files?
Cheers,
Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
2.0.10-RC3 - Please Test!)
Hi guys,
2008/7/31 John Casey [EMAIL PROTECTED]:
[SNIP]
BTW, I'm running on OS X.
Maybe a dummy question but do we have in Apache world some Vmware files?
Cheers,
Vincent
-
To unsubscribe, e-mail
On 30/07/2008, at 12:01 PM, John Casey wrote:
I think you're misunderstanding me: I was talking about test
coverage within _wagon_ itself. Since wagon is on a separate release
cycle to Maven core, Maven releases have to consume released
versions of wagon. This means 72h of voting and so
Thanks for the time on all of this. I had made a note locally to take a
look at the tests in wagon to see what could be improved once I got
2.0.10 out the door, but you've beaten me to it.
I'll hold off on the RC4 I was about to announce, if you're releasing it
tomorrow, and we can try
I think you're misunderstanding me: I was talking about test coverage
within _wagon_ itself. Since wagon is on a separate release cycle to
Maven core, Maven releases have to consume released versions of wagon.
This means 72h of voting and so forth before releasing a new wagon version.
I
I think moving back to -beta-2 will be much less risky. We can try again
for -beta-3 in 2.0.11 or when it's ready.
-john
Brett Porter wrote:
Hi John,
Unfortunately, I've found that HTTP proxies don't work. I added an
integration test which passes on 2.0.9. I've already fixed the problem
on
On 29/07/2008, at 12:40 AM, John Casey wrote:
I think moving back to -beta-2 will be much less risky. We can try
again for -beta-3 in 2.0.11 or when it's ready.
I'll leave it up to you. I still think it is worth the upgrade, if
only to get proper scp group permission setting available
Do we have a list of exactly what would have to be rolled back?
Brett Porter wrote:
On 29/07/2008, at 12:40 AM, John Casey wrote:
I think moving back to -beta-2 will be much less risky. We can try
again for -beta-3 in 2.0.11 or when it's ready.
I'll leave it up to you. I still think it is
What really concerns me is that this release has been in the wild for
quite awhile now, and this issue is just coming to light. Plenty of
people use proxies, so it's not like it's that shady a corner of the
implementation.
I guess what I'm getting at is I wonder if the test suite for wagon is
I don't think the speed with with beta-3 and beta-4 were done are in
sync with the rigor that's been going into the 2.0.x releases.
I think beta-2 should have been cut as 1.0 and then moved one. Applied
real bug fixes but we did a bunch of things to the API and sweep
changes to
don't think we should move forward with beta-4 until this
happens.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Monday, July 28, 2008 11:59 AM
To: Maven Developers List
Subject: Re: Maven 2.0.10-RC3 - Please Test!
What really concerns me is that this release has been
I tested RC3 on several projects with success.
Note : I don't use http proxy in this environment
cheers
Arnaud
On Fri, Jul 25, 2008 at 11:20 PM, John Casey [EMAIL PROTECTED] wrote:
Hi again,
We've solved all of the issues brought up in response to the 2.0.10-RC2
release candidate, minus
On 28-Jul-08, at 9:04 AM, Jason van Zyl wrote:
I don't think the speed with with beta-3 and beta-4 were done are in
sync with the rigor that's been going into the 2.0.x releases.
Sorry, switched timezones and without coffee. Let me say that again:
I don't think the speed with which
On 28-Jul-08, at 9:09 AM, Arnaud HERITIER wrote:
I tested RC3 on several projects with success.
Note : I don't use http proxy in this environment
Right, changing the functionality of something the vast majority of
people don't use logically means that demographic gets nailed. I think
the trick at this point is to figure out what rolling back to -beta-2
will undo in terms of our JIRA count for the release, and where the
associated code is. I'll get started on this today.
-john
Jason van Zyl wrote:
On 28-Jul-08, at 9:04 AM, Jason van Zyl wrote:
I don't think the speed
On 29/07/2008, at 2:05 AM, Brian E. Fox wrote:
Same here. I think that before we go ahead and put out beta-4, we
should
have significant coverage in Maven Its to capture the integration.
I had already added a number of tests over recent times related to
this. The touch points with Maven
I understand the concerns, but let me try and explain where I'm coming
from.
On 29/07/2008, at 1:58 AM, John Casey wrote:
What really concerns me is that this release has been in the wild
for quite awhile now, and this issue is just coming to light. Plenty
of people use proxies, so it's
Hi John,
Unfortunately, I've found that HTTP proxies don't work. I added an
integration test which passes on 2.0.9. I've already fixed the problem
on Wagon trunk and the test passes with 2.0.10-RC4-SNAPSHOT (not
committed as it would bump wagon to a snapshot).
This leaves the following
On 27-Jul-08, at 12:34 PM, Brett Porter wrote:
Hi John,
Unfortunately, I've found that HTTP proxies don't work. I added an
integration test which passes on 2.0.9. I've already fixed the
problem on Wagon trunk and the test passes with 2.0.10-RC4-SNAPSHOT
(not committed as it would bump
Rollback.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 27, 2008 2:37 PM
To: Maven Developers List
Subject: Re: Maven 2.0.10-RC3 - Please Test!
On 27-Jul-08, at 12:34 PM, Brett Porter wrote:
Hi John,
Unfortunately, I've found that HTTP proxies
This appears to be another permutation of MNG-2739. I've reopened it.
-john
Olivier Lamy wrote:
Hi,
In my settings.xml, I have :
mirror
mirrorOfrec-ap2/mirrorOf
urlhttp://xx.xxx.xxx.xxx:10080/maven2/url
!--idproxy-recap2/id--
/mirror
This causes :
bash-3.00$ mvn
Hi again,
We've solved all of the issues brought up in response to the 2.0.10-RC2
release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we
can take a look at whether this is happening by design, and what
resolution we want to pursue for it).
The issues we've solved for this
Sorry, the URL for RC3 is:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC3/org/apache/maven/apache-maven/2.0.10-RC3
-j
John Casey wrote:
Hi again,
We've solved all of the issues brought up in response to the 2.0.10-RC2
release candidate, minus MNG-3678 (which I've postponed
Hi,
In my settings.xml, I have :
mirror
mirrorOfrec-ap2/mirrorOf
urlhttp://xx.xxx.xxx.xxx:10080/maven2/url
!--idproxy-recap2/id--
/mirror
This causes :
bash-3.00$ mvn validate
[INFO]
[ERROR] FATAL
36 matches
Mail list logo
