Brian Topping wrote:
Hi,
there's a bug in maven 2.0.4 for the plugin ordering. It uses a Set.
This is fixed in SVN (LinkedHashSet that preserves ordering), and will
be available in 2.0.5 and 2.1.
Thinking about this, it may be a too harsh limitation of M2: plugins are meant
to
be independent of eachother, so you really shouldn't have to execute several
plugins
to achieve 1 task, or even set up something specific for another plugin.
Looking at the assembly/debian plugin problem, a solution could be
to support the debian packaging in the assembly plugin, perhaps by
specifying a <dependency> in the assembly plugin declaration; the dependency
would
have a components.xml for a .deb archiver. I'm guessing there's a lot more to
it though.
Another way would be to fix/extend the assembly plugin to be able to point to the
original locations used by the assembly plugin to create the structure.
I agree that this poses some limitations (no dependency-unpack calls)
and you probably have other structures like this for other plugins.
Maybe the lifecycle should be extended with a prepare-package phase before
package,
and possibly a process-package phase afterwards?
-- Kenney
Greetings,
I'm having a problem using assembly plugin to create a work directory
for another plugin (the debian plugin). I started off by putting these
plugins in different phases to force the order, but as the project has
evolved, this has become unworkable because there are no open phases
left that are a good place to put these different plugins. The two
plugins are ordered as they should be run in the POM file, but they
execute in the opposite order.
As a really flimsy hack, I tried reversing the order of the two, but
they still execute in the wrong order.
I'm not at all convinced that the right way to be doing this is to make
a plugin that executes two plugins.
It seems like the right thing to be doing here is for the <plugin>
elements to have an <order> element, but it would require a different
POM schema. Not easy to do.
Thoughts?
Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
