+1. I tried this out and the output is much better than what we
currently have:
Summary view:
Build Plan:
1. org.apache.maven.plugins:maven-clean-plugin:2.1:clean [executionId:
default]
2. org.apache.maven.plugins:maven-plugin-plugin:2.2:descriptor
[executionId: def
ault]
3. org.apache.maven.plugins:maven-resources-plugin:2.2:resources
[executionId: d
efault]
4. org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
[executionId: de
fault]
5. org.apache.maven.plugins:maven-resources-plugin:2.2:testResources
[executionI
d: default]
6. org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile
[executionId
: default]
7. org.apache.maven.plugins:maven-surefire-plugin:2.3:test [executionId:
default
]
8. org.apache.maven.plugins:maven-jar-plugin:2.1:jar [executionId:
default]
9.
org.apache.maven.plugins:maven-plugin-plugin:2.2:addPluginArtifactMetada
ta [e
xecutionId: default]
10. org.apache.maven.plugins:maven-install-plugin:2.1:install
[executionId: defa
ult]
Detailed view:
Project:
org.apache.maven.plugins:maven-lifecycle-plugin:maven-plugin:1.0-SNAPSH
OT
Tasks: clean,install
Build Plan:
1. org.apache.maven.plugins:maven-clean-plugin:2.1:clean [executionId:
default]
Origin: default lifecycle
Configuration:
null
2. org.apache.maven.plugins:maven-plugin-plugin:2.2:descriptor
[executionId: def
ault]
Origin: packaging: maven-plugin
Configuration:
null
-----Original Message-----
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Friday, March 16, 2007 12:52 PM
To: Maven Developers List
Subject: [vote] Merge 2.1-lifecycle-refactor branch back to maven trunk
Hi everyone,
I've performed a fairly significant refactoring of the lifecycle
executor on
the 2.1-lifecycle-refactor branch. The changes allow Maven to construct
a
build plan before execution begins in earnest, which contains all of the
mojos and their configurations and is then rendered to a List for
iteration
and execution.
This opens up a whole new world of possibility for controlling builds,
not
to mention build-process debugging and discovery.
I've run the integration tests on this branch, and it seems that
everything
is working well. I'd like to merge this branch back to trunk, but since
it's
such a large refactor, I thought it appropriate to vote on it first, in
an
effort to help us maintain a stable trunk.
I've parked binaries, javadocs (of maven-core, where the big changes
are),
and two design PNG images out here:
http://people.apache.org/~jdcasey/maven-drops/2.1-lifecycle-refactor
Also, if you want to see the new build plan in action, install the
lifecycle
plugin:
http://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-lifecy
cle-plugin
and run the following command with the binaries above:
mvn lifecycle:build-plan -Dtasks=clean,install
If you'd like to see the configurations for the mojos, use this:
mvn lifecycle:build-plan -Dtasks=clean,install -DextendedInfo=true
Please peruse and let me know what you think. I'll give it 72h; please
vote
+1/+0/-1.
Here's my +1.
Thanks,
John
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
