#43156: maven-devel installation completely broken ----------------------------+-------------------------------- Reporter: simonazriel@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: maven-devel | ----------------------------+-------------------------------- Comment (by easieste@…): Replying to [comment:1 ryandesign@…]: [I had responded to this last week with the "wrong" return address for the mailing list. Thanks to @ryandesign for pointing this out.] Yes, this is the way forward in general. The subtlety was that maven-3.1.x changed the API points it exports to be used by other tools in a way that is incompatible with maven-3.0.x, so previous consumers of the maven3 port were broken if I we had updated maven3 to point to maven-3.1.x. Enough time has passed, that most of these consumers of maven3 (or at least the ones that I use), now work with both the maven-3.0.x and maven-3.1.x API. Two ways forward: 1) maven3 goes to maven-3.1.x. MacPorts no longer offers a maven-3.0.x installation 2) A new port 'maven31' gets introduced for maven-3.1.x; We rename 'maven3' as 'maven30' which offers maven-3.0.x. Possibly we use 'maven3' as synonym for 'maven31'. In any event, maven-devel should be retired. -- Ticket URL: <https://trac.macports.org/ticket/43156#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X