I think the component.xml is correct (at end) - it certainly looks the
same as the plexus examples.
My project that uses this plugin works entirely correctly, *unless* it
is a part of a multiproject build, in which case it uses the wrong
extension. I don't know why this would be the case unless
Please file a JIRA on the multi-project vs single project, with some
details, we'll look into it. It could be a bug.
That said, I think some people have been contributing similar
functionality to the war plugin itself - might be worth investigating.
- Brett
On 11/24/05, Nigel Magnay [EMAIL
Ah - I have found out why I'm having trouble - my configuration looks like
configuration
extensionwar/extension
typeuberwar/type
/configuration
This works correctly when I build the project that uses the plugin.
However, if the project that uses the plugin is built as a
I'm losing track of this in all the bits and pieces as to what you really have.
I'd suggest looking at the Plexus plugin and comparing the
components.xml to your own:
http://svn.plexus.codehaus.org/trunk/plexus-maven-plugin/
HTH,
Brett
On 11/24/05, Nigel Magnay [EMAIL PROTECTED] wrote:
Ah - I
I have an 'uberwar' mojo; it's components.xml has a lifecyclemapping
and an artifacthandler definition, both with the role-hint of uberwar.
My project that uses this mojo has a pom.xml with
packaginguberwar/packaging
The lifecycle is working correctly, my mojo is being called in the
packaging
As I said, your type should be uberwar - not war (it needs to match
the role-hint, as
stated in the docs).
On 11/18/05, Nigel Magnay [EMAIL PROTECTED] wrote:
I have an 'uberwar' mojo; it's components.xml has a lifecyclemapping
and an artifacthandler definition, both with the role-hint of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You're defining this components.xml in a plugin, right? Do you have
extensionstrue/extensions defined in the plugin reference within
your plugin-user POM? If not, it will use a default artifact handler
that has the same type as your packaging, and
Yep - I'm pretty sure it's reading it as there is also a
LifecycleMapping which is being used correctly.
Are the private member variables supposed to get read set by some
persistence mechanism from the configuration node ?
On 11/17/05, John Casey [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, the private member vars are injected with values from the
configuration. That's how plexus works by default (plexus is the
underlying container Maven uses).
So, you have a POM with packaginguberwar/packaging, and it's setting
the extension to
Your type should be uberwar (it needs to match the role-hint, as
stated in the docs).
- Brett
On 11/18/05, Nigel Magnay [EMAIL PROTECTED] wrote:
Hello - I have been trying to follow the configuration for
ArtifactHandlers - I have in my components.xml
component
10 matches
Mail list logo
