Oophm is not planned for 1.6

On Fri, Nov 21, 2008 at 12:35 PM, nicolas.deloof
<[EMAIL PROTECTED]>wrote:

>
> I was not aware OOPHM was planned for 1.6, but in such case only jars
> are required in maven repo. This will just require the maven plugin(s)
> to upgrade and detect gwt version >= 1.6
>
> Cheers,
> Nicolas
>
>
> On 21 nov, 18:19, Jason Essington <[EMAIL PROTECTED]> wrote:
> > but with OOPHM in 1.6, that is no longer necessary is it?
> >
> > On Nov 20, 2008, at 3:20 PM, Scott Blum wrote:
> >
> > > Funny you should mention this.. we had a crazy plan once to embed
> > > the native libs into gwt-dev.jar, and at startup install them into
> > > the temp directory and then load them, with delete on exit.
> >
> > > On Thu, Nov 20, 2008 at 5:15 PM, Ray Cromwell
> > > <[EMAIL PROTECTED]> wrote:
> > > 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
> >
>

--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---

Reply via email to