More on this.
With maven 2.0.9 here is the 'classpath' constructed by maven to jaxws :
Maven 2.0.9
[DEBUG] Configuring mojo 'org.codehaus.mojo:jaxws-maven-plugin:1.10:wsgen' --
[DEBUG] (f) destDir = C:\Documents and
Settings\gomezhe\Bureau\sample-wsgen\target\classes
[DEBUG] (f) extension =
Hi,
I´m running a Ubuntu Hardy instalation with a dual core 6700 4gig ram.
How long were you thinking of making the test?
If you pass me the pre configured hudson instance (via ftp or other means) I
can let it run on my pc.
Regards,
Gerrit Jansen van Vuuren
On 7/9/08, Jason van Zyl [EMAIL
John,
I am assuming it's a mistake that you are directly using a shaded
class in the FileProfileActivator? It was never intended that any
source code actually import processed classes directly. There seems to
be shaded bits all along the dependency chain now which was never my
original
John,
I would just put the separated plexus utils in new packages. That
shading along the way is going to be a nasty problem. Importing
processed/shaded classes can only be a recipe for trouble.
On 10-Jul-08, at 7:09 AM, Jason van Zyl wrote:
John,
I am assuming it's a mistake that you
A long time back i discovered that if you have the same target output for
eclipse and maven you end up with broken shit all over the place, intemittent
errors. All really unpleasant.
The default settings for eclipse:eclipse and eclipse:m2eclipse set the outputs
to the same. Does this actually
I tried to build the latest maven 2.1 from trunk with mvn install but
it still failed in tests.
What should be done to get a build of maven 2.1 ?
I need it to track a classloader issue with jaxws-maven-plugin even if
it seems to be a general problem with the system scope.
Regards and thanks for
We've discussed this subject on m2e dev list a lot recently and I
believe the conclusion is that both collocated and separate output
folders cause problems for some projects and development styles, for
the lack of a better word.
For example, I mostly work with maven core and various maven
Henri,
Here's the most recent build:
http://ci.sonatype.org/view/Maven%202.1x/job/maven-2.1.x-bootstrap/ws/trunk/maven-distribution/target/
On 10-Jul-08, at 10:02 AM, Henri Gomez wrote:
I tried to build the latest maven 2.1 from trunk with mvn install but
it still failed in tests.
What
Igor Fedorenko wrote:
We've discussed this subject on m2e dev list a lot recently
Just to give the pointer:
http://docs.codehaus.org/display/M2ECLIPSE/Separate+Eclipse+and+Maven+output+folders
Benjamin
-
To unsubscribe,
Well
I 'll put your maven 2.1 build to our Hudson instance :)
2008/7/10 Jason van Zyl [EMAIL PROTECTED]:
Henri,
Here's the most recent build:
http://ci.sonatype.org/view/Maven%202.1x/job/maven-2.1.x-bootstrap/ws/trunk/maven-distribution/target/
On 10-Jul-08, at 10:02 AM, Henri Gomez
I'm not sure what you're talking about, but I'll look into it.
Jason van Zyl wrote:
John,
I would just put the separated plexus utils in new packages. That
shading along the way is going to be a nasty problem. Importing
processed/shaded classes can only be a recipe for trouble.
On
If you have 2.0.x installed you need to bootstrap.
It builds fine for me now with 2.0.9, we've never needed to bootstrap to
build 2.1 before, so what's different now?
If we can't trust Maven to build our own applications here, then we have
a serious problem IMO that needs to be fixed. Maven 2.1
I found two references to classes in Maven like:
import hidden.org.codehaus.plexus...
Maybe your refactoring stuff grabbed hold of it.
If that wasn't intentional I'll check in my changes.
On 10-Jul-08, at 10:34 AM, John Casey wrote:
I'm not sure what you're talking about, but I'll look into
It builds fine for me now with 2.0.9, we've never needed to bootstrap to
build 2.1 before, so what's different now?
You got it works with 2.0.9 ?
Just with mvn install ?
If we can't trust Maven to build our own applications here, then we have
a serious problem IMO that needs to be fixed.
On 10-Jul-08, at 11:01 AM, Brian E. Fox wrote:
If you have 2.0.x installed you need to bootstrap.
It builds fine for me now with 2.0.9, we've never needed to
bootstrap to
build 2.1 before, so what's different now?
If you ever change APIs where the JARs in the distribution come first
It looks like we've got a good set of issues fixed for 2.0.10 and things
are starting to stabilize. We'll start publishing 2.0.10 RC's as early
as today. I think we worked out a good process with the 2.0.9 release
and we should continue in that direction. The basic principles are:
1) we
It builds fine for me now with 2.0.9, we've never needed to bootstrap
to
build 2.1 before, so what's different now?
You got it works with 2.0.9 ?
Yes.
Just with mvn install ?
Yes.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
I always bootstrap.
On 10-Jul-08, at 11:12 AM, Henri Gomez wrote:
It builds fine for me now with 2.0.9, we've never needed to
bootstrap to
build 2.1 before, so what's different now?
You got it works with 2.0.9 ?
Just with mvn install ?
If we can't trust Maven to build our own
It builds fine for me now with 2.0.9, we've never needed to
bootstrap to
build 2.1 before, so what's different now?
If you ever change APIs where the JARs in the distribution come first
on the classpath you need to start from scratch. Most of the time we
don't do that so it never
On Thu, Jul 10, 2008 at 5:14 PM, Brian E. Fox [EMAIL PROTECTED] wrote:
1) we will stop to fix any regressions between 2.0.9 and 2.0.10
What's the rationale for this?
--
Look, that's why there's rules, understand? So that you think before
you break 'em.
-- (Terry Pratchett, Thief
Not intentional at all. I have two of the classes revised here to use
plexus interpolation directly, but if you've got the changes on trunk
and 2.0.x already, I'll let you commit it.
-john
Jason van Zyl wrote:
I found two references to classes in Maven like:
import
I think what he intended to say is we're going to do a code freeze and
only fix regressions that are exposed by testing of the RCs.
-john
Jochen Wiedmann wrote:
On Thu, Jul 10, 2008 at 5:14 PM, Brian E. Fox [EMAIL PROTECTED] wrote:
1) we will stop to fix any regressions between
Jason van Zyl wrote:
import hidden.org.codehaus.plexus...
Side note:
The Checkstyle rule IllegalImport [0] could help to ban this.
Benjamin
[0] http://checkstyle.sourceforge.net/config_imports.html#IllegalImport
-
To
1) we will stop to fix any regressions between 2.0.9 and 2.0.10
What's the rationale for this?
I meant stop the current RC to fix the issue and then recut the next RC. We
won't respin for other random issues.
In the process couldn't we create a 2.0.10-RC branch where we fix issues
discovered in RCs.
At the end we create the final release from this branch and we merge changes
in the 2.0.x trunk.
We that we are sure that no other commit on 2.0.x can be added by error in
the RC process.
(it's just a
The default settings for eclipse:eclipse and eclipse:m2eclipse set the
outputs
to the same. Does this actually work for people? Maybe locking on windows
actually make a positive impact finally?
Yes, it works well. We have maven projects for 3 years (maven 1.x and maven
2) with developing
I was thinking the same thing the other day. I think this is a good idea.
-john
Arnaud HERITIER wrote:
In the process couldn't we create a 2.0.10-RC branch where we fix issues
discovered in RCs.
At the end we create the final release from this branch and we merge changes
in the 2.0.x trunk.
We
Sure, we can do that.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2008 1:55 PM
To: Maven Developers List
Subject: Re: Preparing for 2.0.10 RC1
I was thinking the same thing the other day. I think this is a good
idea.
-john
Arnaud HERITIER
Done. The branch is:
https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.10-RC
-j
Brian E. Fox wrote:
Sure, we can do that.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2008 1:55 PM
To: Maven Developers List
Subject: Re:
Is it possible to shade to something that would be illegal to use
directly, like appending $shade to the class name, and still have it
all work?
- Brett
On 11/07/2008, at 1:08 AM, Jason van Zyl wrote:
I found two references to classes in Maven like:
import hidden.org.codehaus.plexus...
Issue Subscription
Filter: Design Best Practices (28 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
What version of Maven is being used to execute these builds? I can't
see why it successfully downloads two artifacts then fails with a
resolution error on them.
- Brett
On 11/07/2008, at 3:01 PM, Hudson wrote:
See http://ci.sonatype.org/job/maven-core-integration-testing/109/changes
What will be the procedure going forward to upgrade super POM dependencies?
Before the RC is cut, I'd like to see a task-type ticket open that
specifically deals with the upgrade. It will be good for tracking purposes.
I hope this is done per release.
Paul
33 matches
Mail list logo
