[
https://issues.apache.org/jira/browse/STANBOL-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler resolved STANBOL-619.
-----------------------------------------
Resolution: Fixed
The groupid is now changed to "net.sourceforge.owlapi". In trunk owlapi 3.2.3
is provided by an embedded maven repository of the
"org.apache.stanbol.commons.owl" module that also export its.
As soon as owlapi is available on maven central one needs only to change the
"org.apache.stanbol.commons.owl" and checks that all the other components do
work with the new version.
> Modify OWLAPI maven groupId and artifactIds
> -------------------------------------------
>
> Key: STANBOL-619
> URL: https://issues.apache.org/jira/browse/STANBOL-619
> Project: Stanbol
> Issue Type: Improvement
> Components: Commons
> Reporter: Peter Ansell
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
