[Bug-kawa] [bug #38311] FR: Publish Kawa 1.13 to Maven Repository

[Daniel Gregoire]

Follow-up Comment #10, bug #38311 (project kawa):

As long as the release blessed by this project uses something like a group ID
of org.gnu.kawa and an artifact ID of kawa, folks will see that as more
reputable and will also see the more recent release date.

You can certainly publish a JAR to Maven Central via Sonatype simply with the
the JAR and a correctly-formatted pom.xml file. I think the long-term solution
to keeping Kawa releases available on Maven Central is to tackle a small-scale
Mavenization of Kawa that defers to the existing Ant scripts that already
build the project, which can be done without changing the Ant side of things
by using the Maven AntRun plugin.

Another question that releasing Kawa on Maven raises is: should the separate
libraries, like gnu.bytecode, be released independently from Kawa? Kawa stands
right now as a jar-with-dependencies, but since it's also designed as a
language-building framework, it might make sense to consider releasing those
sub-projects independently as well.

Sorry not to be more helpful. Here's a project that I released on Maven
Central; the README includes detailed instructions of how I released both
staging and production releases via Sonatype, and the pom.xml file includes
everything required by Maven Central:

https://github.com/semperos/screwdriver

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?38311>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/