Igor, I can come up with three possible solutions which one I prefer.
1) Unspecified order plugins are all given highest precedence; specified
plugins come after.
2) Unspecified order plugins are all given lowest precedence; specified
plugins come before.
3) Unspecified order plugins are given a d
Good question. I haven't thought of that. In all the examples presented
thus far, the developer had control over all the executions and
explicitly ordered them. This won't be the case all the time. What happens
when you mix ordering and unspecified?
Cheers,
Paul
On Thu, Jun 5, 2014 at 9:12 AM,
Mojo executions bound to in packaging type lifecycle mapping have fixed
"default-" ids. To continue my Tycho pack200 example, I will need
to insert jarsigner between pack200:normalize and pack200:pack goals.
If pack200:normalize and pack200:pack goals are bound to the default
lifecycle, can you ex
I actually think the attributes are perfectly fine and won't interfere with
anything. The attributes were always intended to be metadata about the elements
and I think the use of instructing the core about how to order the executions
falls into that category of use.
On Jun 5, 2014, at 9:52 AM,
After giving it some more thought, I think interpolating the is less
disruptive than a new attribute. I am sure once POM 5 exists, there will be
an official way.
Lastly, I am not not a fan of the "step-#" naming because it's a prefix but
it is more descriptive; I would prefer to just simply allow
