You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Peter Ansell (Created) (JIRA)" <ji...@apache.org> on 2012/04/18 05:47:14 UTC
[jira] [Created] (STANBOL-588) Commons modules should not have
dependencies outside of commons
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
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_2BKp8SHDPA@mail.gmail.com%3E
https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3CCA+_sZ+gLuCc4_Ua1BNwAk8BMKi8QQv5g10XDtGjp3_Cwki1Z-g@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
[jira] [Commented] (STANBOL-588) Commons modules should not have
dependencies outside of commons
Posted by "Alessandro Adamou (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256543#comment-13256543 ]
Alessandro Adamou commented on STANBOL-588:
-------------------------------------------
To the best of my knowledge, the core dependency outside of commons is the object model for content items, enhancements etc., which was originally developed as part of the Stanbol Enhancer API and never moved out of it since.
Given that other modules are using that object model now, perhaps the time would be right for making a commons/contentapi or something like that.
> 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
> 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_2BKp8SHDPA@mail.gmail.com%3E
> https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3CCA+_sZ+gLuCc4_Ua1BNwAk8BMKi8QQv5g10XDtGjp3_Cwki1Z-g@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
[jira] [Commented] (STANBOL-588) Commons modules should not have
dependencies outside of commons
Posted by "Peter Ansell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278535#comment-13278535 ]
Peter Ansell commented on STANBOL-588:
--------------------------------------
The current trunk reactor ( 0.10.0-incubating-SNAPSHOT) looks much cleaner. Thanks, Peter
> 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_2BKp8SHDPA@mail.gmail.com%3E
> https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3CCA+_sZ+gLuCc4_Ua1BNwAk8BMKi8QQv5g10XDtGjp3_Cwki1Z-g@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
[jira] [Commented] (STANBOL-588) Commons modules should not have
dependencies outside of commons
Posted by "Fabian Christ (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256569#comment-13256569 ]
Fabian Christ commented on STANBOL-588:
---------------------------------------
I think Rupert did already some improvements on this. But we should definitely have a closer look.
Thanks, Peter!
> 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
> 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_2BKp8SHDPA@mail.gmail.com%3E
> https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3CCA+_sZ+gLuCc4_Ua1BNwAk8BMKi8QQv5g10XDtGjp3_Cwki1Z-g@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
[jira] [Commented] (STANBOL-588) Commons modules should not have
dependencies outside of commons
Posted by "Peter Ansell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279899#comment-13279899 ]
Peter Ansell commented on STANBOL-588:
--------------------------------------
A clean install still fails with the following error, indicating a dependency between commons and data, but there are no dependencies in the other direction, so it is possible to run mvn clean install on the data pom without having to pull in the rest of stanbol.
[ERROR] Failed to execute goal on project org.apache.stanbol.commons.opennlp: Could not resolve dependencies for project org.apache.stanbol:org.apache.stanbol.commons.opennlp:bundle:0.10.0-incubating-SNAPSHOT: Could not find artifact org.apache.stanbol:org.apache.stanbol.data.opennlp.lang.en:jar:1.0.2-incubating-SNAPSHOT in apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1]
You can close it if you think that it is necessary for commons.opennlp to have a dependency on the data files. I would not have thought that this would be necessary for the commons module from a naive point of view, but I am not familiar with the actual code.
> 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_2BKp8SHDPA@mail.gmail.com%3E
> https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3CCA+_sZ+gLuCc4_Ua1BNwAk8BMKi8QQv5g10XDtGjp3_Cwki1Z-g@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
[jira] [Commented] (STANBOL-588) Commons modules should not have
dependencies outside of commons
Posted by "Peter Ansell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279917#comment-13279917 ]
Peter Ansell commented on STANBOL-588:
--------------------------------------
In addition, the stanbol-parent pom also needs to be manually installed if it is not present in a repository on the web, ie:
cd stanbol/parent/
mvn clean install
> 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_2BKp8SHDPA@mail.gmail.com%3E
> https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3CCA+_sZ+gLuCc4_Ua1BNwAk8BMKi8QQv5g10XDtGjp3_Cwki1Z-g@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
[jira] [Resolved] (STANBOL-588) Commons modules should not have
dependencies outside of commons
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-588.
-----------------------------------------
Resolution: Fixed
commons dos no longer depend on other Stanbol modules. The dependency to data is intended and needed for unit tests..
> 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_2BKp8SHDPA@mail.gmail.com%3E
> https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3CCA+_sZ+gLuCc4_Ua1BNwAk8BMKi8QQv5g10XDtGjp3_Cwki1Z-g@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
[jira] [Assigned] (STANBOL-588) Commons modules should not have
dependencies outside of commons
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ 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_2BKp8SHDPA@mail.gmail.com%3E
> https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3CCA+_sZ+gLuCc4_Ua1BNwAk8BMKi8QQv5g10XDtGjp3_Cwki1Z-g@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
[jira] [Commented] (STANBOL-588) Commons modules should not have
dependencies outside of commons
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258824#comment-13258824 ]
Rupert Westenthaler commented on STANBOL-588:
---------------------------------------------
Yes I removed two dependencies of commons to other components (BTW: both where test level dependencies). So maybe this is already resolved, but there might be also additional unwanted dependencies.
I will assign this to me and test the current trunk for it.
> 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
> 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_2BKp8SHDPA@mail.gmail.com%3E
> https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3CCA+_sZ+gLuCc4_Ua1BNwAk8BMKi8QQv5g10XDtGjp3_Cwki1Z-g@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
[jira] [Commented] (STANBOL-588) Commons modules should not have
dependencies outside of commons
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278689#comment-13278689 ]
Rupert Westenthaler commented on STANBOL-588:
---------------------------------------------
Does that mean that we can close this?
> 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_2BKp8SHDPA@mail.gmail.com%3E
> https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3CCA+_sZ+gLuCc4_Ua1BNwAk8BMKi8QQv5g10XDtGjp3_Cwki1Z-g@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
[jira] [Commented] (STANBOL-588) Commons modules should not have
dependencies outside of commons
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280117#comment-13280117 ]
Rupert Westenthaler commented on STANBOL-588:
---------------------------------------------
The dependency to "o.a.s.data.opennlp.lang.en" is required by the unit tests of the o.a.s.commons.opennlp bundle. As soon as OpenNLP provides models that are compatible with the Apache License we can remove that by adding the required data files directly to the test resources. For now I would prefer to keep it as it is.
> 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_2BKp8SHDPA@mail.gmail.com%3E
> https://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201203.mbox/%3CCA+_sZ+gLuCc4_Ua1BNwAk8BMKi8QQv5g10XDtGjp3_Cwki1Z-g@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