On Thu, Apr 16, 2015 at 12:04 AM, Tibor Digana <tibordig...@apache.org> wrote:
> I thought the multi-versioned JAR had a different ambition, namely > delta-snapshots. > I guess that only a fragment of classes should be deployed in muti-version > JAR due to we have already deployed previous timestamp and thus current > snapshot is only aggregated from previous JARs. In this case the build tool should not care about JDK because it is totally > uppon the deployer whether the timestamps should break the bytecode > compatibility or not. > For me it is the goal (as discussed with Brian) but this where having a new javac will be required to compile these fragments and validate the compatibility of the fragment with the original class. That's why for now we can just "play" with it at runtime with Brian's patch by replacing a full class wrote for J7 and putting the enhanced version for J8 under the META-INF/versions/8 With the patched version of the JRE 8 we should use the enhanced J8 version while in <=J7 we should use the default one. > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/DISCUSSION-JEP-238-Multi-Version-JAR-Files-tp5829748p5832950.html > Sent from the Maven Developers mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- ----- Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
