[
https://jira.codehaus.org/browse/MNG-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348768#comment-348768
]
Sergei Ivanov commented on MNG-3397:
------------------------------------
I support the idea of a compact colon-separated dependency id, however:
* scope does not really belong to artifact coordinates, it is an additional
property of an artifact dependency. As such, IMHO it deserves a separate XML
attribute.
* some plugins are already using colon-separated coordinate notation, but the
ordering of the coordinate parts is not consistent. See for example, off the
top of my head:
http://maven.apache.org/plugins/maven-remote-resources-plugin/process-mojo.html#resourceBundles
versus includes/excludes in
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet
I am pretty sure I saw it being used elsewhere, but cannot remember just now.
This really needs to be standardised.
* it could be just me, but I think colon does not really stand out visually as
a separator in a stream of characters, maybe we should allow for optional
spaces around colons for better readability
* if possible, we should also try to do away with container elements (e.g.
{{exclusions}}) or make them optional in all non-ambiguous contexts.
Example:
{code}
<dependency id="org.junit : junit : 4.11" scope="test">
<exclusion id="org.hamcrest : hamcest-core"/>
</dependency>
{code}
or
{code}
<dependency id="org.apache.maven : maven-core : 3.2.2" scope="compile">
<exclusion id="org.codehaus.plexus : plexus-utils"/>
<exclusion id="org.codehaus.plexus : plexus-interpolation"/>
</dependency>
{code}
> [RFC] change the POM to use attributes
> --------------------------------------
>
> Key: MNG-3397
> URL: https://jira.codehaus.org/browse/MNG-3397
> Project: Maven
> Issue Type: Bug
> Components: FDPFC, POM
> Affects Versions: 2.0.8
> Reporter: Brett Porter
> Fix For: Issues to be reviewed for 4.x
>
>
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
