[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-kawa] [bug #38311] FR: Publish Kawa 1.13 to Maven Repository
From: |
Daniel Gregoire |
Subject: |
[Bug-kawa] [bug #38311] FR: Publish Kawa 1.13 to Maven Repository |
Date: |
Tue, 12 Feb 2013 15:16:33 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.17 (KHTML, like Gecko) Ubuntu Chromium/24.0.1312.56 Chrome/24.0.1312.56 Safari/537.17 |
Follow-up Comment #2, bug #38311 (project kawa):
Perhaps you didn't release it. I was just looking at the project information
you can see on the right pane of this page, and assumed it was you:
http://search.maven.org/#artifactdetails%7Ckawa%7Ckawa%7C1.7%7Cjar
Whoever posted that JAR now has ownership of the kawa/kawa group and artifact
id's. In general, whoever "owns" a project takes control of the appropriate
group and artifact id's for Maven, so no one else can post malicious JAR's
posing as yours, etc. I've not posted to Maven Central specifically before,
but for posting to things like Clojure's Maven repository Clojars, I was only
required to create an account and register an SSH public key. I then just scp
the pom.xml and JAR file of a release to post a new version of a Clojure
library to that Maven repository, which just becomes another step in my
release build process.
If you're not a Maven user, I'd be happy to contribute a stripped-down pom.xml
file that would satisfy Kawa's needs for being posted to a Maven repo.
If you're not inclined to add this, I could post a JAR of Kawa myself, and I
would do it as something like "com.semperos/kawa" so it'd be clear it wasn't
official. I just thought it'd be good to have there from you, so folks who
approach trying out Java tools using Maven would have an easy time pulling in
the latest Kawa.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?38311>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/