I'm ok too, but I don't have the time to work on it.
Emmanuel
Olivier Lamy a écrit :
Hi,
Agree to start processing this.
If I can help I will.
--
Olivier
2007/12/20, Brett Porter [EMAIL PROTECTED]:
So, what's next?
This seems generally in favour - now might be a good time to get
started
i've played with the DefaultLifecycleExecutor and DefaultPluginManager a bit
and tried to separate the preparation phase from the actual mojo executions.
The preparations seem to attribute to astonishing 90% of the build
execution.
See
Which of the declared dependencies is the problem?
Did you fix the problem there too?
[EMAIL PROTECTED] wrote:
Author: olamy
Date: Wed Dec 19 14:32:51 2007
New Revision: 605723
URL: http://svn.apache.org/viewvc?rev=605723view=rev
Log:
add dependency on p-u which it's used but not declared
No issue fixed here.
My only concerns was to add a dependency on p-u because p-u is used
directly in some classes of the project.
I know p-u comes here by transitivity from the other dependencies.
It's just to declare something we use directly in the project.
Sure not mandatory, do you want I
The checkMissingArtifactsInReactor method is only used when the plugin is
an aggregator.
The eclipse plugin may fail when it ask for execution of
phase=generate-sources, as some plugins requires dependency resolution
(sample : an ear having dependency on a war). But in this case, the
execution is
On 22 Dec 07, at 4:49 AM 22 Dec 07, nicolas de loof wrote:
The checkMissingArtifactsInReactor method is only used when the
plugin is
an aggregator.
The eclipse plugin may fail when it ask for execution of
phase=generate-sources, as some plugins requires dependency resolution
(sample : an
On 22 Dec 07, at 1:02 AM 22 Dec 07, Milos Kleint wrote:
i've played with the DefaultLifecycleExecutor and
DefaultPluginManager a bit and tried to separate the preparation
phase from the actual mojo executions. The preparations seem to
attribute to astonishing 90% of the build execution.
On Dec 22, 2007 5:17 PM, Jason van Zyl [EMAIL PROTECTED] wrote:
On 22 Dec 07, at 1:02 AM 22 Dec 07, Milos Kleint wrote:
i've played with the DefaultLifecycleExecutor and
DefaultPluginManager a bit and tried to separate the preparation
phase from the actual mojo executions. The
If I can get some time I might look at it as well. This wouldn't
necessarily be a bad thing if it can tell you all of the errors after
preparing the projects.
Milos Kleint wrote:
The build doesn't fail fast now in some cases. It will prepare all the 20
project's lifecycles, perform dependency
On 22 Dec 07, at 9:09 AM 22 Dec 07, Milos Kleint wrote:
On Dec 22, 2007 5:17 PM, Jason van Zyl [EMAIL PROTECTED] wrote:
On 22 Dec 07, at 1:02 AM 22 Dec 07, Milos Kleint wrote:
i've played with the DefaultLifecycleExecutor and
DefaultPluginManager a bit and tried to separate the
On 22 Dec 07, at 9:55 AM 22 Dec 07, Ralph Goers wrote:
If I can get some time I might look at it as well. This wouldn't
necessarily be a bad thing if it can tell you all of the errors
after preparing the projects.
There are probably things we can know before project collection, like
Seems I have missed some interesting threads on the dev list !
What is this build plan ?
Is this related to http://docs.codehaus.org/display/MAVEN/Toolchains
I didn't find proposal / description of this mechanism on
http://docs.codehaus.org/display/MAVEN/Home
Nico.
2007/12/22, Jason van Zyl
My bad, I misunderstood your svn comment. If plexus-utils is used
directly by the classes it should be a dependency.
Olivier Lamy wrote:
No issue fixed here.
My only concerns was to add a dependency on p-u because p-u is used
directly in some classes of the project.
I know p-u comes here by
+1 I still think this is a great idea...
On Dec 22, 2007 6:34 AM, Emmanuel Venisse [EMAIL PROTECTED] wrote:
I'm ok too, but I don't have the time to work on it.
Emmanuel
Olivier Lamy a écrit :
Hi,
Agree to start processing this.
If I can help I will.
--
Olivier
2007/12/20,
14 matches
Mail list logo
