rmannibucau commented on PR #1437:
URL: https://github.com/apache/maven/pull/1437#issuecomment-1987157849

   > there is no way for a plugin to participate as part of the mojo-execution
   
   Yes, this is why I mentionned we can need to revisit a but the current API. 
Once again my main concern was that the "consumerPom" API has no link with 
consumer pom at all and we must converge to maven 4 (even if we backport to 
3.9) cause otherwise your API will be dead, even in 3.x when we'll backport 
things.
   Ultimately it looks more - in v3 world - to attached artifacts so it is 
doable without the new API to me - short term.
   Long term we need to find a better lifecycle but can need some list 
discussion?
   
   > It won't break anything ... plugins not supporting this will simply never 
set this and then getConsumerPom() will return the "traditional" file like 
today. Also not "all" plugins need to be adjusted, just these that care about 
build vs consumer pom...
   
   exactly so if you do you are no more compatible with the chain you describe 
earlier since the right pom will not be consumed downside so we need to be 
vigilant and see if it is an issue to break all the existing ecosystem or if we 
don't care plugins using this new (to be defined) API will not be compatible 
with existing plugins.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to