7 Oct
2010
7 Oct
'10
2:10 p.m.
On Oct 7, 2010, at 1:32 PM, Sergiu Dumitriu wrote:
On 10/07/2010 09:38 AM, Vincent Massol wrote:
This was supposedly fixed in Maven 2.1....
Thanks
-Vincent
4) The way the Extension Manager works is by
looking at the dependency version in the Maven POM for the extension. Thus the best
practice is to use version ranges to show the compatibility matrix of a given extension
with XE core. Thus I propose several things:
-- that we start using version ranges in our extension POMs
Currently there's a problem with version ranges and releases:
http://jira.codehaus.org/browse/MRELEASE-318