The last comment on it seems to be definitive. Does your test case
contradict it?
On Sun, May 8, 2011 at 7:32 PM, Graham Lea gra...@grahamlea.com wrote:
Hello.
I would like to draw your attention to the issue:
http://jira.codehaus.org/browse/MNG-2258
This issue is now 5 years old and has 81
Hi Benson,
Thanks for taking a look at it.
I suppose my test case does contradict the last comment by Benjamin.
The comment is about inheritance and the like, however the test case I've
created has no inheritance at all. All I've done is bound the exec plugin to
the compile phase in a
On Mon, May 9, 2011 at 5:02 PM, Graham Lea gra...@grahamlea.com wrote:
I suppose my test case does contradict the last comment by Benjamin.
The comment is about inheritance and the like, however the test case I've
created has no inheritance at all.
Isn't there a super pom baked inside Maven
Wendy Smoak wrote:
Isn't there a super pom baked inside Maven that everything implicitly
inherits from?
Yes.
I wonder if the order is coming from that...
No, the rules for the plugin ordering game within a given phase are
1) plugins from lifecycle mappings go first
2) plugins from the
Thanks for the clarification, Benjamin.
Does this mean that it's not possible to force a plugin to execute in the
compile phase and before the default-compile execution unless I write a custom
lifecycle and use a different packaging type?
Cheers,
Graham.
On 10/05/2011, at 7:23 AM, Benjamin
Graham Lea wrote:
Does this mean that it's not possible to force a plugin to execute in the
compile phase and before the default-compile execution unless I write a custom
lifecycle and use a different packaging type?
Correct.
Benjamin
Hello.
I would like to draw your attention to the issue:
http://jira.codehaus.org/browse/MNG-2258
This issue is now 5 years old and has 81 votes, however no one is assigned to
investigate or resolve it.
I created a duplicate of the issue with a simple test case to try and gain some
