[
https://issues.apache.org/jira/browse/STANBOL-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler reassigned STANBOL-588:
-------------------------------------------
Assignee: Rupert Westenthaler
> Commons modules should not have dependencies outside of commons
> ---------------------------------------------------------------
>
> Key: STANBOL-588
> URL: https://issues.apache.org/jira/browse/STANBOL-588
> Project: Stanbol
> Issue Type: Bug
> Components: Commons
> Affects Versions: 0.9.0-incubating
> Reporter: Peter Ansell
> Assignee: Rupert Westenthaler
> Labels: maven
>
> The commons module currently has dependencies on other modules, which makes
> it difficult or impossible to selectively compile different parts of stanbol
> using the second level maven pom.xml files. For example commons/pom.xml does
> not compile from scratch as it requires modules from enhancer/pom.xml, which
> requires different modules from commons/pom.xml.
> The stanbol parent reactor compiles things correctly as there aren't any
> circular dependencies between the actual modules, just between the second
> level pom.xml files.
> Hence this issue only affects people who try to compile commons on its own:
> To replicate the issue run:
> $ cd commons
> $ mvn clean install
> This command currently fails due to unresolved dependency on
> org.apache.stanbol.enhancer.servicesapi , which itself has a dependency on a
> module from commons that was not compiled using the mvn clean install, so
> even running mvn clean install in the enhancer directory first fails as
> commons is required.
> See email thread from mailing list for background:
> https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3ccagyfocqu8bv9hqdmrrhqa4dnjckvstynnpqpwgt_2bkp8sh...@mail.gmail.com%3E
> https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3cca+_sz+glucc4_ua1bnwak8bmki8qqv5g10xdtgjp3_cwki1...@mail.gmail.com%3E
--
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
