You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2019/10/01 19:45:57 UTC

[GitHub] [maven] rfscholte commented on issue #286: [MNG-6656] Introduce base for build/consumer process

rfscholte commented on issue #286: [MNG-6656] Introduce base for build/consumer process
URL: https://github.com/apache/maven/pull/286#issuecomment-537198294
 
 
   > On the feature I have mainly one point: are the transformed pom and real project pom attached? Think it makes sense to attach both but didnt spot the code doing that (original classifier for the project one maybe?)
   
   The pom is being transformed during the process, making it suitable for its purpose. At this moment in the beginning the pom is enriched with elements so it reflects the max pom is people/IDE/... are using right now. During distribution (install/deploy) the pom will be cleaned up from some build specific information as the parents relativePath and modules. Hence there should be no reason to attach more than one pom. You must trust that Maven is doing it correct, and for that reason I've tried to be very strict with class exposure, most are package private.
   
   These are just examples that should give us hopefully enough feedback if the process works.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services