JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Feature request JPPF-133  -  Publish JPPF artifacts to maven central
Posted Mar 14, 2013 - updated Dec 27, 2014
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
  • Assigned to
  • Progress
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Category
  • Resolution
  • Priority
  • Targetted for
    icon_milestones.png JPPF 3.3
Issue description
I guess the title says it all smileys/2.png

My understanding of the process involved:
  • sign up with Sonatype (because SourceForge sn't synced with maven central)
  • modify our build scripts to generate the required artifacts: pom, binary, source and javadoc jars and their PGP signatures
  • publish to Sonatype in stages, sync with maven central is automatic once artifacts have been released

Comment posted by
Mar 30, 19:36
I finally managed to deploy a v3.3 snapshot:
Comment posted by
Mar 31, 12:19
This is now implemented - added build scripts to generate the maven artifacts and upload them properly to the sonatype repositories. Changes committed to SVN trunk revision 2673. The first actual release to be in Maven Central will be 3.3

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Confirmed to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • Information about the user working on this issue has been changed, from lolo4j to Not being worked on.
  • Time spent on this issue, from No time spent to 2 days, 12 hours.