Thanks, Daniel, it's an interesting idea toward Mavenizing GWT, but I don't think we're ready to bite off much more than simple deployment to Central just yet. I plan to post the current script and POMs for code review this week. The script does a bit of custom packaging since we include Java sources needed by the GWT compiler in the gwt-user jar itself. Let's continue the discussion once the script is available for review.
/dmc On Mon, Aug 29, 2011 at 11:03 AM, Daniel Bell <[email protected]>wrote: > Hey Guys, > > I just noticed this thread, and wanted to suggest Maven Ant Tasks ( > http://maven.apache.org/ant-tasks/index.html). It includes Ant tasks for > installing build artifacts to local Maven repositories, or deploying them to > remote Maven repositories, both with arbitrary POMs. It can also generate > POMs with given dependencies, and download/manage dependencies using Maven. > > It seems like a good road to take, given that it integrates better than > tools/scripts/maven_script.sh with the existing build (Ant scripts), and > means that you wouldn't have to store your dependencies in source control > (apart from the patched/rebased ones, though you could deploy them to > Central too). It could also replace your script that deploys to the remote > Maven repository (I haven't seen that one, but I'm assuming it's a shell > script too: > http://code.google.com/p/google-web-toolkit/issues/detail?id=4853#c12), > and allow you to automate the deployment to Sonatype's repo (and > consequently to Central). If the plan was to eventually try to remove the > dependencies and manage them with Maven, this would be a step in that > direction too. > > Cheers, > Daniel > > On 29 August 2011 20:00, Thomas Broyer <[email protected]> wrote: > >> It's actually just a slight improvement over the already existing >> maven_script.sh<http://code.google.com/p/google-web-toolkit/source/browse/trunk/tools/scripts/maven_script.sh> >> (using >> pre-written POMs rather than generating them) >> >> That's actually not enough though, because GWT jars are created with a >> JarIndex, and a JarIndex contains the name of the JAR, so renaming it >> without regenerating or stripping the JarIndex (META-INF/INDEX.LIST) >> generates spurious exceptions in DevMode (caught internally, but very >> annoying if you "suspend executions on unhandled exceptions" when launching >> DevMode with a debugger attached: the CompilingClassLoader looks up classes >> in a gwt-user.jar instead of the gwt-user-2.4-SNAPSHOT.jar). >> Removing the JarIndex, or regenerating it, is easy, but still. >> >> -- >> http://groups.google.com/group/Google-Web-Toolkit-Contributors >> > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- David Chandler Developer Programs Engineer, GWT+GAE w: http://code.google.com/ b: http://turbomanage.wordpress.com/ b: http://googlewebtoolkit.blogspot.com/ t: @googledevtools -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
