First: +1 for 1.6 minimum. Second: I feel we need to take a more strategic look at java in general and plugin mechanics & dependencies in particular. 1.6 is deprecated since a few years - and while its bytecode runs fine on a JDK 8 runtime, any implicit dependencies and internal reflection magic relies on the horrible fact that the classpath is global and anything is accessible.
This is not the case (or should not be the case) when running on a Java 9 runtime. As I'm sure you are aware, attempting to run maven and its plugins in an OSGi environment is a rather complex, and currently rather futile, exercise due to the modularized nature of the classloader as well as the runtime in general. While there are certainly differences between OSGi and Java 9 as far as the runtime and classloading mechanics go, the similarities in modularization are decently clear. So ... how do we ensure that our plugins can work in a JDK 9 runtime environment (in addition to JDK 6 - 8 RTs)? Do we create a shared utility to generate correct module-info.java files? What are your thoughts on the upcoming - substantially bigger - change when we need to be compliant with the module mechanics of Java 9? 2014-12-24 14:20 GMT+01:00 Kristian Rosenvold <krosenv...@apache.org>: > >Oops. Snappy contains 1.6 java bytecode, which breaks the build on maven > plugins. We need to upgrade to 1.6; I'm taking this to the mailing list :) > > Last time discussed this we established a consensus to establish 3.0.5 > (maybe 3.0.6) as a minimum baseline for the 3.x range of plugins. > > This 3.0.X has a 1.5 java requirement. The problem is that *everyone* > is moving to 1.6 and it's getting increasingly hard to maintain a 1.5 > code base. As an example, I have been moving code to apache commons, > but we're basically unable to use this effort because commons is now > 1.6. alternately I need to backport the code in a > "source-level-shading", but these things are getting silly. > > I propose the following: > > Make the 3.x line of plugins java 1.6+ only. > Release all shared utilities in 1.6 versions in the 3.x version range. > 3.0.X maven versions stay "forever" on the 2.x line of plugins and jdk 1.5. > The most recent core version moves defaults to the 3.x range of plugins. > The parent poms migrate to 3.x range some time in the near future. > > Keeping 3.0.x fixes to a minuimum (and "critical" stuff) only, will > ensure that we can still stay 1.5 compatible here. > > > Kristian > > 2014-12-24 13:52 GMT+01:00 Benson Margulies <bimargul...@gmail.com>: > > I don't have access to push a plexus-archiver release, could you > > please do the honors. > > > > Also, looks like my splitting job left some work behind in terms of > > the parent pom. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- -- +==============================+ | Bästa hälsningar, | [sw. "Best regards"] | | Lennart Jörelid | EAI Architect & Integrator | | jGuru Europe AB | Mölnlycke - Kista | | Email: l...@jguru.se | URL: www.jguru.se | Phone | (skype): jgurueurope | (intl): +46 708 507 603 | (domestic): 0708 - 507 603 +==============================+
