Stephen Connolly wrote: > So now that I have a spec for the PDTs drafted, I have been thinking of how > that could influence Maven 5. Some things that came to mind, in no particular > order:
May I suggest support for custom "transformation rules" when inheriting a value from the parent POM. Have a look at what I outlined in MNG-5951 [1]. The current solution for project/src/url, project/scm/connection, etc. [2] is horrible: 1.) Having to define attributes like @child.scm.developerConnection.inherit.append.path on the parent rather than the child element they apply to leads to ridiculously long attribute names, but had to be done to avoid changing the Modello model [3]. Placing those on the element they actually refer to would avoid any ambiguity. 2.) Attributes like @child.scm.developerConnection.inherit.append.path solve special cases for special elements. IMHO, there should be a generic and customizable way to describe how a POM's values are inherited. Just my 2 cents, Andreas [1] <https://issues.apache.org/jira/browse/MNG-5951?focusedCommentId=15190890&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15190890> [2] <https://issues.apache.org/jira/browse/MNG-6059> [3] <https://issues.apache.org/jira/browse/MNG-6059?focusedCommentId=15373650&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15373650>
signature.asc
Description: OpenPGP digital signature
