[MacPorts] #43156: maven-devel installation completely broken

[MacPorts]

#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    |
----------------------------+--------------------------------
Changes (by ryandesign@…):

 * cc: easieste@…, me@…, blair@… (added)
 * keywords:  maven3 maven-devel =>
 * priority:  High => Normal


Comment:

 The problem is that there seem to be too many maven ports, with
 conflicting naming schemes; I don't know why this is.

 Usually a software package in MacPorts has either:

  1. one version at a time: only one of these can be installed at a time
 because they install files to the same places:
    a. a single port foo for the current version
    b. a port foo for the current stable version and a port foo-devel for a
 development version
  2. multiple versions simultaneously: any number of ports fooA fooB fooC
 etc. where A B and C are some portion of the version number; any of these
 can be installed at the same time because they install files to different
 places; often a foo_select port is available to make one of these the
 version that gets run when you run "foo"

 maven seems to be using both strategies 1(b) and 2, and it should decide
 which of these strategies it wants to follow. I think it wants to follow
 the 2nd strategy, since the maven port is replaced by the maven1 port. So
 shouldn't maven3 be updated to a newer version (#42737) and maven-devel
 replaced by maven3? See also #42114.

-- 
Ticket URL: <https://trac.macports.org/ticket/43156#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X