You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2011/04/30 23:14:04 UTC
[jira] [Created] (UIMA-2134) Tagger build dependency on Whitespace
Tokenizer causes failure for mvn commands which don't build the jar
Tagger build dependency on Whitespace Tokenizer causes failure for mvn commands which don't build the jar
---------------------------------------------------------------------------------------------------------
Key: UIMA-2134
URL: https://issues.apache.org/jira/browse/UIMA-2134
Project: UIMA
Issue Type: Bug
Components: Sandbox-Tagger
Affects Versions: 2.3.1BSF Annotator
Reporter: Marshall Schor
Priority: Minor
Note: This probably should be fixed *after* the 2.3.1addons release.
The Tagger has a dependency on the Whitespace Tokenizer addon component, at the same release level (currently).
This means that if you check out the source, and then do a "mvn test", you get a failure, because
* although Maven correctly orders things so that the build of the WhitespaceTokenizer happens first
* because the Maven command is "mvn test", no *jar* file is built
* and the Tagger tests fail because they are depending on the Jar being built.
The workaround is to run mvn install once, so the right level of the WhitespaceTokenizer is in the local .m2 repo.
The fix could be to change the dependency of the WhitespaceTokenizer to a previous (could be unchanging) release, e.g. the 2.3.0 level. Of course, that can't be done yet, because we haven't released the add-ons to Maven Central (yet) - the last release was to the special repo for incubating projects.
My feeling is to leave this as an issue for the 2.3.1 release, and fix it for the next release by depending on the released 2.3.1 version of the WhitespaceTokenizer.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (UIMA-2134) Tagger build dependency on Whitespace
Tokenizer causes failure for mvn commands which don't build the jar
Posted by "Marshall Schor (Closed) (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-2134.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.4.0Addons
Assignee: Marshall Schor
> Tagger build dependency on Whitespace Tokenizer causes failure for mvn commands which don't build the jar
> ---------------------------------------------------------------------------------------------------------
>
> Key: UIMA-2134
> URL: https://issues.apache.org/jira/browse/UIMA-2134
> Project: UIMA
> Issue Type: Bug
> Components: Sandbox-Tagger
> Affects Versions: 2.3.1Addons
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 2.4.0Addons
>
>
> Note: This probably should be fixed *after* the 2.3.1addons release.
> The Tagger has a dependency on the Whitespace Tokenizer addon component, at the same release level (currently).
> This means that if you check out the source, and then do a "mvn test", you get a failure, because
> * although Maven correctly orders things so that the build of the WhitespaceTokenizer happens first
> * because the Maven command is "mvn test", no *jar* file is built
> * and the Tagger tests fail because they are depending on the Jar being built.
> The workaround is to run mvn install once, so the right level of the WhitespaceTokenizer is in the local .m2 repo.
> The fix could be to change the dependency of the WhitespaceTokenizer to a previous (could be unchanging) release, e.g. the 2.3.0 level. Of course, that can't be done yet, because we haven't released the add-ons to Maven Central (yet) - the last release was to the special repo for incubating projects.
> My feeling is to leave this as an issue for the 2.3.1 release, and fix it for the next release by depending on the released 2.3.1 version of the WhitespaceTokenizer.
--
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] [Updated] (UIMA-2134) Tagger build dependency on Whitespace
Tokenizer causes failure for mvn commands which don't build the jar
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-2134:
---------------------------------
Affects Version/s: (was: 2.3.1BSF Annotator)
2.3.1Addons
> Tagger build dependency on Whitespace Tokenizer causes failure for mvn commands which don't build the jar
> ---------------------------------------------------------------------------------------------------------
>
> Key: UIMA-2134
> URL: https://issues.apache.org/jira/browse/UIMA-2134
> Project: UIMA
> Issue Type: Bug
> Components: Sandbox-Tagger
> Affects Versions: 2.3.1Addons
> Reporter: Marshall Schor
> Priority: Minor
>
> Note: This probably should be fixed *after* the 2.3.1addons release.
> The Tagger has a dependency on the Whitespace Tokenizer addon component, at the same release level (currently).
> This means that if you check out the source, and then do a "mvn test", you get a failure, because
> * although Maven correctly orders things so that the build of the WhitespaceTokenizer happens first
> * because the Maven command is "mvn test", no *jar* file is built
> * and the Tagger tests fail because they are depending on the Jar being built.
> The workaround is to run mvn install once, so the right level of the WhitespaceTokenizer is in the local .m2 repo.
> The fix could be to change the dependency of the WhitespaceTokenizer to a previous (could be unchanging) release, e.g. the 2.3.0 level. Of course, that can't be done yet, because we haven't released the add-ons to Maven Central (yet) - the last release was to the special repo for incubating projects.
> My feeling is to leave this as an issue for the 2.3.1 release, and fix it for the next release by depending on the released 2.3.1 version of the WhitespaceTokenizer.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira