[STANBOL-619] Modify OWLAPI maven groupId and artifactIds

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: commons-0.11.0
• Component/s: Commons
• Assignee: Unassigned
• Reporter: Peter Ansell
• Created: 18/May/12 02:59
• Updated: 22/Jan/13 12:08
• Resolved: 26/Jun/12 17:25

Description

Currently the owlapi groupId and versionId that stanbol is using is "owlapi" and "owlapi"

Even though I don't think the full set of OWLAPI maven modules are currently in maven central, would it be possible to change to using references to the groupId and artifactIds that are used by the OWLAPI project in their current subversion trunk.

The standard groupId is:

<groupId>net.sourceforge.owlapi</groupId>

The module that you will likely want to pull in for API references is owlapi-api [1], while the module that you will likely want to pull in for a complete set of API and implementations (including OWLManager) is owlapi-apibinding [2].

Although the main goal is to standardise these identifiers so that things will just work when the modules are released on maven central, these changes would make it much easier for me to substitute my patched owlapi for the version that you are using [3].

[1] http://owlapi.svn.sourceforge.net/viewvc/owlapi/v3/trunk/api/pom.xml
[2] http://owlapi.svn.sourceforge.net/viewvc/owlapi/v3/trunk/apibinding/pom.xml
[3] https://github.com/ansell/owlapi

Issue Links

• is related to: STANBOL-265 Remove embedded maven repository for owlapi dependency
• relates to: STANBOL-626 Update OWL-API to version 3.3