Hello, With the recent commit of Paul Lindner's Maven pom.xml changes: http://svn.apache.org/viewvc?view=revision&revision=1085239
...and my followup using these to allow us to utilize Closure for Java 1.6 JS compilation: http://svn.apache.org/viewvc?view=revision&revision=1085647 ...Shindig now has separate default functionality when using JDK 1.5 vs. JDK 1.6. Long ago we had hoped to move to 1.6 wholesale, but discovered that a number of users rely on 1.5 and cannot switch. As such, we developed this solution. A consequence of this is that you'll now see source directories named java15 and java16, peer to the usual java/ versions. Eg: http://svn.apache.org/repos/asf/shindig/trunk/java/gadgets/src/main/java15/org/apache/shindig/gadgets/ http://svn.apache.org/repos/asf/shindig/trunk/java/gadgets/src/main/java16/org/apache/shindig/gadgets/ The former is built w/ 1.5; the latter, >1.6. This introduces complications with Eclipse (and probably other IDEs) since JsCompilerModule is referenced in "base" DefaultGuiceModule. As such, your IDE needs a JsCompilerModule mapping. I haven't yet figured out the cleanest way to do this w/ the Maven Eclipse plugin, but augmenting your client is fairly easy. Steps: 1. For Java 1.5 users, choose java15. Java 1.6, choose java16. 2. After mapping in your client, see the missing symbol error in DefaultGuiceModule for JsCompilerModule. 3. Use Project -> Properties -> Java Build Path -> Source -> Add Folder... to add java/gadgets/src/[main,test]/java[15,16] 4. If using Closure (JDK 1.6), manually map in external JARs for Closure Compiler and Protobuf. Both are under the Maven repository com/google/ directory. >From here, you can develop as usual. If anyone has advice on how to activate the java15/java16 profile(s) natively in the Maven plugin, this would be most welcome! --j
