Hi,
I'd like to write a custom packaging to add some javascript-tooling. As part of
this, it should be packaged with maven-assembly-plugin.
I wrote the components.xml and lifecycle.xml mapping the package-phase to
org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single and tried to
configure it in lifecycle.xml:
<lifecycle>
<id>jszip</id>
<phases>
<phase>
<id>package</id>
<executions>
<execution>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
<configuration>
<descriptorRefs>
<descriptorRef>jszip</descriptorRef>
</descriptorRefs>
</configuration>
</phase>
</phases>
</lifecycle>
According to lifecycle-1.0.0.xsd this is valid.
When I try to package my test-project, the new lifecycle is successfully used,
but I get an error because no assembly descriptor found. If I configure the
assembly-plugin this way in my project-pom (including the plugins additional
<dependencies>) the assembly-descriptor is successfully retrieved from the
repository.
Debugging maven-core and maven-plugin, it looks like nothing of my
configuration of maven-assembly-plugin is applied (breakpoint in
DefaultLifecycleExecutor, viewing mojoExecution for lifecycleMapping "package",
the configuration of mojoExecution is null and mojoConfiguration of
mojoDescriptor contains lots of variables (${descriptor}, etc., but nothing of
descriptorRefs)).
Is it not possible (at least with Maven 2.2.1) to configure a lifecycle-mapped
plugin as part of the lifecycle-definition?
Thanks in advance,
Stefan
--
NEU: FreePhone - kostenlos mobil telefonieren und surfen!
Jetzt informieren: http://www.gmx.net/de/go/freephone
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
