Add API libraries for GWT under maven central repository.

[GoogleCodeExporter]

Found in Release:
1.1, 1.3 (for gears)

Detailed description:
The recently updated libraries cannot be found under maven central repository ( 
http://repo2.maven.org/maven2/com/google/gwt/google-apis/ ).

From this issue:
http://code.google.com/p/support/issues/detail?id=1226 
I found maven-google-repository which mirrors artifacts uploaded there to the 
central maven 
repository only for projects owned by Google (those marked with label:google).
Please consider uploading new versions of the libraries there. 

Workaround if you have one:
Just as a workaround for development, if you need to use the 1.1 release to 
your maven project 
until it becomes available through central, you can install it to your local 
maven repository with 
the following command:
mvn install:install-file \
-DgroupId=com.google.gwt.google-apis \
-DartifactId=gwt-xxx \
-Dversion=1.1.0 \
-Dpackaging=jar
-Dfile=/path/to/gwt-xxx.jar \
-DgeneratePom=true

and then use it in your pom.xml like:
<dependency>
    <groupId>com.google.gwt.google-apis</groupId>
    <artifactId>gwt-xxx</artifactId>
    <version>1.1.0</version>
</dependency>

note: xxx is the name of the api. e.g. maps, search

Original issue reported on code.google.com by jgon...@gmail.com on 2 Jun 2010 at 11:45

[GoogleCodeExporter]

Issue 383 has been merged into this issue.

Original comment by zundel@google.com on 9 Jun 2010 at 1:24

[GoogleCodeExporter]

Yes please add them. It will ease a lot the usage of gwt in mavenized projects.
For exemple gwt-gadgets-1.2.0 aren't yet available.

Original comment by aheritier on 4 Aug 2010 at 1:08

[GoogleCodeExporter]

When is this going to be fixed. This issue (which is rather simple to fix) has 
been hanging for some time.

Original comment by felixnut...@gmail.com on 15 Dec 2010 at 2:18

[GoogleCodeExporter]

Please update the central repo with the latest libraries.

Original comment by croydondias on 20 May 2011 at 6:52

[GoogleCodeExporter]

I'm surprised to see this isn't resolved yet. Is there a reason why the newer 
versions aren't in the maven repository?

Original comment by mail.ber...@gmail.com on 18 Jul 2011 at 2:09

[GoogleCodeExporter]

This is rather unusual. Do we have plans to make this available in Maven? I 
know there are not that many maven users but please be good Maven citizens and 
deploy this to maven central.

Original comment by misra.abby@gmail.com on 17 Aug 2011 at 2:39

[GoogleCodeExporter]

FYI, for there's a small typo in the mvn:install - 
-Dpackaging=jar  should be
-Dpackaging=jar \

Original comment by sanj2s...@gmail.com on 5 Nov 2011 at 6:39

[GoogleCodeExporter]

I'm looking for 1.2.1 but I don't see it in public repositories.

Original comment by kyoke...@gmail.com on 21 Aug 2012 at 5:47

[GoogleCodeExporter]

I can't believe that a such project looks dead!
Is it obsolete? deprecated?

What's happened?

Original comment by boboss74 on 24 Sep 2012 at 4:29

Attachments:

• isgwtapidead.png

[GoogleCodeExporter]

Looks to me like Google abandons gwt!

Original comment by shpand...@gmail.com on 24 Sep 2012 at 5:04

[GoogleCodeExporter]

Hard to say.
Ray Cromwell (gwt project leader, publishing on g+) says that it will be 
difficult to abandon GWT. Google ads use GWT (more than 95% of revenues)

Original comment by mathieu....@gmail.com on 24 Sep 2012 at 6:04

[GoogleCodeExporter]

It seems that Dart is the future of GWT... 

https://plus.google.com/117487419861992917007/posts/6YWpsHpqMqZ

Original comment by boboss74 on 25 Sep 2012 at 8:21

[GoogleCodeExporter]

The only way is local repository

Original comment by theasp...@gmail.com on 22 Oct 2012 at 8:24

[GoogleCodeExporter]

Yes, using an other (not necessarily local) repository is a solution...

But this is not fair...

Original comment by boboss74 on 22 Oct 2012 at 8:49

[GoogleCodeExporter]

Booooooooooooo

Original comment by shpand...@gmail.com on 22 Oct 2012 at 9:00

[GoogleCodeExporter]

The method by which you can draw attention to the issue is to vote for it. I 
doubt anyone owns this issue and that these projects are active. 

WORKAROUND:
For those who don't host a repository (like nexus or archiva) look at using the 
project scm as repo. Brett Porter has an excellent blog post on the subject 
(includes warnings about best practices) :

http://brettporter.wordpress.com/2009/06/10/a-maven-friendly-pattern-for-storing
-dependencies-in-version-control/

p.s. Booooooo++;

 :) 

Original comment by ahhug...@gmail.com on 22 Oct 2012 at 10:25