Open GoogleCodeExporter opened 9 years ago
Since this project is open-source and the JARs are here, could you do it
yourself?
Original comment by pamela.fox
on 1 Oct 2009 at 4:58
It's not really appropriate or easy for a non-project owner to upload jars to
Maven
repositories. I would say it is in your interest as much or more than mine,
since it
will drive adoption. I can provide some POM meta data if you want to get
started,
but that really belongs in your source code repository, so it needs to be owned
and
maintained by a committer (which is already a good reason why it should be the
project's responsibility, not the users').
There is a guide to uploading here:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html. In
particular notice that it requires some infrastructure to be set up to sync
from and
that you must "provide proof of owning the domain" that the code originates
from. A
project member is much more likely to be able to do that.
I notice that there are already several feeds from Google and googlecode, so it
looks
like its a feature provided by the infrastructure of your project already.
Greg Kick
(gak@google.com) is listed as owning the sync site at
https://google-maven-repository.googlecode.com/svn/repository/. Maybe you can
ask
him for help (say "hi" to him from me if you do)?
Original comment by david.s...@googlemail.com
on 1 Oct 2009 at 10:47
As someone who builds a lot of java code with maven, I concur that it should be
Google project member who deploys built jar files to public maven repository.
Original comment by moni...@gmail.com
on 1 Oct 2009 at 1:02
Has any action been taken on this? I would find having the wave robot API
published
on a maven repository very helpful, event if it's not on Central.
What additional information is needed for this to move forward?
Please list the repository and artifact coordinates once it is uploaded, or
post them
if they've already been posted.
Thanks!
Jim
Original comment by jimbetha...@gmail.com
on 16 Dec 2009 at 3:36
please resolve this asap, I'm used to using maven to manage my dependencies,
and I
don't really like manually importing newer versions of jars to my local repo
once
they come out
Original comment by yar...@gmail.com
on 14 Mar 2010 at 2:21
Agreed all the wave deps for java should be in maven central. This has been the
standard in java projects for a while. Projects owners should install in maven
central. Also all examples would gain widespread adoption if they were exposed
as
maven artifacts so you could get them up and running with sources with a single
command
Original comment by raulr...@gmail.com
on 15 May 2010 at 8:11
Original issue reported on code.google.com by
david.s...@googlemail.com
on 23 Jul 2009 at 8:42