If this is done, please make sure that the conventions adhere to the gwt-maven plugin's repo layout. This allows you to use the maven-dependency plugin to download the platform specific JNI libraries separately and unpack them, so that one doesn't have to "install" the GWT distribution and set up a GWT_HOME environment variable.
I use this in my build process which allows Chronoscope to build clean on an empty computer with only Java and Maven installed and no other prerequisites or reliance on absolute file system paths. This allows us to startup a VMWare instant with an OS of our choice, and have it build and test out of the box with virtually no configuration needed. -Ray On Thu, Nov 20, 2008 at 2:09 PM, nicolas.deloof <[EMAIL PROTECTED]> wrote: > > I was considering only releases, as google-maven-repository has a > rsync to publish on maven central > But maybe you'd like to have a custom snapshot / milestones repository > (the way Springframework does for example). > > Nicolas > > On 20 nov, 21:59, Scott Blum <[EMAIL PROTECTED]> wrote: >> Do you mean for things like nightlies, or just full releases? >> >> On Wed, Nov 19, 2008 at 11:12 AM, nicolas.deloof >> <[EMAIL PROTECTED]>wrote: >> >> >> >> > Hi, >> >> > As a maven developper, I have contributed the central repository with >> > gwt artifacts. I now GWT team doesn't want to use maven as build >> > system, and I'm fine with this. I'm not here to try changing your >> > choice. >> >> > I just would like the build script to support deploying the GWT >> > artifacts to a maven repo (there is one dedicated to google projects >> > athttp://code.google.com/p/google-maven-repository/). I did this >> > manually myself for 1.5.x versions, but a more automated deployment >> > would be nice. >> >> > What's your opinion ? > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
