Artefacts not published to Maven Central

[GoogleCodeExporter]

While publishing to a custom repository is fine for standalone users, not 
existing in Maven Central is an issue for those users in a corporate 
environment where they do not have control over their maven repository & are 
not able to add new custom repositories to their poms.

It would be great if you could start publishing to Central in future.

Original issue reported on code.google.com by louis.em...@gmail.com on 21 Mar 2012 at 9:12

[GoogleCodeExporter]

My plan was to start publishing in Central when I'd have a 1.0 version, but I 
must admit I'm far from it... So yes, I think it's time to do it.

I will release a 0.37 version this weekend and then will follow the steps to 
publish on Sonatype OSS Maven repository (which is sync with Central : 
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage
+Guide)

For that, I will change the gwt-test-utils groupId, which will become 
"com.googlecode" and rename every package to match it.
I'll also try to use classifiers for the different versions of gwt-test-utils.

Original comment by gael.laz...@gmail.com on 21 Mar 2012 at 11:10

• Changed state: Accepted

[GoogleCodeExporter]

I've open a ticket at sonatype to host gwt-test-utils artifact : 
https://issues.sonatype.org/browse/OSSRH-3191

I also decided to change gwt-test-utils groupId from 'com.octo.gwt.test' to 
'com.googlecode' and to rename each java package in accordingly (com.octo.xxx 
to com.googlecode.xxx)

Original comment by gael.laz...@gmail.com on 23 Mar 2012 at 9:21

• Changed state: Started

[GoogleCodeExporter]

That's it, the first releases of gwt-test-utils are now available on Maven 
Central :

0.38 : for GWT 2.4
0.33.3 : for GWT 2.3.0
0.28.10 : for GWT 2.2.0
0.25.7 : for GWT 2.1.0 and 2.1.1
0.22.7 : for GWT 2.0.2, 2.0.3 and 2.0.4

Enjoy ;-)

Original comment by gael.laz...@gmail.com on 2 Apr 2012 at 8:15

• Changed state: Done
• Added labels: Type-Enhancement
• Removed labels: Type-Defect