The Camel committer has the right to upload file to this url.
It's just like you create a new directory and commit it into the svn
repository.
Willem
Claus Ibsen wrote:
On Mon, Nov 9, 2009 at 2:51 AM, Willem Jiang <willem.ji...@gmail.com> wrote:
+1 to upload to GAE API to https://svn.apache.org/repos/asf/camel/m2-repo/
so we can get full control of it in camel.
If SMX wants to use the artifacts from upper url, we can add a repository
ref for it in its feature :)
Who has access to be able to upload to this repo?
Willem
Martin Krasser wrote:
I attached the jars to
https://issues.apache.org/activemq/browse/CAMEL-2085 because I don't have
write permissions to the SMX repo.
Alternatively, we could add the jars to
https://svn.apache.org/repos/asf/camel/m2-repo/ then I could do the upload
myself and update it as soon as newer SDK version are released.
What do you prefer?
Claus Ibsen schrieb:
On Sat, Nov 7, 2009 at 11:59 AM, Martin Krasser <d...@martin-krasser.de>
wrote:
I forgot to mention that I couldn't find a Maven repo that contains the
most
recent GAE SDK. The 'official' Google Code project for maintaining such
a
repository is http://code.google.com/p/google-maven-repository but the
latest SDK version there is 1.2.1. Requests for adding newer versions
haven't been followed yet.
Bad bad Google!
This is always a problem with Maven when artifacts is not updated to
well known repos in timely manner.
There is the Apache SMX repo which have many jars as well. We could
consider uploading it there. Camel does fetch some .jars from this
repo already.
Martin Krasser schrieb:
I'm currently working on Camel components for the Google App Engine
(see
CAMEL-2085) and have dependencies to the GAE APIs that are part of the
GAE
SDK. To which Maven repo should they go to (and how do I get them
there)? I
currently have them deployed to the Open eHealth Maven repository but
this
should only be a temporary solution.
Thanks in advance for any help,
Martin
