I like the 'Java 5 by default, but...' stance here. I see no problem at all in requiring Java 6 if you want to use Cassandra, since the more restricted platforms (like GAE) won't run Cassandra anyway. If you need persistence on such a platform, you will have to build a persistence system that is compatible with its environment.
Summing up: Java 5 for most things OK, with a special clearance for the Cassandra persistence to use Java 6. Angelo On Oct 22, 2010, at 7:48 AM, Marcel Offermans wrote: > I agree it makes things a bit more complicated, but we need to be aware of it > anyway since the "execution environment" is something we can (and maybe > should) set explicitly in every bundle's manifest (just like we explicitly > import, export and version our packages). > > I don't think it's too much work though, if we agree that by default our > bundles are Java 5 compatible and we can make exceptions (if the technology > we use in a bundle requires it). > > On 22 Oct 2010, at 0:44 , Bram de Kruijff wrote: > >> 2010/10/21 Marcel Offermans <marcel.offermans at luminis.nl>: >>> Aloha! >>> On 21 Oct 2010, at 16:08 , Ivo Ladage-van Doorn wrote: >>> >>> What do you think? Should we support Java 5 or can we require Java 6? >>> >>> I think we should not go to Java 6 for all bundles. There definitely is >>> value in choosing the lowest possible "execution environment" for a bundle >>> because it increases the portability. The OSGi framework itself still runs >>> on CDC/Foundation and although I'm not advocating we should use that for all >>> bundles, sticking with Java 5 for most of them ensures that they will >>> probably also run on platforms like Android (not sure about the Google App >>> Engine?). >> >> This will make things more complicated in terms of configuration >> management and we will need to make jvm level requirements explciit >> for subprojects, distributions, etc... still I agree so +1 for keeping >> platform at level 5. >> >> Regards, >> Bram >> _______________________________________________ >> Amdatu-developers mailing list >> Amdatu-developers at amdatu.org >> http://lists.amdatu.org/mailman/listinfo/amdatu-developers > > > _______________________________________________ > Amdatu-developers mailing list > Amdatu-developers at amdatu.org > http://lists.amdatu.org/mailman/listinfo/amdatu-developers
