Well it's not like Maven [,3.2) is critically broken... so you'll just have to live with that toolchain... anyways, toolchains support should resolve issues down to 1.5 at least (or older if you can live with older versions of surefire plugin)
On 12 November 2013 11:02, Chris Graham <[email protected]> wrote: > Um, yes, me! :-) > > Seriously we are still stuck on Java 1.5/WAS 6.1/COBOL for at least > another year. Until we move to java 6 (or 7) depending on what oracle will > support. > > -Chris, representing 0.0001% :-) > > > Sent from my iPhone > > On 12/11/2013, at 4:41 PM, Romain Manni-Bucau <[email protected]> > wrote: > > > Isnt the question: is there still someone needing j5? Almost all apache > > projects and others moved to j6 at least > > Le 11 nov. 2013 23:53, "John Patrick" <[email protected]> a écrit : > > > >> i guess it's the only way to definitely ensure backwards compatibility > >> > >> open potential solution would be to use vagrant, I use it to ensure > >> developers as using the same base build setup and the files can be > source > >> controlled > >> > >> > >> > >> On 11 November 2013 22:39, Benson Margulies <[email protected]> > wrote: > >> > >>> > >>> > >> > http://maven.apache.org/developers/release/maven-project-release-procedure.html > >>> > >>> says so. I don't know where I'm going to get that environment. > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >>> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
