bugKawa - Bugs: bug #38311, FR: Publish Kawa 1.13 to Maven...

 
 

bug #38311: FR: Publish Kawa 1.13 to Maven Repository

Submitted by:  Daniel Gregoire <semperos>
Submitted on:  Tue 12 Feb 2013 04:24:29 AM UTC  
 
Category: NoneSeverity: 3 - Normal
Item Group: Feature RequestStatus: None
Privacy: PublicAssigned to: None
Open/Closed: Open

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission Jump to the original submission)

Mon 25 Feb 2013 04:23:10 AM UTC, comment #6:

Adding this here not to lose it.

https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement

This lists the required fields in the POM configuration file, as well as the three artifacts that need to be generated (namely, the main JAR, a JAR dedicated to Javadocs, and a JAR with the original sources).

Using Sonatype will allow Kawa a great deal of flexibility. The repository supports not only release builds, but also SNAPSHOT builds if desired, and provides an automatic migration path such that release JAR's reach Maven central without any extra work on our part.

Daniel Gregoire <semperos>
Tue 12 Feb 2013 10:22:28 PM UTC, comment #5:

Great. Thanks.

Per Bothner <bothner>
Project Administrator
Tue 12 Feb 2013 10:15:20 PM UTC, comment #4:

That's fair enough, and I'm happy to contribute in any way that I can. If it ever becomes an issue, I can always transfer ownership back to you or someone else.

I'll make the groupId "org.gnu.kawa" and the artifact id "kawa", so folks will be able to add it as a dependency with the following:

<dependency>
<groupId>org.gnu.kawa</groupId>
<artifactId>kawa</artifactId>
<version>1.13</version>
</dependency>

The packaging in Kawa's source obviously uses "gnu.kawa", but I see other GNU Maven artifacts modeled like the above. Let me know if this presents an issue.

In the mean time, I'll research how to get JAR's posted to Maven Central.

Daniel Gregoire <semperos>
Tue 12 Feb 2013 09:41:37 PM UTC, comment #3:

I see no reason why I can't delegate to you to create and maintain an official Kawa Maven entry.

Technically Kawa is a GNU project. Currently, I make the decisions and do most of the work, and I'm the only one checking in patches. However, it would be nice if we could have more people do more of the work (and I could relax my control-freakism ...). Letting you handle the Maven aspects seems a no-brainer.

Per Bothner <bothner>
Project Administrator
Tue 12 Feb 2013 03:16:33 PM UTC, comment #2:

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.

Daniel Gregoire <semperos>
Tue 12 Feb 2013 08:15:14 AM UTC, comment #1:

I don't remember releasing Kawa for Maven, and I don't know what's involved. Is there any reason you can't do it?

Per Bothner <bothner>
Project Administrator
Tue 12 Feb 2013 04:24:29 AM UTC, original submission:

I see that you made a release to Maven Central for Kawa 1.7 back in 2005. I'm opening this issue to request that you release 1.13 to Maven Central as well.

I'm writing a simple build library for compiling web client-side assets like CoffeeScript, LESS, etc., using a simple Java stack. I'm already including Kawa as a scripting language (via javax.script) to allow folks to easily script their builds.

I use Maven for dependency and build management. It would make the build more consistent and reliable if folks could download Kawa as a dependency from Maven Central (or other public Maven repository of your choosing), instead of me adding instructions to manually download and install it.

If this is a burden, please let me know if there is anything I can do to help. Thanks for a great piece of software.

Daniel Gregoire <semperos>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by bothner (Posted a comment)
  • -unavailable- added by semperos (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    No Changes Have Been Made to This Item

    Back to the top


    Powered by Savane 3.1-cleanup