Issue 57 in gwtwiki: Make current Maven repo obsolete and move to Sonatype OSS

[gwt...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 57 by 1983-01...@gmx.net: Make current Maven repo obsolete and
move to Sonatype OSS
http://code.google.com/p/gwtwiki/issues/detail?id=57

The usage of the current repos is cumbersome.
Why?
1. None of the produced artifacts are in Maven Central
2. The repos and to be declared in client POMs over and over again
3. Those who use a repo manager have to nag the admin to add there to the
proxied repo list

Sonatype OSS provides a hosted Maven Repo on Nexus + all release artifacts
will be automatically synched with Maven Central. This will ease the use of
this library.

For more information see here:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

[gwt...@googlecode.com]

Comment #1 on issue 57 by 1983-01...@gmx.net: Make current Maven repo

obsolete and move to Sonatype OSS
http://code.google.com/p/gwtwiki/issues/detail?id=57

Will this ever gonna happen or are we punished with a custom repo forever?

[gwt...@googlecode.com]

Comment #2 on issue 57 by axelclk: Make current Maven repo obsolete and

move to Sonatype OSS
http://code.google.com/p/gwtwiki/issues/detail?id=57

I don't have time at the moment.
If you like to do it, I can give you SVN access.

[gwt...@googlecode.com]

Updates:
Labels: Maven

Comment #3 on issue 57 by axe...@gmail.com: Make current Maven repo

obsolete and move to Sonatype OSS
http://code.google.com/p/gwtwiki/issues/detail?id=57

(No comment was entered for this change.)

[gwt...@googlecode.com]

Updates:
Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low

Comment #4 on issue 57 by axe...@gmail.com: Make current Maven repo

[gwt...@googlecode.com]

Updates:
Status: Started
Owner: axe...@gmail.com

Comment #5 on issue 57 by axe...@gmail.com: Make current Maven repo

obsolete and move to Sonatype OSS
http://code.google.com/p/gwtwiki/issues/detail?id=57

I started to deploy the snapshots:
3.1.01-SNAPSHOT (Java 6 dependent and API changes) and
3.0.20-SNAPSHOT (Java 5 dependent)
https://oss.sonatype.org/content/repositories/snapshots/info/bliki/wiki/
https://oss.sonatype.org/content/groups/public/info/bliki/wiki/

[gwt...@googlecode.com]

Comment #6 on issue 57 by James.Mo...@gmail.com: Make current Maven repo

obsolete and move to Sonatype OSS
http://code.google.com/p/gwtwiki/issues/detail?id=57

While we are waiting for 3.0.20, is there a way you can deploy the
stable .19 release to Sonatype and have that sync to central?

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[gwt...@googlecode.com]

Comment #7 on issue 57 by pedrobss...@gmail.com: Make current Maven repo

obsolete and move to Sonatype OSS
http://code.google.com/p/gwtwiki/issues/detail?id=57

The bundle for 3.0.19 was uploaded to Sonatype. We are currently waiting
for the bundle's promotion.