Hi Jon, Le dimanche 15 février 2015 21:41:52 Jon Harper a écrit : > Hi, > since there were no answers, I'm not sure I wrote to the correct mailing > list for this problem. good mailing list, but can of worm :)
> Can anyone direct me to someone who is interested in > working on this issue ? I can try to work on this once more: perhaps we'll manage to improve something > > For info, the docs have been saying the following for 7+ years: > "groupId, artifactId, version: > These elements are self-explanatory" > > The version element is *not* self-explanatory, especially regarding > interactions between version ranges and *-SNAPSHOTs artifacts. you're right: version *in dependencies* is not self explanatory (version in Maven coordinates is self explanatory) It has a lot of subtle features: preferred vs exact match, version range, then the question of SNAPSHOTS > > Any thoughts on this matter would be appreciated. if you have little patches for the source of the page [1], I can review and we can work and discuss on it step by step Regards, Hervé [1] https://svn.apache.org/repos/asf/maven/site/trunk/content/apt/pom.apt > Regards, > Jon > > On Thu, Feb 5, 2015 at 5:52 PM, Jon Harper <[email protected]> wrote: > > Hi, > > I'm resurrecting this old thread to ask if it's possible to change > > http://maven.apache.org/pom.html to document the current implementation > > behavior (7+ years old). > > > > Please see my comment on MNG-3092: > > http://jira.codehaus.org/browse/MNG-3092?focusedCommentId=362616&page=com. > > atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-36261 > > 6 > > > > Jon > > > > Mark Hobson Fri, 06 Jul 2007 06:53:04 -0700 > > > > > Hi, > > > > > > Whilst attempting to fix MNG-2994, I discovered MNG-3092 that was > > > contrary to the 2.0 design docs: > > > > > > http://jira.codehaus.org/browse/MNG-3092 > > > > > > Brett, Kenney and myself had a brief discussion on IRC about this: > > > Kenney says that the behaviour is theoretically correct (which it is), > > > although I feel it goes against the practical usage described in the > > > docs. The two main choices I can see are: > > > > > > 1) We stick to the design docs and disallow snapshots in ranges when > > > they aren't an explicit boundary, as per the MNG-3092 patch. > > > > > > 2) We reconsider the design docs and leave range resolution behaving > > > as it is, then use profiles to enable or disable snapshot repositories > > > at build time. > > > > > > Any thoughts? > > > > > > Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
