[
https://issues.apache.org/jira/browse/STANBOL-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182519#comment-13182519
]
Ali Anil Sinaci commented on STANBOL-446:
-----------------------------------------
Parent POM of Contenthub provides a Bundle-Category for the bundles under
Contenthub. This is also the case for Entityhub and Enhancer. I guess
Bundle-Category is the category information for each bundle that we can see
from the Felix console. I prefer to keep it for this reason.
On the other hand, I can move the dependencies to Stanbol's parent (so, parent
pom for contenthub will exist, but it will have no dependencies), however I
need to try whether it will lead to conflicts or not. For example, we need
jersey-client with a "provided" scope, but in Stanbol's parent its scope is
"test". I will try to change it to "provided" and be sure there will be no
conflict and apply the changes in my next patch.
> Remove ContentHub parent POM
> ----------------------------
>
> Key: STANBOL-446
> URL: https://issues.apache.org/jira/browse/STANBOL-446
> Project: Stanbol
> Issue Type: Bug
> Reporter: Fabian Christ
> Assignee: Suat Gonul
> Labels: Dependencies
>
> The ContentHub has its own parent POM which inherits from the global parent
> POM. It is unclear why the ContentHub needs its own parent POM. Versions of
> artifacts should be defined in the global parent POM.
> Therefore, the ContentHub parent POM should be removed as it is not needed.
--
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
