My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 501: Ensure that GWT artifacts are present in the Maven central repositories as part of release process.
44 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  cgruber@google.com
Closed:  Sep 2011


Sign in to add a comment
 
Reported by t.broyer, Dec 17, 2010
If you want to use Guava in a GWT project, you currently have to deploy the guava-r07-gwt.jar in your own Maven repository, as it's not on Maven Central.

Not a show stopper for us, but it would be much better if we weren't force to do it (and repeat it when we'll switch to r08)
Jan 12, 2011
Project Member #1 kevinb@google.com
(No comment was entered for this change.)
Summary: Would like guava-r08-gwt to be present on Maven Central
Status: Accepted
Owner: cgruberatgoog
Labels: Type-Task
Jan 13, 2011
Project Member #2 cgruber@google.com
I'll work on it this coming week.

Christian.
Jan 20, 2011
Project Member #3 kevinb@google.com
(No comment was entered for this change.)
Labels: Milestone-Release08
Jan 26, 2011
Project Member #4 kevinb@google.com
(No comment was entered for this change.)
Status: Started
Mar 24, 2011
Project Member #5 fry@google.com
(No comment was entered for this change.)
Status: Fixed
Mar 24, 2011
Project Member #6 cgdec...@gmail.com
Just checking, but should this really be marked fixed? I don't see any sign of the GWT jar in maven central.
Mar 24, 2011
Project Member #7 fry@google.com
Christian, can you comment on this? I figure either it's already happened or it won't happen, as release 9 is on its way out the door now...
Mar 24, 2011
#8 alexandr...@gmail.com
guava-gwt does not appear in any sub-folder of http://repo1.maven.org/maven2/com/google/guava/
What groupId/artifactId/version/classifier did you use ?
Mar 24, 2011
Project Member #9 cgdec...@gmail.com
I think at this point it would be fine if we could get this for r09 instead of r08. The main thing that's wanted here is the GWT jar in maven central and a way to ensure that happens for each release going forward.
Mar 24, 2011
Project Member #10 fry@google.com
(No comment was entered for this change.)
Summary: Would like guava-r09-gwt to be present on Maven Central
Status: Accepted
Labels: -Milestone-Release08 Milestone-Release09
Mar 24, 2011
Project Member #11 cgruber@google.com
<sigh>  Ok, if we're about to drop r09, then I'll fix it in trunk so we can release it all properly at the same time in the same process.
Mar 24, 2011
Project Member #12 cgruber@google.com
(No comment was entered for this change.)
Summary: Ensure that GWT artifacts are present in the Maven central repositories as part of release process.
Labels: Priority-High OpSys-All
Apr 7, 2011
Project Member #13 kevinb@google.com
(No comment was entered for this change.)
Labels: -Milestone-Release09 Milestone-Release10
May 5, 2011
#14 christop...@gmail.com
Any news on this ?
May 5, 2011
Project Member #15 cgruber@google.com
We're re-organizing the build system and it should all be there in the next couple of weeks.

Can you help out by giving us a sense of HOW you use the gwt artifact?  At present, do you use the ant-built downloadable one as-is?  And do you use it via the maven GWT plugins, or how does it fit into your lifecycle?

Christian.
May 5, 2011
#16 christia...@gmail.com
We're re-working the build system.  It should be in within the next couple of weeks.  Also, can you help describe how you use this artifact?  Using what plugins to consume it, etc.?  
May 5, 2011
Project Member #17 cgruber@google.com
Heh.  Forgot this wouldn't post to the bug. :)
May 5, 2011
#18 t.broyer
We have an internal Artifactory Maven repo, so I simply downloaded the bundle from the Downloads page and deployed the guava-rXX-gwt.jar in the repository.
I deployed it with the same groupId and artifactId as Guava, using <classifier>gwt</classifier> to include it in our GWT modules; i.e.

  <dependency>
    <groupId>com.google.guava</groupId>
    <artifactId>guava</artifact>
    <version>${guava.version}</version>
  </dependency>
  <dependency>
    <groupId>com.google.guava</groupId>
    <artifactId>guava</artifact>
    <version>${guava.version}</version>
    <classifier>gwt</classifier>
  </dependency>

I believe however that the *-gwt.jar should be done differently, using GWT's <super-source> to "redefine" the implementations when GWT-specific code is needed. GWT isn't terribly well integrated with Maven (or is it the other way around?), but what worked well for us (what we use for our own modules) is to simply use the classifier=sources dependency, and bundle the GWT-specific implementations as <super-source> inside it.

FYI, we used both the gwt-maven-plugin and maven-antrun-plugin to launch the GWT compiler. We only do launch the compiler from Maven; we launch GWT's DevMode from within Eclipse.

Do not hesitate to ask if you need to know more.
May 9, 2011
#19 diaz.sal...@gmail.com
@cgruber: responses inline:

> Can you help out by giving us a sense of HOW you use the gwt artifact?  
In short, we have 2 deps in our pom (just like t.broyer)

> At present, do you use the ant-built downloadable one as-is?  
Yes, but the gwt artifact by itself is not useful, the normal artifact is also required (see t.broyer comments about packaging of guava-gwt jar)

> And do you use it via the maven GWT plugins, or how does it fit into your lifecycle?
We use the maven-gwt-plugin to compile GWT client-side code and Google Eclipse Plugin to launch GWT's DevMode

I'll be watching this bug if you need any further comment, but for now it would be enough to deploy the r09 GWT artifact as-is to maven central.

Thanks
Jun 9, 2011
#20 hanrisel...@gmail.com
Hi, any news on this? The guava-gwt artifacts are still not present in maven central. 
Thanks. 
Jul 13, 2011
Project Member #21 kevinb@google.com
(No comment was entered for this change.)
Status: Triaged
Jul 16, 2011
Project Member #22 kevinb@google.com
(No comment was entered for this change.)
Status: Accepted
Aug 2, 2011
#23 kelseyfr...@gmail.com
Any movement on this? We have a GWT library that we'd like to release to Maven Central, but can't because it depends on the guava-gwt artifacts (which aren't yet in Central).
Aug 2, 2011
Project Member #24 kevinb@google.com
We're treating it as a release blocker this time.
Aug 15, 2011
#25 chris.sh...@gmail.com
What's keeping this from being released to Maven Central?  The artifact has already been created, which is typically the hard part.  Do you guys need help generating a pom.xml for it?  If there's anything I can do to help get this artifact into Maven Central, please let me know. 
Aug 21, 2011
#26 sow...@gmail.com
Would be much appreciated, it we could get this on central repo!
Aug 31, 2011
#27 rafalwi...@gmail.com
Just can't wait for this...
Sep 6, 2011
Project Member #28 yrfselrahc@gmail.com
These will be pushed when we push the release candidate.
Status: Fixed
Sign in to add a comment

Powered by Google Project Hosting