I found a solution but for me it's more a workaround that a feature.
I created a custom lifecycle AND a forked lifecycle.
component.xml :
org.apache.maven.lifecycle.mapping.LifecycleMapping
grails-app
org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping
In debug mode I can see that my settings defined in the lifecycle.xml
aren't used :
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:copy-dependencies'
-->
[DEBUG] (f) excludeTransitive = false
[DEBUG] (s) failOnMissingClassifierArtifact = true
[DEBUG] (s
Hey Jason,
I had a look at it, and I tried to create a lifecycle.xml descriptor
but it doesn't do what I want.
In my component.xml I have :
org.apache.maven.lifecycle.mapping.LifecycleMapping
grails-app
org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping
On 23 Aug 07, at 8:46 AM 23 Aug 07, Arnaud HERITIER wrote:
Is it possible with a META-INF/maven/lifecycle.xml instead of
META-INF/plexus/component.xml.
I don't find a documentation about all of this. I need your help.
Look at the clover plugin for an example.
Thx
Arnaud
On 23/08/07, Arn
Is it possible with a META-INF/maven/lifecycle.xml instead of
META-INF/plexus/component.xml.
I don't find a documentation about all of this. I need your help.
Thx
Arnaud
On 23/08/07, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Hi Guys,
>
> In a custom lifecycle I would like to use the depend
Hi Guys,
In a custom lifecycle I would like to use the dependency plugin (the
copy-dependencies mojo to be exact) but I want to set some of its
parameters (outputDirectory, excludedScopes).
Can I?
How ?
--
..
Arnaud HERITIER