myGWT 1 maven repo

[mikl]

Hello,
There is a maven repository for myGWT (http://code.google.com/p/mygwt-maven-repo/).
Is it the official repository ?
Will be update to provide Ext GWT ?

Thanks,
Michael

[ushkinaz]

It's not official, it was set up by some guy from old forums. MyGWT had no official support of Maven. gxt will not have it either, afaik.

[darrellmeyer]

That is correct.

[mikl]

It's a shame :-(
Thanks for the answers

[ushkinaz]

I do have plans of adding maven support to gxt, but that will take some time, since gwt 1.5 is not supported by existing plugins of maven. A plugin from gwtforge, which supports 1.5 does not support I18n.
So I'll have to either wait or write my own plugin )))

[mikl]

Maybe GWT 1.5 will be supported when a full version will released because for the moment there is the Milestone version.

But I think adding maven support for gxt doen't need a plugin, isn't it ?

[ushkinaz]

You need to compile your gxt based project, and for that you need gwt 1.5 support, which is absent in current plugins.

[mikl]

hum /:)
If I understand, to use gxt I need GWT 1.5 version ?

[ushkinaz]

Right. milestone 2 currently.

[mikl]

Oh, shame. So we must waiting gwt maven plugin update (I ask maven gwt plugin owners to know that).

A maven-gwt-plugin owner answers me:

You will need to use the lastest version (2.0beta13) but yes. I have been using it with m1 for a while. We still don't have M2 in the maven repo, though, because we have filled up our Google Code disk quota.


I will try it !

[ushkinaz]

mikl, in case you'll be using maven-gwt from Windows - dont put your files under folder with spaces in the name. =)

[mikl]

Ok, thanks for the HINT. :-)

[mattbishop]

I think there's two issues here; the original post asked if GXT was going to be posted to the maven2 repository (http://repo1.maven.org/) so that maven builds could pick up the jars as dependencies.

The other has to do with the maven build plugin. That's different than repo support.

So, please, post GXT to the main repo so us maven users don't have to put up our own repositories to do builds. If you want a "starter" post to send in, I am happy to provide the one I built.

[PGTaboada]

Why don't simply install it to the local repo?
And, if you are using m2, you will sooner or later need an own repo for stuff that cannot be published.
It would be great thou to have a pom so we can build/ install the artifacts more easily.

I simply created jars with the javadocs and sources provided in the distribution. With the following commands they got installed into the local repo.

mvn install:install-file -DgroupId=com.extjs -DartifactId=gxt -Dversion=1.0-RC1 -Dpackaging=jar -DgeneratePom=true -DcreateChecksum=true -Dfile=gxt.jar

mvn install:install-file -DgroupId=com.extjs -DartifactId=gxt -Dversion=1.0-RC1 -Dpackaging=jar -DgeneratePom=true -DcreateChecksum=true -Dfile=gxt-src.jar -Dclassifier=sources

mvn install:install-file -DgroupId=com.extjs -DartifactId=gxt -Dversion=1.0-RC1 -Dpackaging=jar -DgeneratePom=true -DcreateChecksum=true -Dfile=gxt-api.jar -Dclassifier=javadoc

[mattbishop]

Local installs are fine for one developer; locally-managed repositories are fine for an organization, but globally-deployed repositories make it easier for others to enjoy my derived work. If I release something that uses GXT, I'd really rather they were able to download and build my project without having to do a local install of GXT.

Just because it is possible, doesn't make it attractive. Not having a globally-reachable GXT repo diminishes developer enthusiasm.

Others have seen this too, including the GWT team itself. It's a small effort, especially since GXT is built with maven. It is an effort that will make a lot of developers happy and excited about the using the GXT project in their own efforts.

[PGTaboada]

fair enough.