[ https://issues.apache.org/jira/browse/MNG-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285311#comment-16285311 ]
Hervé Boutemy commented on MNG-6308: ------------------------------------ sure, one can avoid defining ${project.packaging} then put just pom to not benefit from default plugin bindings to lifecycle but in general, if we defined default plugin bindings based on ${project.packaging} value, it's because in general this defines the expected default build: explicitely adding some plugins is just some little additional build customization > display packaging when building a module > ---------------------------------------- > > Key: MNG-6308 > URL: https://issues.apache.org/jira/browse/MNG-6308 > Project: Maven > Issue Type: Improvement > Affects Versions: 3.5.2 > Reporter: Hervé Boutemy > Assignee: Hervé Boutemy > > Packaging is a key information, since it defines what bindings will be: it is > short and should be visible in the build log > proposal: > {code}[INFO] > ------------------------------------------------------------------------ > [INFO] Building Apache Maven Distribution 3.5.3-SNAPSHOT > [15/15] > [INFO] --------------------------------------------------------------- pom > --{code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)