Open GoogleCodeExporter opened 9 years ago
There is a guide on how to do this here:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
Essentially the pom needs to contain the required information, someone needs to
prove ownership, and then it
can be added.
Original comment by steve.sw...@gmail.com
on 17 Mar 2010 at 10:12
[deleted comment]
I have a Maven-based project, HTTPBuilder
(http://groovy.codehaus.org/modules/http-builder) which I'd like to migrate to
your OAuth client from signpost.
Unless the OAuth artifacts are in Maven central, my options are to either
include your source in my project (both ASL 2.0 licensed) or maybe push the
artifacts to the codehaus repo so the dependencies are accessible to my users.
Original comment by tmnich...@gmail.com
on 9 Mar 2011 at 4:00
Please upload the latest build to Maven Central. It will make life much easier.
Thanks.
Original comment by pankaj.j...@gmail.com
on 4 Jun 2011 at 7:26
I'd like to second this issue and suggest that you deploy your artifacts to
Maven Central. This way the artifacts are easier to consume because consumers
don't need to have repositories added to their poms or wait on their corporate
maven repo maintainers to add a new repository .
The steps are very well documented at
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage
+Guide . I've done them for a number of OSS projects, so I can help you if
needed.
Original comment by robert.munteanu
on 13 Mar 2012 at 3:26
any comments? this will make our adoption much easier and standards compliant..
is anyone coding on this project any longer?
Original comment by fern...@gmail.com
on 9 Aug 2012 at 3:49
Original issue reported on code.google.com by
lind...@inuus.com
on 12 Mar 2010 at 7:59