Promoting maven3 to 3.1.1

[Mark Evenson]

On Nov 24, 2013, at 22:38, Blair Zajac <blair at orcaware.com> wrote:

> 
> On Nov 24, 2013, at 3:30 AM, Mark Evenson <evenson at panix.com> wrote:
> 
>> 
>> On Nov 23, 2013, at 9:20, Blair Zajac <blair at orcaware.com> wrote:

[…]

>>> Any reason for me not to update the maven3 port to 3.1.1?
>> 
>> Maven 3.1 is significantly different “under the hood” than Maven 3.0, especially in the adoption of the apache.org Aether connector.  This affected me with ABCL’s usage in that I needed to have both ports around to test things.  

[…]

>> Two paths here that I see:  

[…]

> 
> I’m thinking we do the following:
> 
> 1) Add maven3.0 which is a copy of maven3.
> 2) maven3 becomes replaced_by maven3.0.
> 3) Move maven-devel to maven3.1.
> 
> I don’t see a need for a mvn30 and mvn31 symlinks.  People can ‘port select’ between maven3.0 and maven3.1.

Other than I don’t know any other example of a port name with a period (“.”) in it, so we might want to check that including version in this way doesn’t break anything, this looks like a perfectly acceptable proposal to me.

-- 
"A screaming comes across the sky.  It has happened before but there is nothing 
to compare to it now."