Port for Maven 3.3
horst.leitenmueller at liwest.at
Sat Oct 24 14:52:05 UTC 2015
there are many problems if you don’t have the correct maven version
regarding jdk and so on
i like it how it is done in macports
maven1 was 1.1 but now EOL (http://maven.apache.org/archives/maven-1.x/)
maven2 was 2.2.1 but now EOL (http://maven.apache.org/archives/maven-2.x/)
maven3 keeps the latest 3 version 3.3.3
maven31 keeps latest 3.1.x version 3.1.1
maven32 keeps latest 3.2.x version 3.2.5
and maven-devel keeps the latest devel version
hopefully information helps, in this case you can cover most things
> On 21 Oct 2015, at 14:54, Kurt Jaeger <lists at opsec.eu> wrote:
>> Agreed, it sounds like we need a decision on whether we want
>> devel/maven33 etc.
> Yes. I'm no real maven user, so I can't contribute experience.
> The choice should be based on experience and probably some
> testing, if the dependent ports still build and run with the
> grand unified maven (which would be 3.3.x).
>>> From that ticket, there isn't a huge amount that depends on Maven so the
>> consensus seemed to be for devel/maven. If that is the case I'll cancel my bug
>> and try to help facilitate that. It would be good to have some goal posts
>> agreed though, for where we need to get to for someone to be bold and just
>> commit it. I'm new here though, so I'm not sure how this usually works.
> We try to do evidence-based computer science 8-), but have not found
> anyone who had the time/skills to build and run-test the dependent
> ports listed in
> Can you say something about your time-budget ? If you soon find
> the time to test, I would prefer that. Otherwise, maybe it's just time
> to jump into the abyss with 3.3.x 8-}
> pi at opsec.eu +49 171 3101372 5 years to go !
> freebsd-ports at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
More information about the freebsd-ports