Curious,
I only get 2 failures and one error (against 2.0.7 without the patch):
Results :
Failed tests:
testit0045(org.apache.maven.integrationtests.MavenIT0045Test)
testit0046(org.apache.maven.integrationtests.MavenIT0046Test)
Tests in error:
testit0104(org.apache.maven.integrationtests.
This test is definitely flakey. I was able to fix it in eclipse unit
testing but then it failed again on core.
Build the wagon and place it in maven2/lib. Then edit the m2.conf file:
"main is org.apache.maven.cli.MavenCli from plexus.core
set maven.home default ${user.home}/m2
[plexus.core]
load
I've moved this discussion off JIRA.
Brian,
I have just checked out the core-integration-testing/trunk and was just
trying to execute the core-integration-tests myself. How did you execute
them for Maven-2.0.7 with the WAGON-73 patch applied?
Did you need to change something in the core-integrat
Yep, as others have said we do recognise this. Thanks for raising it
as an issue though, as that sort of frustration is definitely an
issue in growing the community here.
I think the way most of us prefer to work is to run through a set of
related patches at a time, so really the reason for
+1
The licenses and signatures are all in place, and it appears to be
running fine.
I tested the plexus-runtime version and it deleted 2/3 of my
repository - just like I asked it to :)
Cheers,
Brett
On 07/08/2007, at 2:23 AM, Maria Odea Ching wrote:
Hi All,
Archiva 1.0-beta-1 is now r
On 7 Aug 07, at 12:43 AM 7 Aug 07, William Ferguson wrote:
Thanks Jason.
I appreciate that everyone on the list has a day job too, but it *is*
very frustrating to report an issue, document it well, provide test
cases and a patch and have it sit around without any visible action
being taken on
>If I knew the the bug that was really annoying me was
>going to get priority if I put in the extra time to provide a testcase
>and a fix, I'd be more inclined to spend the time.
Hi William,
I'm sorry to see we have frustrated you with your issue. Please be
assured that although it doesn't seem li
Emmanuel is French!?!?!?!?! :)
On 8/6/07, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I already posted this to the users@ list, but I thought some folk
> here might be more particularly interested in what Emmanuel had to
> say when we talked recently: http://www.devzuz.org/?q=node/12.
Thanks Jason.
I appreciate that everyone on the list has a day job too, but it *is*
very frustrating to report an issue, document it well, provide test
cases and a patch and have it sit around without any visible action
being taken on it. I was kind of hopeful that this issue would have been
resol
Thanks Arnaud. I wasn't aware.
I'll direct my request there.
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Monday, 6 August 2007 4:21 PM
To: Maven Developers List
Subject: [***POSSIBLE SPAM***] - Re: Please apply the patch for WAGON-73
- Email has different SMTP
Updating to 0.0.10 or 0.0.11 version resolved the problem.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 01, 2007 4:05 PM
To: dev@maven.apache.org
Subject: M2Eclipse plugin issue.
Hi,
I'm using Maven 2.0 Integration (0.0.9) plugin in my E
On Aug 6, 2007, at 9:48 AM, Jason van Zyl wrote:
We can set you up at the mojo project if you want a place to work
on it.
I'm open to that. It would have been nice to stay within the ASF
subversion repo since we could "svn cp" the maven-idea-plugin and
maintain the history of how the
On Aug 6, 2007, at 6:24 PM, Jason van Zyl wrote:
On 6 Aug 07, at 9:36 AM 6 Aug 07, Jason Dillon wrote:
Any thoughts on how things might work if the snapshot update bits
where a manual process? So that you have to run mvn with some
flag to pull in new snapshot artifacts, and perhaps anoth
On 6 Aug 07, at 9:36 AM 6 Aug 07, Jason Dillon wrote:
Any thoughts on how things might work if the snapshot update bits
where a manual process? So that you have to run mvn with some flag
to pull in new snapshot artifacts, and perhaps another interactive
flag to allow only specific snapsho
We can set you up at the mojo project if you want a place to work on it.
On 6 Aug 07, at 11:07 AM 6 Aug 07, Jason Dillon wrote:
I don't actually use XCode, but I am an avid mac fan and lover, as
well as crack smoker... and I would love to see Maven help support
XCode development anywhere pos
On 6 Aug 07, at 12:18 AM 6 Aug 07, William Ferguson wrote:
Come on guys.
The patch is the addition of just 2 return statements.
There's really not much to verify here.
And 2 additional (simple) test cases have been provided.
Surely that in itself is a good thing to add to the code base.
Now t
Hi Brett,
Nice to meet you :) I hadn't seen maven-jar-shared but it looks great, I
will definitely have a look at it. Using the same logic would be great.
Aardvark seems to address the mavenization of the build system of a project
built with maven 1 or ant (the automation of such a process is a v
On 06/08/2007, at 7:21 PM, Jason Dillon wrote:
This is per-project though isn't it? Anyway to only get that
change applied for my local workspace?
define it in settings.xml, but that'll still be per repository-id.
You could set up your own repo proxy with this config and mirrorOf *
if yo
Hi,
I'm wondering if anyone was working on sharing the resources filtering
capabilities. Lots of plugin actually use this (war, ear, assembly,
dependency).
I'd like to know if there is any way to exclude some token explicitly
when filtering. Let's say I have something like ${project.artifactId}
-
This is per-project though isn't it? Anyway to only get that change
applied for my local workspace?
Can you think of any pitfalls to using a policy of never?
--jason
On Aug 6, 2007, at 12:45 AM, Brett Porter wrote:
in your :
never
then:
mvn -U ...
(no it's not interactive, that's
On Aug 6, 2007, at 12:48 AM, Stephane Nicoll wrote:
Well I guess you should change the update policy instead. SNAPSHOTs is
a crucial concept for us: it allows to continuously integrate our
components, test them, etc.
Yup, it is for me too... I just need to have more control over when
it integ
I don't actually use XCode, but I am an avid mac fan and lover, as
well as crack smoker... and I would love to see Maven help support
XCode development anywhere possible.
Cheers,
--jason
On Aug 2, 2007, at 9:12 PM, Curt Arnold wrote:
I've been working on generating XCode project files for
Well I guess you should change the update policy instead. SNAPSHOTs is
a crucial concept for us: it allows to continuously integrate our
components, test them, etc.
If your build break way,way,way,... to much it might be worse if you
disable snapshots resolution. Anyway, update policy is the way t
in your :
never
then:
mvn -U ...
(no it's not interactive, that's a feature request)
Cheers,
Brett
On 06/08/2007, at 5:36 PM, Jason Dillon wrote:
Any thoughts on how things might work if the snapshot update bits
where a manual process? So that you have to run mvn with some flag
to
Any thoughts on how things might work if the snapshot update bits
where a manual process? So that you have to run mvn with some flag
to pull in new snapshot artifacts, and perhaps another interactive
flag to allow only specific snapshots to be updated (with some
relatively smart warning/su
Hi,
I am unable to set the checksumPolicy in my settings.xml file.
To reproduse the bug, please to the following using maven 2.0.7:
Use the following settings.xml file:
true
never
fail
26 matches
Mail list logo
