if you do not have yet multimodule project then try to split it into client, RPC and server part. I suggest to compile RPC and client part with Java 1.5 specified and server part with 1.6. Maven should automatically turn 1.5 compatibility on also in case you are compiling with JDK 1.6.
On 8. Okt, 23:31 h., Ginny <[EMAIL PROTECTED]> wrote: > I want to compile the server side with Java 1.6, but how can I do this > with the gwt-maven plugin? My pom.xml file specifies a 1.5 source and > target and attempting to change these to 1.6 results in a javac error. > Ginny > > On Oct 8, 6:29 am, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > That doesn't really make sense. If your server side is 1.6, it is > > backwards compatible and can definitely read 1.5 class files. The > > other way around though, doesn't work (of course). > > > Sounds like you may have 1.6 classes trying to be read by a 1.5 > > runtime, rather than what you described? > > > On Oct 7, 4:41 pm, Ginny <[EMAIL PROTECTED]> wrote: > > > > My GWT server side classes include classes that require Java 1.6. If I > > > compile those classes in Java 1.6 and compile my GWT classes in Java > > > 1.5, I get class versioning errors at runtime when the server side is > > > accessed. Is there anyway to use the gwt-maven plugin and compile my > > > server side classes in 1.6 to avoid this problem? Or is there another > > > way around this? > > > Ginny --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
