The ADF stuff is in incubation right now so there are all sorts of possibilities for change. I envision a lively discussion where discuss the pros and cons of allowing tomahawk, tobago or adf to use jdk 1.5 functionality. Currently tomahawk does not have any jdk 1.5 stuff (that I am aware of.)
Sean On 2/21/06, Martin <[EMAIL PROTECTED]> wrote: > Craig McClanahan <craigmcc <at> apache.org> writes: > > > > >> On 2/21/06, Martin <mjdenham <at> gmail.com> wrote: > >> I have tried this already, but unfortunately it does not work (although I > >> am > >> not experienced with maven).I changed the source and target tags in > >> adf-faces/pom.xml as below: > >> > >> <source>1.5</source> > >> <target>1.4</target> > >> but get the error: [INFO] Compilation failure Failure executing javac, > >> but > >> could not parse the error: javac: source release 1.5 requires target > release 1.5 > > > > That is not a Maven issue ... it is a Java restriction. If you want to say > > target=1.4, then you cannot say source=1.5 because the new source format > > requires features in the class format that were not present in the 1.4 > > version. > > > > > > Regards > > > > Craig > Thanks for the responses and clarifications. This means there is no way to > use > the Apache ADF Faces as it stands on JDK 1.4. > > Maybe the JDK 1.5 specific code could be edited to make it compatible with JDK > 1.4. I don't think this would be too hard as the oracle ea19 version was > compatible with JDK 1.4. > > > >
