You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by Maczka Michal <mi...@imtf.ch> on 2005/02/16 10:31:05 UTC
RE: cvs commit: maven-components/maven-core/src/test/java/org/apa
che/maven/plugin PluginParameterExpressionEvaluatorTest.java
> -----Original Message-----
> From: jvanzyl@apache.org [mailto:jvanzyl@apache.org]
> Sent: Wednesday, February 16, 2005 8:17 AM
> To: maven-components-cvs@apache.org
> Subject: cvs commit:
> maven-components/maven-core/src/test/java/org/apache/maven/plugin
> PluginParameterExpressionEvaluatorTest.java
>
Hey this looks good!
> + <phases>
> + <!-- 1 -->
> + <phase>
> + <id>generate-sources</id>
> + </phase>
> + <!-- 2 -->
> + <phase>
> + <id>process-sources</id>
> + </phase>
> + <!-- 3 -->
> + <phase>
> + <id>generate-resources</id>
> + </phase>
> + <!-- 4 -->
> + <phase>
> + <id>process-resources</id>
> + <goal>resources:resources</goal>
> + </phase>
> + <!-- 5 -->
> + <phase>
> + <id>compile</id>
> + <goal>compiler:compile</goal>
> + </phase>
> + <!-- 6 -->
> + <phase>
> + <id>process-classes</id>
> + </phase>
> + <!-- 7 -->
> + <phase>
> + <id>generate-test-sources</id>
> + </phase>
> + <!-- 8 -->
> + <phase>
> + <id>process-test-sources</id>
> + </phase>
> + <!-- 9 -->
> + <phase>
> + <id>generate-test-sources</id>
> + </phase>
> + <!-- 10 -->
> + <phase>
> + <id>process-test-resources</id>
> + <goal>resources:testResources</goal>
> + </phase>
> + <!-- 11 -->
> + <phase>
> + <id>test-compile</id>
> + <goal>compiler:testCompile</goal>
> + </phase>
> + <!-- 12 -->
> + <phase>
> + <id>test</id>
> + <goal>surefire:test</goal>
> + </phase>
> + <!-- 13 -->
> + <phase>
> + <id>package</id>
> + <goal>jar:jar</goal>
> + </phase>
> + <!-- 14 -->
> + <phase>
> + <id>install</id>
> + <goal>jar:install</goal>
> + </phase>
> + <!-- 15 -->
> + <phase>
> + <id>deploy</id>
> + <goal>jar:deploy</goal>
> + </phase>
> + </phases>
> + <!-- END SNIPPET: lifecycle -->
> + </configuration>
> + </component>
> </components>
> </component-set>
>
I have still some "control" questions to validate the idea :
- How we are going to support deployment of "exploded" j2ee artifacts?
I mean exploded wars, ejbs, ears etc. Specifically I use very frequently
in m1 "war:webapp" goal,
which is assembling the web application directly in the location which
is visible for servlet container.
I don't see a phase where this might fall into. I feel that this might be
something for such funtionality around phase #6.
- Will we have other lifecycles the this one? E.g for release process, web
site generation, integration tests?
- In m1 some plugins have their own clean goal (e.g war:clean). I wonder if
such contribution to clean phase (which is not present in this life cycle)
can be somehow supported.
regards
Michal
Re: cvs commit:
maven-components/maven-core/src/test/java/org/apache/maven/plugin
PluginParameterExpressionEvaluatorTest.java
Posted by Jason van Zyl <ja...@maven.org>.
On Wed, 2005-02-16 at 11:47 +0100, Emmanuel Venisse wrote:
> > Hey this looks good!
>
> I think there are some corrections to do.
> For package, install and deploy, we must use the pom type and not always the
> jar plugin
>
> for war :
> =>package : war:war
> =>install : war:install
> =>deploy : war:deploy
>
> for pom :
> =>install : pom:install
> =>deploy : pom:deploy
>
> Is it possible to use #pom.type instead of jar.
> Is it possible to redefine phases in pom (like package run my specific goal)
It's coming, simplest thing first. I just wanted to get the bootstrap
working as the first step. Next step is getting it0008, and it0009
working again where a plugin configuration replaces what a pre/post goal
did and then I'll start wiring the artifact handlers into the life
cycle.
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
Re: cvs commit: maven-components/maven-core/src/test/java/org/apache/maven/plugin PluginParameterExpressionEvaluatorTest.java
Posted by Emmanuel Venisse <em...@venisse.net>.
> Hey this looks good!
I think there are some corrections to do.
For package, install and deploy, we must use the pom type and not always the
jar plugin
for war :
=>package : war:war
=>install : war:install
=>deploy : war:deploy
for pom :
=>install : pom:install
=>deploy : pom:deploy
Is it possible to use #pom.type instead of jar.
Is it possible to redefine phases in pom (like package run my specific goal)
Emmanuel
>
>
> > + <phases>
> > + <!-- 1 -->
> > + <phase>
> > + <id>generate-sources</id>
> > + </phase>
> > + <!-- 2 -->
> > + <phase>
> > + <id>process-sources</id>
> > + </phase>
> > + <!-- 3 -->
> > + <phase>
> > + <id>generate-resources</id>
> > + </phase>
> > + <!-- 4 -->
> > + <phase>
> > + <id>process-resources</id>
> > + <goal>resources:resources</goal>
> > + </phase>
> > + <!-- 5 -->
> > + <phase>
> > + <id>compile</id>
> > + <goal>compiler:compile</goal>
> > + </phase>
> > + <!-- 6 -->
> > + <phase>
> > + <id>process-classes</id>
> > + </phase>
> > + <!-- 7 -->
> > + <phase>
> > + <id>generate-test-sources</id>
> > + </phase>
> > + <!-- 8 -->
> > + <phase>
> > + <id>process-test-sources</id>
> > + </phase>
> > + <!-- 9 -->
> > + <phase>
> > + <id>generate-test-sources</id>
> > + </phase>
> > + <!-- 10 -->
> > + <phase>
> > + <id>process-test-resources</id>
> > + <goal>resources:testResources</goal>
> > + </phase>
> > + <!-- 11 -->
> > + <phase>
> > + <id>test-compile</id>
> > + <goal>compiler:testCompile</goal>
> > + </phase>
> > + <!-- 12 -->
> > + <phase>
> > + <id>test</id>
> > + <goal>surefire:test</goal>
> > + </phase>
> > + <!-- 13 -->
> > + <phase>
> > + <id>package</id>
> > + <goal>jar:jar</goal>
> > + </phase>
> > + <!-- 14 -->
> > + <phase>
> > + <id>install</id>
> > + <goal>jar:install</goal>
> > + </phase>
> > + <!-- 15 -->
> > + <phase>
> > + <id>deploy</id>
> > + <goal>jar:deploy</goal>
> > + </phase>
> > + </phases>
> > + <!-- END SNIPPET: lifecycle -->
> > + </configuration>
> > + </component>
> > </components>
> > </component-set>
> >
>
> I have still some "control" questions to validate the idea :
>
>
> - How we are going to support deployment of "exploded" j2ee artifacts?
> I mean exploded wars, ejbs, ears etc. Specifically I use very frequently
> in m1 "war:webapp" goal,
> which is assembling the web application directly in the location which
> is visible for servlet container.
> I don't see a phase where this might fall into. I feel that this might
be
> something for such funtionality around phase #6.
>
>
> - Will we have other lifecycles the this one? E.g for release process, web
> site generation, integration tests?
>
>
> - In m1 some plugins have their own clean goal (e.g war:clean). I wonder
if
> such contribution to clean phase (which is not present in this life cycle)
> can be somehow supported.
>
>
> regards
>
> Michal
>
>
>
>