Ola Bini wrote:
> I'm feeling deeply torn, especially since I know many of the features
> of Java 5 will make our lives easier. Can we go the middleground?
> Development and building has to be done with Java 5 or later, meaning
> that the source code can contain annotations, which we can use to do
> code generation with apt. We can force the resulting jars to be
> 1.4-compliant anyway. We could also make dual distributions, where the
> 5+ distribution contains real concurrency instead of the backport, and
> so forth.
But that sounds like it would yield a complicated build process,
complete with subtle problems and differences in the resulting JRuby's
Also: what are the planned uses for Annotations? Only for static code
generation at JRuby build time or for storing information at runtime as
well?
If it generates too much work for providing both 1.4 and 1.5 versions
for JRuby, I'd say one option would be to just stick to 1.4 development
for another, say, year and then re-evaluate.
Or: just switch to 1.5 and hope that by the time of the next major
release, most interested enterprise customers have switched.
Or: another middleway: could some of the features be made pluggable?
Like support Java 5 language features in Java integration (Enums,
Annotations, ...) or others? Keep in mind, Java 7 will create the same
problems of new language features once it hops along, so having a
solution that can be reused for it can be useful.
murphee
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
