Hi,

I have got a use case where I would like to distribute a couple of Aries 
modules to a client on Java 5. Naturally, even the projects that use Java 5 
parents don't quite work outright because everything gets compiled on Java6 - 
as was agreed a while ago - so in a couple of places Java6 API calls have 
sneaked in.

What I would like to do is use the animal-sniffler plugin 
(http://mojo.codehaus.org/animal-sniffer-maven-plugin/) to check compile class 
files for usage of Java 6 APIs. It adds a bit of overhead to the build step but 
would ensure that projects that claim to be Java 5 compatible actually are 
without forcing all projects to move down (which I believe we can't even do 
since there were some definite Java6 prereqs). Also doing it that way let's us 
continue use @Override on implemented interface methods ;)

Thoughts / objections ?

Regards,

Valentin

Reply via email to