I believe the only reason is that we had a discussion thread about 4 or so months ago concurring that we should use 1.5-compatible APIs moving forward (we used to support 1.4 via RetroWeaver at the time).
I tend to agree that if 1.5 is already end-of-lifed (and has been for 4 months), it doesn't make much sense to release a brand new (first ever) Shiro release that targets a platform that Sun no longer even supports. Does anyone feel differently? On Tue, Jan 26, 2010 at 3:23 PM, Kalle Korhonen <[email protected]> wrote: > Bah, I just managed to break the build by adding the new aspectj > module. It fails on: > [INFO] Compilation failure > /export/home/hudson/hudson/jobs/Shiro/workspace/trunk/support/aspectj/src/test/java/org/apache/shiro/aspectj/DummyServiceTest.java:[32,-1] > cannot access > org.apache.shiro.aspectj.AspectjAnnotationsAuthorizingMethodInterceptor > bad class file: > /export/home/hudson/hudson/jobs/Shiro/workspace/trunk/support/aspectj/target/classes/org/apache/shiro/aspectj/AspectjAnnotationsAuthorizingMethodInterceptor.class > class file has wrong version 50.0, should be 49.0 > > I.e. the builder jdk is 1.5 but 1.6 is required. What I don't get > though is that it just compiled that > AspectjAnnotationsAuthorizingMethodInterceptor but I suppose it's > actually the imported AspectJ classes that are built on jdk 1.6. Now, > 1.5 was end-of-lifed last October. Funny, but I don't even have 1.5 > jdk anymore on my system and Sun has really made it difficult to get > to it anymore (just checked). > > What's our policy regarding supporting jre versions? The easiest fix > is probably to use a different builder on Hudson, but we might be > using jdk 1.5 for a reason. I can detach the new module in the > meantime. > > Kalle >
