Hi,
On 5/4/16 10:38 PM, Karl Heinz Marbaise wrote:
Hi Mirko,
just for the record the issue is:
https://issues.apache.org/jira/browse/MJAR-183
and not MJAR-193 ;-)..
On 5/4/16 9:21 PM, Mirko Friedenhagen wrote:
Hello,
I think I understand why it is more appropriate to put life cycles for
package types into the corresponding plugin.
So is the plan to update referenced mojos between minor plugin releases?
I think there problem with that approach, cause if you define your
plugin versions via pluginManagement in your projects (corporate pom
etc.) there will be no change...only if you just omit the definitions
this will influence one...as it does today with changing Maven version...
This should meant:
I think there is no problem with that approach...
Will maven-core 3000 drop life cycle definitions and everyone will
have to
include the type plugin in the pom and remember to switch on extensions?
From the current state yes...
The most important at the moment is we need a mapping from packaging to
plugin which must be extendable...
But we might enhance Maven so there is no need to define extensions=true
...etc.. would make handling simpler...
This is the first step to have the chance for changing Maven core...
Just curious :-)
Regards
Mirko
Some further informations:
http://www.mail-archive.com/[email protected]/msg108951.html
Also information about the subject:
https://issues.apache.org/jira/browse/MNG-5697
Kind regards
Karl Heinz
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
