[jira] Commented: (UIMA-1543) Missing version tags in uimaj-distr POM
[ https://issues.apache.org/jira/browse/UIMA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12750867#action_12750867 ] Tommaso Teofili commented on UIMA-1543: --- version tag should be present in each dependency according to maven good practices but I'm not sure if this is true also if the parent POM specifiies versions, so maybe it's ok to not doing it in uimaj-distr POM. I'll think about it a little more. Missing version tags in uimaj-distr POM - Key: UIMA-1543 URL: https://issues.apache.org/jira/browse/UIMA-1543 Project: UIMA Issue Type: Bug Components: Build, Packaging and Test Affects Versions: 2.3S Reporter: Tommaso Teofili Fix For: 2.3 uimaj-distr POM miss version tag in each dependency so the POM is invalid -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1546) Fix sandbox notice and license files
Fix sandbox notice and license files Key: UIMA-1546 URL: https://issues.apache.org/jira/browse/UIMA-1546 Project: UIMA Issue Type: Bug Components: Sandbox Reporter: Thilo Goetz Assignee: Thilo Goetz Fix For: 2.3S Review all sandbox notice and license files. Make sure top-level notice and license files are aggregates of the component ones. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-769) AnnotationEditor should support undo and redo
[ https://issues.apache.org/jira/browse/UIMA-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-769: --- Description: Modifications in the Annotation Editor should be undone and redone. Affects Version/s: 2.3 defer past 2.3.0 AnnotationEditor should support undo and redo - Key: UIMA-769 URL: https://issues.apache.org/jira/browse/UIMA-769 Project: UIMA Issue Type: Improvement Components: CasEditor Affects Versions: 2.3 Reporter: Jörn Kottmann Assignee: Jörn Kottmann Priority: Minor Modifications in the Annotation Editor should be undone and redone. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-766) The Annotation Editor is not a reliable drag source for annotations
[ https://issues.apache.org/jira/browse/UIMA-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-766: --- Affects Version/s: 2.3 defer past 2.3.0 The Annotation Editor is not a reliable drag source for annotations --- Key: UIMA-766 URL: https://issues.apache.org/jira/browse/UIMA-766 Project: UIMA Issue Type: Bug Components: CasEditor Affects Versions: 2.3 Reporter: Jörn Kottmann Assignee: Jörn Kottmann Priority: Minor Its possible to drag annotations from the annotation editor. Tough this does not work very well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-710) Show error symbol on file icon in the Corpus Explorer if the file has an error
[ https://issues.apache.org/jira/browse/UIMA-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-710: --- Affects Version/s: 2.3 Remaining Estimate: (was: 8h) Original Estimate: (was: 8h) defer past 2.3.0 Show error symbol on file icon in the Corpus Explorer if the file has an error -- Key: UIMA-710 URL: https://issues.apache.org/jira/browse/UIMA-710 Project: UIMA Issue Type: Improvement Components: CasEditor Affects Versions: 2.3 Reporter: Jörn Kottmann Assignee: Jörn Kottmann Priority: Trivial If a file contains an error the error symbol should be shown on the file icon in the corpus explorer and parent elements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-560) Cas Editor: Add a drag source to the FSView
[ https://issues.apache.org/jira/browse/UIMA-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-560: --- Affects Version/s: 2.3 defer past 2.3.0 Cas Editor: Add a drag source to the FSView --- Key: UIMA-560 URL: https://issues.apache.org/jira/browse/UIMA-560 Project: UIMA Issue Type: Improvement Components: CasEditor Affects Versions: 2.3 Reporter: Jörn Kottmann Assignee: Jörn Kottmann Priority: Minor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-767) Use eclipse content types to identify annotators descriptors (.ann) and consumer descriptors (.con)
[ https://issues.apache.org/jira/browse/UIMA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-767: --- Fix Version/s: 2.3 Use eclipse content types to identify annotators descriptors (.ann) and consumer descriptors (.con) --- Key: UIMA-767 URL: https://issues.apache.org/jira/browse/UIMA-767 Project: UIMA Issue Type: Improvement Components: CasEditor Reporter: Jörn Kottmann Assignee: Jörn Kottmann Priority: Minor Fix For: 2.3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-556) Cas Editor: Add drag n drop to the corpus explorer view
[ https://issues.apache.org/jira/browse/UIMA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-556: --- Affects Version/s: 2.3 defer past 2.3.0 Cas Editor: Add drag n drop to the corpus explorer view --- Key: UIMA-556 URL: https://issues.apache.org/jira/browse/UIMA-556 Project: UIMA Issue Type: Improvement Components: CasEditor Affects Versions: 2.3 Reporter: Jörn Kottmann Assignee: Jörn Kottmann Priority: Minor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-557) Cas Editor: Annotator Runner should show log output of the AE
[ https://issues.apache.org/jira/browse/UIMA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-557: --- Affects Version/s: 2.3 defer past 2.3.0 Cas Editor: Annotator Runner should show log output of the AE - Key: UIMA-557 URL: https://issues.apache.org/jira/browse/UIMA-557 Project: UIMA Issue Type: Improvement Components: CasEditor Affects Versions: 2.3 Reporter: Jörn Kottmann Assignee: Jörn Kottmann Priority: Minor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Fwd: Committer info
Redirecting this thread to uima-dev, may be useful information for other people as well. Tommaso Teofili wrote: Thanks a lot Marshall for being so helpful. Recently I was reading something related to svn log, is there something to do related to it? I don't think so - but maybe I'm not following... Can you be more specific? or give a pointer? in a previous email on uima-commits I saw something like: Author: schor Revision: 719734 Modified property: svn:log Modified: svn:log at Fri Jul 31 11:55:39 2009 -- --- svn:log (original) +++ svn:log Fri Jul 31 11:55:39 2009 @@ -1 +1 @@ .. Tommaso That just means that the commit log was modified after the fact. If you have forgotten to add a commit comment with the jira number or some other important information, you can later add that. The most important information in the commit log is, as Marshall said, the Jira issue number like UIMA-1234. This allows us to go back to Jira and look at the discussion surrounding a commit. Conversely, this number allows Jira to associate subversion commits with an issue. So you can click on the Subversion Commits tab in a Jira issue and see all the commits for an issue. I also like to put the URL to a Jira issue in the commit comment, because I'm lazy and this allows me to just click on the link in the commit message and I don't have to copy and paste the issue number into the Jira search field: https://issues.apache.org/jira/browse/UIMA-1234 But that's just me, it's not a general rule. --Thilo
[jira] Updated: (UIMA-1174) Add Find/Annotate keyboard shortcut
[ https://issues.apache.org/jira/browse/UIMA-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-1174: Affects Version/s: 2.3 defer past 2.3.0 Add Find/Annotate keyboard shortcut --- Key: UIMA-1174 URL: https://issues.apache.org/jira/browse/UIMA-1174 Project: UIMA Issue Type: Improvement Components: CasEditor Affects Versions: 2.3 Reporter: Jörn Kottmann Assignee: Jörn Kottmann Priority: Minor Create a keyboard shortcut to add annotations for all parts of the document which match the current selection. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
CPM test case hang
Hi all, has anything changed in the CPM recently? I get a reliable test case hang here (no cpu activity): --- T E S T S --- Running org.apache.uima.collection.impl.cpm.CpmProcessingTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.344 sec Running org.apache.uima.collection.impl.cpm.CasPoolTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.125 sec Running org.apache.uima.collection.impl.cpm.CpmInitTest Initialize was called: true Sep 3, 2009 10:50:48 AM org.apache.uima.collection.impl.cpm.BaseCPMImpl process WARNING: Processing the request to stop the CPM. (Thread Name: main) Sep 3, 2009 10:50:48 AM org.apache.uima.collection.impl.cpm.engine.CPMEngine process INFO: The collection reader thread state is: 2007 (Thread Name: main) I have to kill the process, so I don't have more info than this. It only happens with this jvm (on windows): java version 1.5.0 Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20090707 (SR10 )) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20090707 (JIT enabled) J9VM - 20090706_38445_lHdSMr JIT - 20090623_1334_r8 GC - 200906_09) JCL - 20090705 I tried 3 others, and it goes through with all of them: java version 1.6.0 Java(TM) SE Runtime Environment (build pwi3260sr5-20090529_04(SR5)) IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr5-20090519_35743 (JIT enabled, AOT enabled) J9VM - 20090519_035743_lHdSMr JIT - r9_20090518_2017 GC - 20090417_AA) JCL - 20090529_01 java version 1.5.0_11 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode) java version 1.6.0_13 Java(TM) SE Runtime Environment (build 1.6.0_13-b03) Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode) Let me know if you need more information. --Thilo
Compiling project in sandbox (was: Can we update the version of Tika in the TikaAnnotator to 0.4)
Hi, I was having the same problem as Jorn using the default version of Maven from Ubuntu. I have upgraded it to 2.2.1 and can now build UIMA but still cannot build the TikaAnnotator. When doing svn install in the TikaAnnotator directory I am getting : *Reason: Cannot find parent: org.apache.uima:SandboxDistr for project: org.apache.uima:TikaAnnotator:jar:2.3.0-incubating-SNAPSHOT for project org.apache.uima:TikaAnnotator:jar:2.3.0-incubating-SNAPSHOT* I then tried to build SandboxDistr but am getting : *antrun:run {execution: CopyLicenseNoticeDisclaimer}] [INFO] Executing tasks [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An Ant BuildException has occured: /usr/local/bin/uimaj-distr/src/main/readme not found.* whereas my uimaj-distr is actually located in a different directory (* /usr/local/bin/uima-svn/uimaj-distr* with the sandbox in*/usr/local/bin/uima-sandbox-svn *). Is there an implicit requirement for the sandbox to be located within the main UIMA directory? Once the sandbox is put inside the main uima dir everything compiles OK. Thanks Julien Won't have time to look into this in the short term but can try at some point next week. Maybe someone with more experience of Maven can give it a try first and see if it compiles OK? I tried this and it compiled OK. I had success with the following (requires maven to be installed): cd to directory TikaAnnotator mvn install That builds it, builds any docbook documentation (there is none) and runs the test cases (there are none, I think). -- DigitalPebble Ltd http://www.digitalpebble.com
[jira] Resolved: (UIMA-1462) SimpleUimaAsService has checked in SimpleServer libraries as binaries
[ https://issues.apache.org/jira/browse/UIMA-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved UIMA-1462. --- Resolution: Fixed Fix Version/s: 2.3S Assignee: Tommaso Teofili patches applied SimpleUimaAsService has checked in SimpleServer libraries as binaries - Key: UIMA-1462 URL: https://issues.apache.org/jira/browse/UIMA-1462 Project: UIMA Issue Type: Bug Components: Sandbox-SimpleUimaAsService Affects Versions: 2.2.2S, 2.3S Reporter: Thilo Goetz Assignee: Tommaso Teofili Fix For: 2.3S Attachments: patch1462.txt, patch1462b1.txt, patch1462b2.txt, patch1462c1.txt, patch1462c2.txt, simpleServerDistributionPatch.txt, simpleUimaAsServicePatch.txt For the upcoming release, this should be changed so it depends on the SimpleServer project directly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Compiling project in sandbox (was: Can we update the version of Tika in the TikaAnnotator to 0.4)
Julien Nioche wrote: Hi, I was having the same problem as Jorn using the default version of Maven from Ubuntu. I have upgraded it to 2.2.1 and can now build UIMA but still cannot build the TikaAnnotator. When doing svn install in the TikaAnnotator directory I am getting : *Reason: Cannot find parent: org.apache.uima:SandboxDistr for project: org.apache.uima:TikaAnnotator:jar:2.3.0-incubating-SNAPSHOT for project org.apache.uima:TikaAnnotator:jar:2.3.0-incubating-SNAPSHOT* I then tried to build SandboxDistr but am getting : *antrun:run {execution: CopyLicenseNoticeDisclaimer}] [INFO] Executing tasks [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An Ant BuildException has occured: /usr/local/bin/uimaj-distr/src/main/readme not found.* whereas my uimaj-distr is actually located in a different directory (* /usr/local/bin/uima-svn/uimaj-distr* with the sandbox in*/usr/local/bin/uima-sandbox-svn *). Is there an implicit requirement for the sandbox to be located within the main UIMA directory? Short answer: yes. For the long answer, see Marshall's note. Once the sandbox is put inside the main uima dir everything compiles OK. Thanks Julien Won't have time to look into this in the short term but can try at some point next week. Maybe someone with more experience of Maven can give it a try first and see if it compiles OK? I tried this and it compiled OK. I had success with the following (requires maven to be installed): cd to directory TikaAnnotator mvn install That builds it, builds any docbook documentation (there is none) and runs the test cases (there are none, I think).
Re: svn commit: r810863 - in /incubator/uima/sandbox/trunk: SimpleServer/ SimpleServer/src/main/assembly/ SimpleUimaAsService/ SimpleUimaAsService/src/main/java/org/apache/uima/simpleserver/as/
Marhsall, I am afraid, you are right, some lines have not been merged properly. Do you know how can I fix it without changing revision? Tommaso 2009/9/3 Marshall Schor m...@schor.com Tommaso, I see some issues with this commit. Looking at the SimpleServer/pom.xml changes, it looks like your changes undid the previous-to-yours changes, done in revision 807268. Did you do that on purpose? -Marshall tomm...@apache.org wrote: Author: tommaso Date: Thu Sep 3 10:16:17 2009 New Revision: 810863 URL: http://svn.apache.org/viewvc?rev=810863view=rev Log: [UIMA-1462] SimpleUimaAsService has checked in SimpleServer libraries as binaries Added: incubator/uima/sandbox/trunk/SimpleServer/src/main/assembly/ incubator/uima/sandbox/trunk/SimpleServer/src/main/assembly/distribution.xml Modified: incubator/uima/sandbox/trunk/SimpleServer/pom.xml incubator/uima/sandbox/trunk/SimpleUimaAsService/pom.xml incubator/uima/sandbox/trunk/SimpleUimaAsService/src/main/java/org/apache/uima/simpleserver/as/UimaAsSerive.java Modified: incubator/uima/sandbox/trunk/SimpleServer/pom.xml URL: http://svn.apache.org/viewvc/incubator/uima/sandbox/trunk/SimpleServer/pom.xml?rev=810863r1=810862r2=810863view=diff == --- incubator/uima/sandbox/trunk/SimpleServer/pom.xml (original) +++ incubator/uima/sandbox/trunk/SimpleServer/pom.xml Thu Sep 3 10:16:17 2009 @@ -1,103 +1,244 @@ -!-- - Licensed to the Apache Software Foundation (ASF) under one - or more contributor license agreements. See the NOTICE file - distributed with this work for additional information - regarding copyright ownership. The ASF licenses this file - to you under the Apache License, Version 2.0 (the - License); you may not use this file except in compliance - with the License. You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, - software distributed under the License is distributed on an - AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY - KIND, either express or implied. See the License for the - specific language governing permissions and limitations - under the License. --- -project xmlns=http://maven.apache.org/POM/4.0.0; - xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; + !-- + Licensed to the Apache Software Foundation (ASF) under one or more + contributor license agreements. See the NOTICE file distributed with + this work for additional information regarding copyright ownership. + The ASF licenses this file to you under the Apache License, Version + 2.0 (the License); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 Unless required by + applicable law or agreed to in writing, software distributed under the + License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR + CONDITIONS OF ANY KIND, either express or implied. See the License for + the specific language governing permissions and limitations under the + License. + -- + +project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdorg.apache.uima/groupId artifactIdSimpleServer/artifactId packagingjar/packaging - version2.3.0-incubating-SNAPSHOT/version !-- this comment is a flag for changeVersion -- + version2.3.0-incubating-SNAPSHOT/version nameApache UIMA Simple Server/name - - parent -groupIdorg.apache.uima/groupId -artifactIdSandboxDistr/artifactId -version2.3.0-incubating-SNAPSHOT/version !-- this comment is a flag for changeVersion -- -relativePath../SandboxDistr/relativePath - /parent - - dependencies -!-- versions from parent -- -dependency - groupIdorg.apache.uima/groupId - artifactIduimaj-core/artifactId -/dependency -dependency - groupIdorg.apache.uima/groupId - artifactIduimaj-test-util/artifactId -/dependency -dependency - groupIdorg.apache.uima/groupId - artifactIduimaj-component-test-util/artifactId -/dependency - -dependency - groupIdjavax.servlet/groupId - artifactIdservlet-api/artifactId - version2.4/version -/dependency -dependency - groupIdorg.apache.uima.xmlbeans/groupId - artifactIdxbean/artifactId - version1.0/version -
[jira] Created: (UIMA-1547) XML problems with simple server test cases
XML problems with simple server test cases -- Key: UIMA-1547 URL: https://issues.apache.org/jira/browse/UIMA-1547 Project: UIMA Issue Type: Bug Components: Sandbox-SimpleServer Reporter: Thilo Goetz Assignee: Thilo Goetz Fix For: 2.3S Simple server test cases fail in various JVMs due to various issues with XML generation in those JVMs. This would not be problem if we had some sort of semantic XML comparison capability (anybody know if there is such a thing out there?). Since we compare the files literally, little things like whitespace and standalone=no declarations matter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r810863 - in /incubator/uima/sandbox/trunk: SimpleServer/ SimpleServer/src/main/assembly/ SimpleUimaAsService/ SimpleUimaAsService/src/main/java/org/apache/uima/simpleserver/as/
Tommaso Teofili wrote: Marhsall, I am afraid, you are right, some lines have not been merged properly. Do you know how can I fix it without changing revision? I don't think you can (not sure though). There's no problem with creating another revision. Just fix the problem, and commit with the same jira issue in the comment. The transactional scope is the Jira issue, so to speak. --Thilo Tommaso 2009/9/3 Marshall Schor m...@schor.com Tommaso, I see some issues with this commit. Looking at the SimpleServer/pom.xml changes, it looks like your changes undid the previous-to-yours changes, done in revision 807268. Did you do that on purpose? -Marshall tomm...@apache.org wrote: Author: tommaso Date: Thu Sep 3 10:16:17 2009 New Revision: 810863 URL: http://svn.apache.org/viewvc?rev=810863view=rev Log: [UIMA-1462] SimpleUimaAsService has checked in SimpleServer libraries as binaries Added: incubator/uima/sandbox/trunk/SimpleServer/src/main/assembly/ incubator/uima/sandbox/trunk/SimpleServer/src/main/assembly/distribution.xml Modified: incubator/uima/sandbox/trunk/SimpleServer/pom.xml incubator/uima/sandbox/trunk/SimpleUimaAsService/pom.xml incubator/uima/sandbox/trunk/SimpleUimaAsService/src/main/java/org/apache/uima/simpleserver/as/UimaAsSerive.java Modified: incubator/uima/sandbox/trunk/SimpleServer/pom.xml URL: http://svn.apache.org/viewvc/incubator/uima/sandbox/trunk/SimpleServer/pom.xml?rev=810863r1=810862r2=810863view=diff == --- incubator/uima/sandbox/trunk/SimpleServer/pom.xml (original) +++ incubator/uima/sandbox/trunk/SimpleServer/pom.xml Thu Sep 3 10:16:17 2009 @@ -1,103 +1,244 @@ -!-- - Licensed to the Apache Software Foundation (ASF) under one - or more contributor license agreements. See the NOTICE file - distributed with this work for additional information - regarding copyright ownership. The ASF licenses this file - to you under the Apache License, Version 2.0 (the - License); you may not use this file except in compliance - with the License. You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, - software distributed under the License is distributed on an - AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY - KIND, either express or implied. See the License for the - specific language governing permissions and limitations - under the License. --- -project xmlns=http://maven.apache.org/POM/4.0.0; - xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; + !-- + Licensed to the Apache Software Foundation (ASF) under one or more + contributor license agreements. See the NOTICE file distributed with + this work for additional information regarding copyright ownership. + The ASF licenses this file to you under the Apache License, Version + 2.0 (the License); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 Unless required by + applicable law or agreed to in writing, software distributed under the + License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR + CONDITIONS OF ANY KIND, either express or implied. See the License for + the specific language governing permissions and limitations under the + License. + -- + +project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdorg.apache.uima/groupId artifactIdSimpleServer/artifactId packagingjar/packaging - version2.3.0-incubating-SNAPSHOT/version !-- this comment is a flag for changeVersion -- + version2.3.0-incubating-SNAPSHOT/version nameApache UIMA Simple Server/name - - parent -groupIdorg.apache.uima/groupId -artifactIdSandboxDistr/artifactId -version2.3.0-incubating-SNAPSHOT/version !-- this comment is a flag for changeVersion -- -relativePath../SandboxDistr/relativePath - /parent - - dependencies -!-- versions from parent -- -dependency - groupIdorg.apache.uima/groupId - artifactIduimaj-core/artifactId -/dependency -dependency - groupIdorg.apache.uima/groupId - artifactIduimaj-test-util/artifactId -/dependency -dependency - groupIdorg.apache.uima/groupId - artifactIduimaj-component-test-util/artifactId -/dependency - -dependency - groupIdjavax.servlet/groupId - artifactIdservlet-api/artifactId -
[jira] Closed: (UIMA-767) Use eclipse content types to identify annotators descriptors (.ann) and consumer descriptors (.con)
[ https://issues.apache.org/jira/browse/UIMA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann closed UIMA-767. -- Resolution: Fixed Use eclipse content types to identify annotators descriptors (.ann) and consumer descriptors (.con) --- Key: UIMA-767 URL: https://issues.apache.org/jira/browse/UIMA-767 Project: UIMA Issue Type: Improvement Components: CasEditor Reporter: Jörn Kottmann Assignee: Jörn Kottmann Priority: Minor Fix For: 2.3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r810863 - in /incubator/uima/sandbox/trunk: SimpleServer/ SimpleServer/src/main/assembly/ SimpleUimaAsService/ SimpleUimaAsService/src/main/java/org/apache/uima/simpleserver/as/
Thilo Goetz wrote: Tommaso Teofili wrote: Marhsall, I am afraid, you are right, some lines have not been merged properly. Do you know how can I fix it without changing revision? I don't think you can (not sure though). There's no problem with creating another revision. Just fix the problem, and commit with the same jira issue in the comment. The transactional scope is the Jira issue, so to speak. +1. The purpose of SVN is to track all the changes... so it doesn't let you make something disappear. Maybe the best approach is to revert this last change (as an SVN update) and then do your change as another update - that way it will be clearer exactly what you're changing with your update. -Marshall --Thilo Tommaso 2009/9/3 Marshall Schor m...@schor.com Tommaso, I see some issues with this commit. Looking at the SimpleServer/pom.xml changes, it looks like your changes undid the previous-to-yours changes, done in revision 807268. Did you do that on purpose? -Marshall tomm...@apache.org wrote: Author: tommaso Date: Thu Sep 3 10:16:17 2009 New Revision: 810863 URL: http://svn.apache.org/viewvc?rev=810863view=rev Log: [UIMA-1462] SimpleUimaAsService has checked in SimpleServer libraries as binaries Added: incubator/uima/sandbox/trunk/SimpleServer/src/main/assembly/ incubator/uima/sandbox/trunk/SimpleServer/src/main/assembly/distribution.xml Modified: incubator/uima/sandbox/trunk/SimpleServer/pom.xml incubator/uima/sandbox/trunk/SimpleUimaAsService/pom.xml incubator/uima/sandbox/trunk/SimpleUimaAsService/src/main/java/org/apache/uima/simpleserver/as/UimaAsSerive.java Modified: incubator/uima/sandbox/trunk/SimpleServer/pom.xml URL: http://svn.apache.org/viewvc/incubator/uima/sandbox/trunk/SimpleServer/pom.xml?rev=810863r1=810862r2=810863view=diff == --- incubator/uima/sandbox/trunk/SimpleServer/pom.xml (original) +++ incubator/uima/sandbox/trunk/SimpleServer/pom.xml Thu Sep 3 10:16:17 2009 @@ -1,103 +1,244 @@ -!-- - Licensed to the Apache Software Foundation (ASF) under one - or more contributor license agreements. See the NOTICE file - distributed with this work for additional information - regarding copyright ownership. The ASF licenses this file - to you under the Apache License, Version 2.0 (the - License); you may not use this file except in compliance - with the License. You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, - software distributed under the License is distributed on an - AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY - KIND, either express or implied. See the License for the - specific language governing permissions and limitations - under the License. --- -project xmlns=http://maven.apache.org/POM/4.0.0; - xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; + !-- + Licensed to the Apache Software Foundation (ASF) under one or more + contributor license agreements. See the NOTICE file distributed with + this work for additional information regarding copyright ownership. + The ASF licenses this file to you under the Apache License, Version + 2.0 (the License); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 Unless required by + applicable law or agreed to in writing, software distributed under the + License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR + CONDITIONS OF ANY KIND, either express or implied. See the License for + the specific language governing permissions and limitations under the + License. + -- + +project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdorg.apache.uima/groupId artifactIdSimpleServer/artifactId packagingjar/packaging - version2.3.0-incubating-SNAPSHOT/version !-- this comment is a flag for changeVersion -- + version2.3.0-incubating-SNAPSHOT/version nameApache UIMA Simple Server/name - - parent -groupIdorg.apache.uima/groupId -
Re: Compiling project in sandbox (was: Can we update the version of Tika in the TikaAnnotator to 0.4)
Marshall Schor wrote: [...] Here's the story. For this release, we are planning to release uima (base), uima-as, sandbox, and uima-cpp together as one release. The parent POMs were re-arranged so that the uimaj pom is now the parent of the sandboxDistr pom. Parent POMs are found via 2 mechanims. One is looking them up using the information in the relative-path element of the POM - and as you have seen, that requires that the sandbox be located within the main uima directory. (This perhaps unusual requirement comes from working with Eclipse, which does not support hierarchical directories for projects). That's only true if you want to extract both the core and the sandbox from within eclipse into a single workspace. The only reason this doesn't give you svn troubles is because the eclipse svn client checks out every project individually. I like to check out things on the command line. Then you can import the projects into eclipse, all of them into the same workspace, if you want. When you want to do an update, you just need to say svn up on the command line, and do a refresh in eclipse. I also usually have the sandbox and core in two separate workspaces so I don't have so many projects in one workspace (yes I know what working sets are). However, for this approach to work you need to copy some resources from the core to the sandbox: uimaj and the docbook stuff. So if you update those from svn, you must not forget to copy them again. In linux, you could probably just create a link. On windows, we don't have that luxury. But there is another way too - maven (if it doesn't find the POM using the relative-path link) looks up the POM using the maven coordinates in the various maven repositories, starting with your local .m2 repository. So, all you have to do is build the uimaj POM and install it to your local repository. (Note that after things are released, any user would automatically get the parent POM downloaded from the release repositories, assuming they had maven set up to find these repositories). Doesn't work for me. I do mvn install in the core, and I still have to manually copy over the uimaj project (or maybe just the pom, I never tried that) to build the sandbox. Is there another incantation I need to utter for this to work? There is a trick to building the uimaj POM - if you just say mvn install in the directory of the uimaj project, it will build, but it will also build all of the base UIMA. If all you want to do is just install the POM, without building all of UIMA, you can do that using the -N parameter: type mvn -N install. The -N parameter stops maven from processing the submodules. HTH. -Marshall
[jira] Closed: (UIMA-1547) XML problems with simple server test cases
[ https://issues.apache.org/jira/browse/UIMA-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilo Goetz closed UIMA-1547. - Resolution: Fixed Fixed for most jvms. Test cases still fail with at least one Sun Java 1.5 on windows. If that's a problem, we need to get more sophisticated when comparing xml files. XML problems with simple server test cases -- Key: UIMA-1547 URL: https://issues.apache.org/jira/browse/UIMA-1547 Project: UIMA Issue Type: Bug Components: Sandbox-SimpleServer Reporter: Thilo Goetz Assignee: Thilo Goetz Fix For: 2.3S Simple server test cases fail in various JVMs due to various issues with XML generation in those JVMs. This would not be problem if we had some sort of semantic XML comparison capability (anybody know if there is such a thing out there?). Since we compare the files literally, little things like whitespace and standalone=no declarations matter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Build error after updating to latest uimaj/pom.xml (rev. 807808)
Marshall Schor wrote: Tommaso Teofili wrote: yes, there are many changes from 2.0.9, you could try with newest 2.2.1. I have no problem with both 2.1.0 and 2.2.1 on MacOS X 10.5, but get the same error Jorn gets with maven 2.0.9. Tommaso Thanks Tommaso, for the investigation ! I'm on 2.2, and saw a bunch of messages that 2.1 is not a good level (unless I'm confusing this with something else) - so I encourage everyone to migrate to 2.2.x. Sure I can update to 2.2.x, but I do not appreciate the change because OS X 10.5 and Ubuntu 9.10 both are shipped with maven 2.0.9. For me that sounds like many users will run into this issue. What do we get anything that is worth depending on 2.2.x ? Jörn
Re: Compiling project in sandbox (was: Can we update the version of Tika in the TikaAnnotator to 0.4)
Thilo Goetz wrote: Marshall Schor wrote: [...] Here's the story. For this release, we are planning to release uima (base), uima-as, sandbox, and uima-cpp together as one release. The parent POMs were re-arranged so that the uimaj pom is now the parent of the sandboxDistr pom. Parent POMs are found via 2 mechanims. One is looking them up using the information in the relative-path element of the POM - and as you have seen, that requires that the sandbox be located within the main uima directory. (This perhaps unusual requirement comes from working with Eclipse, which does not support hierarchical directories for projects). That's only true if you want to extract both the core and the sandbox from within eclipse into a single workspace. The only reason this doesn't give you svn troubles is because the eclipse svn client checks out every project individually. I like to check out things on the command line. Then you can import the projects into eclipse, all of them into the same workspace, if you want. When you want to do an update, you just need to say svn up on the command line, and do a refresh in eclipse. I also usually have the sandbox and core in two separate workspaces so I don't have so many projects in one workspace (yes I know what working sets are). However, for this approach to work you need to copy some resources from the core to the sandbox: uimaj and the docbook stuff. So if you update those from svn, you must not forget to copy them again. In linux, you could probably just create a link. On windows, we don't have that luxury. But there is another way too - maven (if it doesn't find the POM using the relative-path link) looks up the POM using the maven coordinates in the various maven repositories, starting with your local .m2 repository. So, all you have to do is build the uimaj POM and install it to your local repository. (Note that after things are released, any user would automatically get the parent POM downloaded from the release repositories, assuming they had maven set up to find these repositories). Doesn't work for me. I do mvn install in the core, and I still have to manually copy over the uimaj project (or maybe just the pom, I never tried that) to build the sandbox. Is there another incantation I need to utter for this to work? Hmmm. Here's my guess: 1) the mvn install does work, but 2) there are *other* dependencies that use relative paths. It would be great if someone tried this and reported exactly what the errors are... then, perhaps we could solve these. I think there are some issues with copying the LIC/NOT/DISC files - because the source is located by relative links. That might be able to be fixed. I am planning to change the source directory for these files shortly (modifying only the uimaj pom) so that if the LIC/NOT/DISC files are found in the dir of the project being built, those are used (useful for sandbox projects which have different LIC/NOT/DISC files to go in their JARs), and only if they are not found there, then the main ones for the UIMA project are used as the source. That may help this one issue (#2) if that's all that's left by way of relative path dependencies. -Marshall There is a trick to building the uimaj POM - if you just say mvn install in the directory of the uimaj project, it will build, but it will also build all of the base UIMA. If all you want to do is just install the POM, without building all of UIMA, you can do that using the -N parameter: type mvn -N install. The -N parameter stops maven from processing the submodules. HTH. -Marshall
Re: Build error after updating to latest uimaj/pom.xml (rev. 807808)
Jörn Kottmann wrote: Marshall Schor wrote: Tommaso Teofili wrote: yes, there are many changes from 2.0.9, you could try with newest 2.2.1. I have no problem with both 2.1.0 and 2.2.1 on MacOS X 10.5, but get the same error Jorn gets with maven 2.0.9. Tommaso Thanks Tommaso, for the investigation ! I'm on 2.2, and saw a bunch of messages that 2.1 is not a good level (unless I'm confusing this with something else) - so I encourage everyone to migrate to 2.2.x. Sure I can update to 2.2.x, but I do not appreciate the change because OS X 10.5 and Ubuntu 9.10 both are shipped with maven 2.0.9. For me that sounds like many users will run into this issue. What do we get anything that is worth depending on 2.2.x ? Good question. I think some dependencies have been creeping in... Before going down the path of trying to find all of these, how hard is it to get/use the 2.2.x maven on these systems? -Marshall Jörn
Re: svn commit: r810863 - in /incubator/uima/sandbox/trunk: SimpleServer/ SimpleServer/src/main/assembly/ SimpleUimaAsService/ SimpleUimaAsService/src/main/java/org/apache/uima/simpleserver/as/
Tommaso - I'm curious to know a bit more how this could have happened. The tools that I use for SVN commits (mainly the SVN plugin for Eclipse) prevent me from committing a change if I haven't done an update to the latest level, and resolved any conflicts. What tooling are you using to do SVN commits? -Marshall Tommaso Teofili wrote: Marhsall, I am afraid, you are right, some lines have not been merged properly. Do you know how can I fix it without changing revision? Tommaso 2009/9/3 Marshall Schor m...@schor.com Tommaso, I see some issues with this commit. Looking at the SimpleServer/pom.xml changes, it looks like your changes undid the previous-to-yours changes, done in revision 807268. Did you do that on purpose? -Marshall tomm...@apache.org wrote: Author: tommaso Date: Thu Sep 3 10:16:17 2009 New Revision: 810863 URL: http://svn.apache.org/viewvc?rev=810863view=rev Log: [UIMA-1462] SimpleUimaAsService has checked in SimpleServer libraries as binaries Added: incubator/uima/sandbox/trunk/SimpleServer/src/main/assembly/ incubator/uima/sandbox/trunk/SimpleServer/src/main/assembly/distribution.xml Modified: incubator/uima/sandbox/trunk/SimpleServer/pom.xml incubator/uima/sandbox/trunk/SimpleUimaAsService/pom.xml incubator/uima/sandbox/trunk/SimpleUimaAsService/src/main/java/org/apache/uima/simpleserver/as/UimaAsSerive.java Modified: incubator/uima/sandbox/trunk/SimpleServer/pom.xml URL: http://svn.apache.org/viewvc/incubator/uima/sandbox/trunk/SimpleServer/pom.xml?rev=810863r1=810862r2=810863view=diff == --- incubator/uima/sandbox/trunk/SimpleServer/pom.xml (original) +++ incubator/uima/sandbox/trunk/SimpleServer/pom.xml Thu Sep 3 10:16:17 2009 @@ -1,103 +1,244 @@ -!-- - Licensed to the Apache Software Foundation (ASF) under one - or more contributor license agreements. See the NOTICE file - distributed with this work for additional information - regarding copyright ownership. The ASF licenses this file - to you under the Apache License, Version 2.0 (the - License); you may not use this file except in compliance - with the License. You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, - software distributed under the License is distributed on an - AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY - KIND, either express or implied. See the License for the - specific language governing permissions and limitations - under the License. --- -project xmlns=http://maven.apache.org/POM/4.0.0; - xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; + !-- + Licensed to the Apache Software Foundation (ASF) under one or more + contributor license agreements. See the NOTICE file distributed with + this work for additional information regarding copyright ownership. + The ASF licenses this file to you under the Apache License, Version + 2.0 (the License); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 Unless required by + applicable law or agreed to in writing, software distributed under the + License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR + CONDITIONS OF ANY KIND, either express or implied. See the License for + the specific language governing permissions and limitations under the + License. + -- + +project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdorg.apache.uima/groupId artifactIdSimpleServer/artifactId packagingjar/packaging - version2.3.0-incubating-SNAPSHOT/version !-- this comment is a flag for changeVersion -- + version2.3.0-incubating-SNAPSHOT/version nameApache UIMA Simple Server/name - - parent -groupIdorg.apache.uima/groupId -artifactIdSandboxDistr/artifactId -version2.3.0-incubating-SNAPSHOT/version !-- this comment is a flag for changeVersion -- -relativePath../SandboxDistr/relativePath - /parent - - dependencies -!-- versions from parent -- -dependency - groupIdorg.apache.uima/groupId - artifactIduimaj-core/artifactId -
Re: CPM test case hang
Thilo, recently I applied a patch attached to JIRA UIMA-1304. I only tested this with JDK1.6. I will look into this today. Jerry On Thu, Sep 3, 2009 at 5:00 AM, Thilo Goetz twgo...@gmx.de wrote: Hi all, has anything changed in the CPM recently? I get a reliable test case hang here (no cpu activity): --- T E S T S --- Running org.apache.uima.collection.impl.cpm.CpmProcessingTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.344 sec Running org.apache.uima.collection.impl.cpm.CasPoolTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.125 sec Running org.apache.uima.collection.impl.cpm.CpmInitTest Initialize was called: true Sep 3, 2009 10:50:48 AM org.apache.uima.collection.impl.cpm.BaseCPMImpl process WARNING: Processing the request to stop the CPM. (Thread Name: main) Sep 3, 2009 10:50:48 AM org.apache.uima.collection.impl.cpm.engine.CPMEngine process INFO: The collection reader thread state is: 2007 (Thread Name: main) I have to kill the process, so I don't have more info than this. It only happens with this jvm (on windows): java version 1.5.0 Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20090707 (SR10 )) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20090707 (JIT enabled) J9VM - 20090706_38445_lHdSMr JIT - 20090623_1334_r8 GC - 200906_09) JCL - 20090705 I tried 3 others, and it goes through with all of them: java version 1.6.0 Java(TM) SE Runtime Environment (build pwi3260sr5-20090529_04(SR5)) IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr5-20090519_35743 (JIT enabled, AOT enabled) J9VM - 20090519_035743_lHdSMr JIT - r9_20090518_2017 GC - 20090417_AA) JCL - 20090529_01 java version 1.5.0_11 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode) java version 1.6.0_13 Java(TM) SE Runtime Environment (build 1.6.0_13-b03) Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode) Let me know if you need more information. --Thilo
Re: Build error after updating to latest uimaj/pom.xml (rev. 807808)
no particular difficulty in my opinion: you only have to download the archive from maven.apache.org and, eventually, change your system path to new Maven location. However, as Jason Van Zyl stated in the last JUG meeting here in Rome, Maven is on its way towards 3.0 release and newer Maven versions begin to get some features of the upcoming release (but personally I don't know which ones). Tommaso 2009/9/3 Marshall Schor m...@schor.com Jörn Kottmann wrote: Marshall Schor wrote: Tommaso Teofili wrote: yes, there are many changes from 2.0.9, you could try with newest 2.2.1. I have no problem with both 2.1.0 and 2.2.1 on MacOS X 10.5, but get the same error Jorn gets with maven 2.0.9. Tommaso Thanks Tommaso, for the investigation ! I'm on 2.2, and saw a bunch of messages that 2.1 is not a good level (unless I'm confusing this with something else) - so I encourage everyone to migrate to 2.2.x. Sure I can update to 2.2.x, but I do not appreciate the change because OS X 10.5 and Ubuntu 9.10 both are shipped with maven 2.0.9. For me that sounds like many users will run into this issue. What do we get anything that is worth depending on 2.2.x ? Good question. I think some dependencies have been creeping in... Before going down the path of trying to find all of these, how hard is it to get/use the 2.2.x maven on these systems? -Marshall Jörn
Re: Compiling project in sandbox (was: Can we update the version of Tika in the TikaAnnotator to 0.4)
Marshall Schor wrote: Thilo Goetz wrote: Marshall Schor wrote: [...] So, all you have to do is build the uimaj POM and install it to your local repository. (Note that after things are released, any user would automatically get the parent POM downloaded from the release repositories, assuming they had maven set up to find these repositories). Doesn't work for me. I do mvn install in the core, and I still have to manually copy over the uimaj project (or maybe just the pom, I never tried that) to build the sandbox. Is there another incantation I need to utter for this to work? Hmmm. Here's my guess: 1) the mvn install does work, but 2) there are *other* dependencies that use relative paths. It would be great if someone tried this and reported exactly what the errors are... then, perhaps we could solve these. You're right, I no longer get the missing parent error. Thanks for fixing that. Now the only error is: [INFO] An Ant BuildException has occurred: C:\build\uimaj-distr\src\main\readme not found. This goes away when I copy uimaj-distr, obviously. --Thilo I think there are some issues with copying the LIC/NOT/DISC files - because the source is located by relative links. That might be able to be fixed. I am planning to change the source directory for these files shortly (modifying only the uimaj pom) so that if the LIC/NOT/DISC files are found in the dir of the project being built, those are used (useful for sandbox projects which have different LIC/NOT/DISC files to go in their JARs), and only if they are not found there, then the main ones for the UIMA project are used as the source. That may help this one issue (#2) if that's all that's left by way of relative path dependencies. -Marshall There is a trick to building the uimaj POM - if you just say mvn install in the directory of the uimaj project, it will build, but it will also build all of the base UIMA. If all you want to do is just install the POM, without building all of UIMA, you can do that using the -N parameter: type mvn -N install. The -N parameter stops maven from processing the submodules. HTH. -Marshall
[jira] Created: (UIMA-1548) Include LICENSE/NOTICE/DISCLAIMER files from local sources ahead of common sources
Include LICENSE/NOTICE/DISCLAIMER files from local sources ahead of common sources -- Key: UIMA-1548 URL: https://issues.apache.org/jira/browse/UIMA-1548 Project: UIMA Issue Type: Bug Components: Build, Packaging and Test Reporter: Marshall Schor Assignee: Marshall Schor Fix For: 2.3 Some of our sub-projects, e.g., the ones in the Sandbox, have individual LICENSE/NOTICE/DISCLAIMER files, that may differ from the common ones for the project because the sub-projects have particular other things they're distributing. Change the antrun configuration to use these in preference to the common ones. Also, change this to support alternate names for these - some of our projects use a suffix of .txt, others don't. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Compiling project in sandbox (was: Can we update the version of Tika in the TikaAnnotator to 0.4)
Thilo Goetz wrote: Marshall Schor wrote: Thilo Goetz wrote: Marshall Schor wrote: [...] So, all you have to do is build the uimaj POM and install it to your local repository. (Note that after things are released, any user would automatically get the parent POM downloaded from the release repositories, assuming they had maven set up to find these repositories). Doesn't work for me. I do mvn install in the core, and I still have to manually copy over the uimaj project (or maybe just the pom, I never tried that) to build the sandbox. Is there another incantation I need to utter for this to work? Hmmm. Here's my guess: 1) the mvn install does work, but 2) there are *other* dependencies that use relative paths. It would be great if someone tried this and reported exactly what the errors are... then, perhaps we could solve these. You're right, I no longer get the missing parent error. Thanks for fixing that. Now the only error is: [INFO] An Ant BuildException has occurred: C:\build\uimaj-distr\src\main\readme not found. Maybe my last commit (just done, for uimaj/pom.xml) fixed this, too. It now doesn't try to copy files from there, *if* the files can be found at the top level of the sandbox project :-) -Marshall This goes away when I copy uimaj-distr, obviously. --Thilo I think there are some issues with copying the LIC/NOT/DISC files - because the source is located by relative links. That might be able to be fixed. I am planning to change the source directory for these files shortly (modifying only the uimaj pom) so that if the LIC/NOT/DISC files are found in the dir of the project being built, those are used (useful for sandbox projects which have different LIC/NOT/DISC files to go in their JARs), and only if they are not found there, then the main ones for the UIMA project are used as the source. That may help this one issue (#2) if that's all that's left by way of relative path dependencies. -Marshall There is a trick to building the uimaj POM - if you just say mvn install in the directory of the uimaj project, it will build, but it will also build all of the base UIMA. If all you want to do is just install the POM, without building all of UIMA, you can do that using the -N parameter: type mvn -N install. The -N parameter stops maven from processing the submodules. HTH. -Marshall
[jira] Closed: (UIMA-1548) Include LICENSE/NOTICE/DISCLAIMER files from local sources ahead of common sources
[ https://issues.apache.org/jira/browse/UIMA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1548. Resolution: Fixed Include LICENSE/NOTICE/DISCLAIMER files from local sources ahead of common sources -- Key: UIMA-1548 URL: https://issues.apache.org/jira/browse/UIMA-1548 Project: UIMA Issue Type: Bug Components: Build, Packaging and Test Reporter: Marshall Schor Assignee: Marshall Schor Fix For: 2.3 Some of our sub-projects, e.g., the ones in the Sandbox, have individual LICENSE/NOTICE/DISCLAIMER files, that may differ from the common ones for the project because the sub-projects have particular other things they're distributing. Change the antrun configuration to use these in preference to the common ones. Also, change this to support alternate names for these - some of our projects use a suffix of .txt, others don't. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Closed: (UIMA-1548) Include LICENSE/NOTICE/DISCLAIMER files from local sources ahead of common sources
Marshall Schor (JIRA) wrote: [ https://issues.apache.org/jira/browse/UIMA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1548. Resolution: Fixed Include LICENSE/NOTICE/DISCLAIMER files from local sources ahead of common sources -- Key: UIMA-1548 URL: https://issues.apache.org/jira/browse/UIMA-1548 Project: UIMA Issue Type: Bug Components: Build, Packaging and Test Reporter: Marshall Schor Assignee: Marshall Schor Fix For: 2.3 Some of our sub-projects, e.g., the ones in the Sandbox, have individual LICENSE/NOTICE/DISCLAIMER files, that may differ from the common ones for the project because the sub-projects have particular other things they're distributing. Change the antrun configuration to use these in preference to the common ones. Also, change this to support alternate names for these - some of our projects use a suffix of .txt, others don't. We use no suffix in the core, and that seems to be the preferred Apache way. Should I just change all sandbox LICENSE/NOTICE/DISCLAIMER files not to use an extension? I'm in there anyway. --Thilo
Lucas NOTICE file
The NOTICE file for Lucas currently does not list any external dependencies. However, looking at Lucas after it's been built, it seems to me we'll be shipping the google-collections.jar. Is that correct? We ship everything that ends up in lib, and nothing else? Thanks, Thilo
Re: Lucas NOTICE file
Thilo Goetz wrote: The NOTICE file for Lucas currently does not list any external dependencies. However, looking at Lucas after it's been built, it seems to me we'll be shipping the google-collections.jar. The google collections jars is in most places just use to get an empty iterator, and in two places to build a map. I would be +1 not using it. Jörn
Re: [jira] Closed: (UIMA-1548) Include LICENSE/NOTICE/DISCLAIMER files from local sources ahead of common sources
Thilo Goetz wrote: Marshall Schor (JIRA) wrote: [ https://issues.apache.org/jira/browse/UIMA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1548. Resolution: Fixed Include LICENSE/NOTICE/DISCLAIMER files from local sources ahead of common sources -- Key: UIMA-1548 URL: https://issues.apache.org/jira/browse/UIMA-1548 Project: UIMA Issue Type: Bug Components: Build, Packaging and Test Reporter: Marshall Schor Assignee: Marshall Schor Fix For: 2.3 Some of our sub-projects, e.g., the ones in the Sandbox, have individual LICENSE/NOTICE/DISCLAIMER files, that may differ from the common ones for the project because the sub-projects have particular other things they're distributing. Change the antrun configuration to use these in preference to the common ones. Also, change this to support alternate names for these - some of our projects use a suffix of .txt, others don't. We use no suffix in the core, and that seems to be the preferred Apache way. Should I just change all sandbox LICENSE/NOTICE/DISCLAIMER files not to use an extension? I'm in there anyway. I have a slight preference for the .txt - it makes opening them a bit easier with today's tooling. But I don't really care, one way or another... and now the scripts don't care either :-) -Marshall --Thilo
Re: Lucas NOTICE file
Thilo Goetz wrote: The NOTICE file for Lucas currently does not list any external dependencies. However, looking at Lucas after it's been built, it seems to me we'll be shipping the google-collections.jar. Is that correct? We ship everything that ends up in lib, and nothing else? I think so. There's already a Jira issue for fixing this: http://issues.apache.org/jira/browse/UIMA-1534 Lucas build puts third-party jars into lib dir - need to review Licenses and update Notices for these The Jira notes there are other things besides google collections: including lucene-snowball and lucene-core. -Marshall Thanks, Thilo
Re: Lucas NOTICE file
I don't agree. There are also NotNullPredicates used in the AnnotationTokenStream class, which avoid null checks of iterator values. This is a really nice feature to clean up the code because iterators are heavily used in this class. Rico On Thu, Sep 3, 2009 at 5:13 PM, Marshall Schorm...@schor.com wrote: Thilo Goetz wrote: The NOTICE file for Lucas currently does not list any external dependencies. However, looking at Lucas after it's been built, it seems to me we'll be shipping the google-collections.jar. Is that correct? We ship everything that ends up in lib, and nothing else? I think so. There's already a Jira issue for fixing this: http://issues.apache.org/jira/browse/UIMA-1534 Lucas build puts third-party jars into lib dir - need to review Licenses and update Notices for these The Jira notes there are other things besides google collections: including lucene-snowball and lucene-core. -Marshall Thanks, Thilo
Re: Lucas NOTICE file
Jörn Kottmann wrote: Thilo Goetz wrote: The NOTICE file for Lucas currently does not list any external dependencies. However, looking at Lucas after it's been built, it seems to me we'll be shipping the google-collections.jar. The google collections jars is in most places just use to get an empty iterator, and in two places to build a map. I would be +1 not using it. +1, seems silly to ship another jar just for this, and besides, the version being shipped is 0.9 ...not yet at 1.x level. -Marshall Jörn
Re: Compiling project in sandbox (was: Can we update the version of Tika in the TikaAnnotator to 0.4)
Thanks for the explanations. I've simply copied the sandbox to the main UIMA directory and it is working fine. I've updated from SVN and when trying to build SandboxDistr from my initial directory (i.e outside the UIMA one) I am now getting : */usr/local/bin/uima-sandbox-svn/SandboxDocs/sandbox_build.xml:35: Cannot find /usr/local/bin/uima-sandbox-svn/PearPackagingAntTask/../uima-docbook-tool/build/build-docbook.xml imported from /usr/local/bin/uima-sandbox-svn/SandboxDocs/sandbox_build.xml* but at least it is not complaining about the readme not being found anymore. If we really have to have the sandbox inside the UIMA dir, maybe we could add a few lines on the website in the Sandbox section about it? Thanks J. 2009/9/3 Marshall Schor m...@schor.com Thilo Goetz wrote: Marshall Schor wrote: Thilo Goetz wrote: Marshall Schor wrote: [...] So, all you have to do is build the uimaj POM and install it to your local repository. (Note that after things are released, any user would automatically get the parent POM downloaded from the release repositories, assuming they had maven set up to find these repositories). Doesn't work for me. I do mvn install in the core, and I still have to manually copy over the uimaj project (or maybe just the pom, I never tried that) to build the sandbox. Is there another incantation I need to utter for this to work? Hmmm. Here's my guess: 1) the mvn install does work, but 2) there are *other* dependencies that use relative paths. It would be great if someone tried this and reported exactly what the errors are... then, perhaps we could solve these. You're right, I no longer get the missing parent error. Thanks for fixing that. Now the only error is: [INFO] An Ant BuildException has occurred: C:\build\uimaj-distr\src\main\readme not found. Maybe my last commit (just done, for uimaj/pom.xml) fixed this, too. It now doesn't try to copy files from there, *if* the files can be found at the top level of the sandbox project :-) -Marshall This goes away when I copy uimaj-distr, obviously. --Thilo I think there are some issues with copying the LIC/NOT/DISC files - because the source is located by relative links. That might be able to be fixed. I am planning to change the source directory for these files shortly (modifying only the uimaj pom) so that if the LIC/NOT/DISC files are found in the dir of the project being built, those are used (useful for sandbox projects which have different LIC/NOT/DISC files to go in their JARs), and only if they are not found there, then the main ones for the UIMA project are used as the source. That may help this one issue (#2) if that's all that's left by way of relative path dependencies. -Marshall There is a trick to building the uimaj POM - if you just say mvn install in the directory of the uimaj project, it will build, but it will also build all of the base UIMA. If all you want to do is just install the POM, without building all of UIMA, you can do that using the -N parameter: type mvn -N install. The -N parameter stops maven from processing the submodules. HTH. -Marshall -- DigitalPebble Ltd http://www.digitalpebble.com
Re: Compiling project in sandbox (was: Can we update the version of Tika in the TikaAnnotator to 0.4)
Julien Nioche wrote: Thanks for the explanations. I've simply copied the sandbox to the main UIMA directory and it is working fine. I've updated from SVN and when trying to build SandboxDistr from my initial directory (i.e outside the UIMA one) I am now getting : */usr/local/bin/uima-sandbox-svn/SandboxDocs/sandbox_build.xml:35: Cannot find /usr/local/bin/uima-sandbox-svn/PearPackagingAntTask/../uima-docbook-tool/build/build-docbook.xml imported from /usr/local/bin/uima-sandbox-svn/SandboxDocs/sandbox_build.xml* Ahh - yes, another dependency on file layout - the documentation build subpart needs the tooling project from the main uima project. I'm not sure how to fix this... any ideas? but at least it is not complaining about the readme not being found anymore. If we really have to have the sandbox inside the UIMA dir, maybe we could add a few lines on the website in the Sandbox section about it? Great idea! Can you draft something? -Marshall Thanks J. 2009/9/3 Marshall Schor m...@schor.com Thilo Goetz wrote: Marshall Schor wrote: Thilo Goetz wrote: Marshall Schor wrote: [...] So, all you have to do is build the uimaj POM and install it to your local repository. (Note that after things are released, any user would automatically get the parent POM downloaded from the release repositories, assuming they had maven set up to find these repositories). Doesn't work for me. I do mvn install in the core, and I still have to manually copy over the uimaj project (or maybe just the pom, I never tried that) to build the sandbox. Is there another incantation I need to utter for this to work? Hmmm. Here's my guess: 1) the mvn install does work, but 2) there are *other* dependencies that use relative paths. It would be great if someone tried this and reported exactly what the errors are... then, perhaps we could solve these. You're right, I no longer get the missing parent error. Thanks for fixing that. Now the only error is: [INFO] An Ant BuildException has occurred: C:\build\uimaj-distr\src\main\readme not found. Maybe my last commit (just done, for uimaj/pom.xml) fixed this, too. It now doesn't try to copy files from there, *if* the files can be found at the top level of the sandbox project :-) -Marshall This goes away when I copy uimaj-distr, obviously. --Thilo I think there are some issues with copying the LIC/NOT/DISC files - because the source is located by relative links. That might be able to be fixed. I am planning to change the source directory for these files shortly (modifying only the uimaj pom) so that if the LIC/NOT/DISC files are found in the dir of the project being built, those are used (useful for sandbox projects which have different LIC/NOT/DISC files to go in their JARs), and only if they are not found there, then the main ones for the UIMA project are used as the source. That may help this one issue (#2) if that's all that's left by way of relative path dependencies. -Marshall There is a trick to building the uimaj POM - if you just say mvn install in the directory of the uimaj project, it will build, but it will also build all of the base UIMA. If all you want to do is just install the POM, without building all of UIMA, you can do that using the -N parameter: type mvn -N install. The -N parameter stops maven from processing the submodules. HTH. -Marshall
Re: Compiling project in sandbox (was: Can we update the version of Tika in the TikaAnnotator to 0.4)
Great idea! Can you draft something? What about adding the section in red below to h*ttp:// incubator.apache.org/uima/sandbox.html* ? You can access the UIMA sandbox in the SVN repository at http://svn.apache.org/repos/asf/incubator/uima/sandbox/trunk/. *Note that in order to compile the projects from the sandbox you will need to check out the repository from within the UIMA main directory as some of the sandbox components use relative paths.* J. -- DigitalPebble Ltd http://www.digitalpebble.com
level of maven-bundle-plugin to use in our builds
We use 1.4.0. Since we last changed that, the Felix project has released 1.4.1 1.4.2 1.4.3 and 2.0.0 Anyone have any experience with these, and is it worth trying to move to a later release? If not, I think I'm leaning to staying at 1.4.0 for now. -Marshall
[jira] Created: (UIMA-1549) uimaj-core has dependency on log4j coded incorrectly
uimaj-core has dependency on log4j coded incorrectly Key: UIMA-1549 URL: https://issues.apache.org/jira/browse/UIMA-1549 Project: UIMA Issue Type: Bug Components: Build, Packaging and Test Reporter: Marshall Schor Priority: Trivial Fix For: 2.3 The dependency is not to be packaged with the result - so the right coding of the scope is provided,not compile. Also, the dependency is optional - it should not be passed by default as a transitive dependency to other maven POMs that depend on the uimaj-core. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1328) deployAsyncService.sh causes Log4j FileNotFoundException
[ https://issues.apache.org/jira/browse/UIMA-1328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12751179#action_12751179 ] Jerry Cwiklik commented on UIMA-1328: - Jorn, there is a bug in our scripts that causes your problem. In UIMA_HOME/config directory there are two config files log4j.properties and activemq-nojournal.xml that should not be there. The reason why is because this directory is added to the classpath by setUimaClasspath.sh script. If you have a component that is dependent on log4j, it will try to initialize it from log4j.properties it finds in the classpath. It finds one loaded from UIMA_HOME/config directory. The problem is, that this file is ActiveMQ specific and leads to an error on this line: log4j.appender.out.file=${activemq.base}/activemq-data/activemq.log {activemq.base} is not initialized and this is why you get the error you describe in the initial comment in this jira. The only reason why the two files are in UIMA_HOME/config is so that we can copy them somewhere else. This copying is done by the UIMA_HOME/bin/startBroker.sh script. The fix for this is to keep the two files in a directory that is not on the classpath. We will fix our build assembly to place the two files in a new directory in the UIMA AS distribution. Thank you for finding this. deployAsyncService.sh causes Log4j FileNotFoundException Key: UIMA-1328 URL: https://issues.apache.org/jira/browse/UIMA-1328 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Environment: Ubuntu 8.10 Reporter: Jörn Kottmann Assignee: Jerry Cwiklik The following exception is printed to the console during startup: bin/deployAsyncService.sh tagger/desc/Deploy_TextAnalysis.xml Setting defaultBrokerURL to: log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /activemq-data/activemq.log (No such file or directory) at java.io.FileOutputStream.openAppend(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:177) at java.io.FileOutputStream.init(FileOutputStream.java:102) at org.apache.log4j.FileAppender.setFile(FileAppender.java:272) at org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:156) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:151) at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:247) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:123) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:87) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:645) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:603) at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:500) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:406) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:432) at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:460) at org.apache.log4j.LogManager.clinit(LogManager.java:113) at org.apache.log4j.Category.getInstance(Category.java:514) at org.apache.commons.logging.impl.Log4JCategoryLog.init(Log4JCategoryLog.java:100) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:502) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:285) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:255) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:381) at org.springframework.util.ClassUtils.clinit(ClassUtils.java:67) at org.springframework.core.io.DefaultResourceLoader.init(DefaultResourceLoader.java:52) at org.springframework.context.support.AbstractApplicationContext.init(AbstractApplicationContext.java:184) at org.springframework.context.support.AbstractRefreshableApplicationContext.init(AbstractRefreshableApplicationContext.java:80) at org.springframework.context.support.AbstractXmlApplicationContext.init(AbstractXmlApplicationContext.java:58) at