Last updated February 27, 2010 11:00, by Fabrizio Giudici
Feedicon  

Artifact names in Phase One (historical)

NBPWR has been designed so the produced artifacts can be consumed by both Maven and Ant projects (in the latter case, with some manual intervention). Since Maven defined a standard structure for naming artifacts, NBPWR follows it borrowing from the coordinates of the original libraries. Given originalGroupId and originalArtifactId, the corresponding NBPWR artifact has got:

  • groupId: com.kenai.nbpwr
  • artifactId: originalGroupId-originalArtifactId where all dots have been replaced by dashes (-).

For instance, SwingX has got:

  • groupId: org.swinglabs
  • artifactId: swingx

so the corresponding NBPWR artifact has got:

  • groupId: com.kenai.nbpwr
  • artifactId: org-swinglabs-swingx

There are many exceptions for original artifacts having incomplete or non-standard coordinates. In this case, the "most important package name" convention is being used. For instance, Apache Commons I/O has got:

  • groupId: commons-io
  • artifactId: commons-io

but the corresponding NBPWR artifact has got:

  • groupId: com.kenai.nbpwr
  • artifactId: org-apache-commons-io

The purpose of the current Phase Two is precisely to sort out this kind of issue and finalize the naming convention. For this reason, it's likely that you find some inconsistencies in the list of artifacts below.

  • Mysql
  • Glassfish
  • Jruby
  • Rails
  • Nblogo
Terms of Use; Privacy Policy;
© 2010, Oracle Corporation and/or its affiliates
(revision 20120127.ac94057)
 
 
Close
loading
Please Confirm
Close