Yeah, I guess we could ask our users and if there are no concerns with going to Java 6 all over, let's simply do it. Updating to latest Sling on Java 5 isn't possible anyway as some modules use Java 6 already.
Carsten 2013/9/10 Felix Meschberger <[email protected]> > Hi > > That means setting sling.java.version=5 on *all* modules which do not > currently have sling.java.version=6 ? I would be fine with that. Then we > can still have an explicit action to actually drop Java 5. Otherwise we > have to analyze each and every bundle now. > > Otherwise: Maybe it is also time to take the next step and just go Java 6 > all over and not consider java 5 at all any longer ? > > Regards > Felix > > Am 10.09.2013 um 11:11 schrieb Bertrand Delacretaz: > > > Hi, > > > > I'm not sure if it's worth the effort keeping that anymore, examples > > like SLING-3042 and SLING-3049 show that it's increasingly getting in > > the way. > > > > IIRC we discussed recently and decided to keep it wherever possible. I > > suggest reversing that and saying that we keep it only for bundles > > where it requires no additional work, and drop it as soon as it's > > bothering us in some way. > > > > In practice, this might mean setting sling.java.version=6 in the > > parent pom, and overriding that with sling.java.version=5 in bundles > > where we feel that's needed. > > > > WDYT? > > > > -Bertrand > > -- Carsten Ziegeler [email protected]
