>> It is - that is the jsr199 compiler that needs to be finished. >> It would be great to finish that and not look back. >> Although I made some progress I don't think I have the time. > > AFAICT, JSR199 also requires Java 1.6?
Indeed. But I am quite positive very few people (if any) use the javac hack anyway. > I'd overlooked the in-memory part - is there any point in releasing it > with javac support for files only? > I.e. just dropping the in-memory support for javac until jsr199 is > implemented. Na - don't think that would really work. You could try to check the store implementation and throw an exception ...but in the end it is an interface and you can never know what the impl is doing. Which is why I think 2.0 is the only real option. That said releasing 2.0 without the JSR199 in place feels a little silly. cheers, Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
