On Monday 07 March 2011 7:30:32 AM Andrzej Michalec wrote: > Another hint for environment. Being seasonal contributor I faced problems > with JDK1.5 build. I did not spot problems since I am using JDK1.6 locally > and generated Eclipse workspace did not force me to use compatibility with > 1.5. Maybe maven should generate by default code compatibility 1.5 instead > of latest-greatest; this way we would reduce problems injected by > contributors regenerating workspace.
I'm all for that, if you can figure out how to do it. :-) I did spend a little time on it a while ago but couldn't figure out the magic incantations to get it all working without doing some major duplication of various profiles in the poms. :-( Seriously, if you run the setup.eclipse with something like: mvn -Psetup.eclipse -Dcxf.jdk.version=1.5 it will set the eclipse projects to 1.5 level. HOWEVER, since we don't include some of the dependencies that are built into the JDK when building with Java6, the projects won't work in eclipse as things like JAXB and stax and such won't be there. You MAY be able to do: mvn -Psetup.eclipse,jdk15 -Dcxf.jdk.version=1.5 as that would bring in the 1.5 deps. However, that would also then generate JAXWS 2.2 and JAXB 2.2 code. I'm not sure if that would then work in the restricted "1.5" environment or not. You could give it a try. -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com
