[jira] Commented: (UIMA-1326) Remove EMF dependency from uimaj-ep-runtime plugin
[ https://issues.apache.org/jira/browse/UIMA-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12750287#action_12750287 ] Thilo Goetz commented on UIMA-1326: --- We provide a lot of code where users first have to download something else before they can make it work. I'd vote for not including the ecore jars. Remove EMF dependency from uimaj-ep-runtime plugin -- Key: UIMA-1326 URL: https://issues.apache.org/jira/browse/UIMA-1326 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Affects Versions: 2.3 Reporter: Jörn Kottmann Assignee: Jörn Kottmann Fix For: 2.3 Attachments: uima-as-distr_1326.patch, uimaj-distr_1326.patch, uimaj-examples_1326.patch The uimaj-ep-runtime plugin depends on EMF, this dependency makes deploying in an non eclipse OSGI environment difficult since EMF depends on org.eclipse.core.runtime, which depends on many other eclipse plugins. Since EMF is only really used in the examples project, the dependency is removed from uimaj-core and the classes Ecore2UimaTypeSystem and UimaTypeSystem2Ecore.java are moved to uimaj-examples. The uimaj-ep-runtime plugin contains currently uimaj-examples, that could be moved to a seperate plugin or shipped with an OSGI bundle. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1541) BaseUIMAAsynchronousEngineCommon_impl should be reformated according to uima guideline
BaseUIMAAsynchronousEngineCommon_impl should be reformated according to uima guideline -- Key: UIMA-1541 URL: https://issues.apache.org/jira/browse/UIMA-1541 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Jörn Kottmann Priority: Trivial The mentioned class should be reformated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1412) EntityProcessStatus implementations should implement toString to ease debuging
[ https://issues.apache.org/jira/browse/UIMA-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-1412. --- Resolution: Fixed Overriden UimaASProcessStatusImpl.toString() to show all variables and their values EntityProcessStatus implementations should implement toString to ease debuging -- Key: UIMA-1412 URL: https://issues.apache.org/jira/browse/UIMA-1412 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Priority: Trivial The eclipse debugger calls the toString method of an object to get a string representation which is displayed in the debugger. To ease debugging the EntityProcessStatus implemenations should reveal basic information about the object in an overwritten toString method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: UIMA AS client CPU load
Jorn, I've added a new testcase that is based on what you've described your client does. It was added to the TestUimaASExtended.java in the uimaj-as-activemq project. The name of the testcase: testClientProcess(). I can send 100 CASes to a service with no problem. Can you check the source of the testcase and tell me how it differs from your code. Thanks, Jerry On Wed, Sep 2, 2009 at 4:22 AM, Jörn Kottmann kottm...@gmail.com wrote: Jaroslaw Cwiklik wrote: Jorn, I took Burn's suggestion and removed a busy loop from the getCas(). Instead of waiting between retries I use a semaphore to signal availability of a CAS. Not sure what this hang is all about. Can you refresh all projects from the svn and try again. The refresh removed a bunch of classes and updated the loop from wait to semaphore. The application now fails non deterministic. Here is the piece of the loop in which it fails: CAS cas = uimaAsEngine.getCAS(); cas.setDocumentText(Bytes.toString(result.getRow())); There are two different erros I get, either Exception in thread main org.apache.uima.cas.CASRuntimeException: Data for Sofa feature setLocalSofaData(String) has already been set. at org.apache.uima.cas.impl.SofaFSImpl.setLocalSofaData(SofaFSImpl.java:105) at org.apache.uima.cas.impl.CASImpl.setSofaDataString(CASImpl.java:4102) at org.apache.uima.cas.impl.CASImpl.setDocumentText(CASImpl.java:4087) at Retag.main(Retag.java:89) or Exception in thread main java.lang.NullPointerException at Retag.main(Retag.java:89) The second one appears to occur especially if there is a breakpoint at getCas(). Jörn
Projects are not synchronized after building
Hi, after building uima there are lots of empty src/main/resource/META-INF folders created in different projects. Can these be added to svn:ignore ? After building the docbook there are .db files created, why these are checked in ? Must they be checked in again when they change during the build ? Could we ignore these files, since they are generated ? Jörn
Build error after updating to latest uimaj/pom.xml (rev. 807808)
After updating to the newest uimaj/pom.xml file the build fails, with the following error message: jo...@karkand:~/uima-dev3/uimaj$ mvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache UIMA Java SDK [INFO] Apache UIMA Utility Classes For JUnit Tests [INFO] Apache UIMA Java Framework Core [INFO] Apache UIMA - Java Vinci Transport Library [INFO] Apache UIMA Java Vinci Adapter [INFO] Apache UIMA Java Collection Processing Engine [INFO] Apache UIMA Java Framework - Document Annotation [INFO] Apache UIMA Java SDK Tools [INFO] Apache UIMA Java SDK Examples [INFO] Apache UIMA Java SOAP Adapter [INFO] Apache UIMA Utility Classes For Component JUnit Tests [INFO] Apache UIMA Java SDK common Eclipse plugin settings [INFO] Apache UIMA Debug Eclipse Plugin [INFO] Apache UIMA JCasGen Eclipse Plugin [INFO] Apache UIMA Configurator Eclipse Plugin [INFO] Apache UIMA PEAR Packager Eclipse Plugin [INFO] Apache UIMA Cas Editor Eclipse Plugin [INFO] Apache UIMA Runtime Plugin [INFO] Apache UIMA - PearPackagingMavenPlugin [INFO] Apache UIMA internal Tools [INFO] [INFO] Building Apache UIMA Java SDK [INFO]task-segment: [install] [INFO] [FATAL ERROR] org.codehaus.plexus.component.configurator.BasicComponentConfigurator#configureComponent(...) caused a linkage error (java.lang.NoSuchMethodError) and may be out-of-date. Check the realms: [FATAL ERROR] Plugin realm = app0.child-container[org.apache.maven.plugins:maven-antrun-plugin] urls[0] = file:/home/joern/.m2/repository/org/apache/maven/plugins/maven-antrun-plugin/1.3/maven-antrun-plugin-1.3.jar urls[1] = file:/home/joern/.m2/repository/ant-contrib/ant-contrib/1.0b3/ant-contrib-1.0b3.jar urls[2] = file:/home/joern/.m2/repository/ant/ant/1.5/ant-1.5.jar urls[3] = file:/home/joern/.m2/repository/org/apache/ant/ant/1.7.1/ant-1.7.1.jar urls[4] = file:/home/joern/.m2/repository/org/apache/ant/ant-launcher/1.7.1/ant-launcher-1.7.1.jar urls[5] = file:/home/joern/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar [FATAL ERROR] Container realm = plexus.core urls[0] = file:/usr/share/maven2/lib/wagon-ssh-common.jar urls[1] = file:/usr/share/maven2/lib/jsch.jar urls[2] = file:/usr/share/maven2/lib/wagon-http-shared.jar urls[3] = file:/usr/share/maven2/lib/wagon-ssh.jar urls[4] = file:/usr/share/maven2/lib/wagon-ssh-external.jar urls[5] = file:/usr/share/maven2/lib/xml-apis.jar urls[6] = file:/usr/share/maven2/lib/plexus-utils.jar urls[7] = file:/usr/share/maven2/lib/plexus-container-default.jar urls[8] = file:/usr/share/maven2/lib/wagon-provider-api.jar urls[9] = file:/usr/share/maven2/lib/wagon-http-lightweight.jar urls[10] = file:/usr/share/maven2/lib/jtidy.jar urls[11] = file:/usr/share/maven2/lib/doxia-sink-api.jar urls[12] = file:/usr/share/maven2/lib/wagon-file.jar urls[13] = file:/usr/share/maven2/lib/plexus-interactivity-api.jar urls[14] = file:/usr/share/maven2/lib/maven2.jar urls[15] = file:/usr/share/maven2/lib/commons-cli.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error configuring: org.apache.maven.plugins:maven-antrun-plugin. Reason: java.lang.NoSuchMethodError: org.apache.tools.ant.util.FileUtils.close(Ljava/io/InputStream;)V [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.apache.maven.plugins:maven-antrun-plugin. Reason: java.lang.NoSuchMethodError: org.apache.tools.ant.util.FileUtils.close(Ljava/io/InputStream;)V at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:587) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
Re: Projects are not synchronized after building
Jörn Kottmann wrote: Hi, after building uima there are lots of empty src/main/resource/META-INF folders created in different projects. Can these be added to svn:ignore ? After building the docbook there are .db files created, why these are checked in ? Must they be checked in again when they change during the build ? Could we ignore these files, since they are generated ? Jörn History repeating itself: http://www.mail-archive.com/uima-dev@incubator.apache.org/msg03700.html and surrounding discussion. I think Marshall deleted some generated files, but not all of them. I think the docbook .db files are used for resolving cross-references. They change every time you change sections and such. I don't pretend to understand the docbook build, but imho those files should not be in svn. --Thilo
Re: Build error after updating to latest uimaj/pom.xml (rev. 807808)
Have you tried deleting m2 repository? I did an svn up and build yesterday, and it worked for me. --Thilo Jörn Kottmann wrote: After updating to the newest uimaj/pom.xml file the build fails, with the following error message: jo...@karkand:~/uima-dev3/uimaj$ mvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache UIMA Java SDK [INFO] Apache UIMA Utility Classes For JUnit Tests [INFO] Apache UIMA Java Framework Core [INFO] Apache UIMA - Java Vinci Transport Library [INFO] Apache UIMA Java Vinci Adapter [INFO] Apache UIMA Java Collection Processing Engine [INFO] Apache UIMA Java Framework - Document Annotation [INFO] Apache UIMA Java SDK Tools [INFO] Apache UIMA Java SDK Examples [INFO] Apache UIMA Java SOAP Adapter [INFO] Apache UIMA Utility Classes For Component JUnit Tests [INFO] Apache UIMA Java SDK common Eclipse plugin settings [INFO] Apache UIMA Debug Eclipse Plugin [INFO] Apache UIMA JCasGen Eclipse Plugin [INFO] Apache UIMA Configurator Eclipse Plugin [INFO] Apache UIMA PEAR Packager Eclipse Plugin [INFO] Apache UIMA Cas Editor Eclipse Plugin [INFO] Apache UIMA Runtime Plugin [INFO] Apache UIMA - PearPackagingMavenPlugin [INFO] Apache UIMA internal Tools [INFO] [INFO] Building Apache UIMA Java SDK [INFO]task-segment: [install] [INFO] [FATAL ERROR] org.codehaus.plexus.component.configurator.BasicComponentConfigurator#configureComponent(...) caused a linkage error (java.lang.NoSuchMethodError) and may be out-of-date. Check the realms: [FATAL ERROR] Plugin realm = app0.child-container[org.apache.maven.plugins:maven-antrun-plugin] urls[0] = file:/home/joern/.m2/repository/org/apache/maven/plugins/maven-antrun-plugin/1.3/maven-antrun-plugin-1.3.jar urls[1] = file:/home/joern/.m2/repository/ant-contrib/ant-contrib/1.0b3/ant-contrib-1.0b3.jar urls[2] = file:/home/joern/.m2/repository/ant/ant/1.5/ant-1.5.jar urls[3] = file:/home/joern/.m2/repository/org/apache/ant/ant/1.7.1/ant-1.7.1.jar urls[4] = file:/home/joern/.m2/repository/org/apache/ant/ant-launcher/1.7.1/ant-launcher-1.7.1.jar urls[5] = file:/home/joern/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar [FATAL ERROR] Container realm = plexus.core urls[0] = file:/usr/share/maven2/lib/wagon-ssh-common.jar urls[1] = file:/usr/share/maven2/lib/jsch.jar urls[2] = file:/usr/share/maven2/lib/wagon-http-shared.jar urls[3] = file:/usr/share/maven2/lib/wagon-ssh.jar urls[4] = file:/usr/share/maven2/lib/wagon-ssh-external.jar urls[5] = file:/usr/share/maven2/lib/xml-apis.jar urls[6] = file:/usr/share/maven2/lib/plexus-utils.jar urls[7] = file:/usr/share/maven2/lib/plexus-container-default.jar urls[8] = file:/usr/share/maven2/lib/wagon-provider-api.jar urls[9] = file:/usr/share/maven2/lib/wagon-http-lightweight.jar urls[10] = file:/usr/share/maven2/lib/jtidy.jar urls[11] = file:/usr/share/maven2/lib/doxia-sink-api.jar urls[12] = file:/usr/share/maven2/lib/wagon-file.jar urls[13] = file:/usr/share/maven2/lib/plexus-interactivity-api.jar urls[14] = file:/usr/share/maven2/lib/maven2.jar urls[15] = file:/usr/share/maven2/lib/commons-cli.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error configuring: org.apache.maven.plugins:maven-antrun-plugin. Reason: java.lang.NoSuchMethodError: org.apache.tools.ant.util.FileUtils.close(Ljava/io/InputStream;)V [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.apache.maven.plugins:maven-antrun-plugin. Reason: java.lang.NoSuchMethodError: org.apache.tools.ant.util.FileUtils.close(Ljava/io/InputStream;)V at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:587) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at
[jira] Reopened: (UIMA-1459) Fix UIMA AS bugs reported by Findbugs
[ https://issues.apache.org/jira/browse/UIMA-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik reopened UIMA-1459: - Assignee: Jerry Cwiklik (was: Bhavani Iyer) Synchronize a few methods in JmsEndpointConnection_impl to address Findbugs inconsistent access msgs Fix UIMA AS bugs reported by Findbugs - Key: UIMA-1459 URL: https://issues.apache.org/jira/browse/UIMA-1459 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik Assignee: Jerry Cwiklik Fix For: 2.3AS Attachments: UIMA-1459.patch There are many bugs found by Findbugs in the UIMA As code. Some are minor like a deadstore in a var that is never used. Others are more severe like dereferencing a var that is not checked for NULL. Clean up the code to eliminate reported bugs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1542) dd2spring error messages specifying descriptor Keys should include parents
dd2spring error messages specifying descriptor Keys should include parents -- Key: UIMA-1542 URL: https://issues.apache.org/jira/browse/UIMA-1542 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.3AS Reporter: Marshall Schor Priority: Minor dd2spring puts out error messages and often includes the name of the Key of the associated Analysis Engine within an aggregate. Sometimes, the same Key name is used by several aggregates, and just using the Key name is not sufficient to disambiguate which one it is. Disambiguate by prepending the path of keys to the key, in error messages. Defer past 2.3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1541) UIMA AS source should be reformated according to uima guideline
[ https://issues.apache.org/jira/browse/UIMA-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-1541. --- Resolution: Fixed Reformatted Uima AS source code to conform to UIMA formatting guidelines UIMA AS source should be reformated according to uima guideline --- Key: UIMA-1541 URL: https://issues.apache.org/jira/browse/UIMA-1541 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Jörn Kottmann Priority: Trivial The mentioned class should be reformated. -- 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)
Thilo Goetz wrote: Have you tried deleting m2 repository? I did an svn up and build yesterday, and it worked for me. Yes that I tried on the day the apache servers where down, and then it took a while until i could build my projects again, but it did not help. Does anyone now more about this issue ? Jörn
Re: Build error after updating to latest uimaj/pom.xml (rev. 807808)
Hi Jorn, which Maven version are you using? Cheers, Tommaso 2009/9/2 Jörn Kottmann kottm...@gmail.com Thilo Goetz wrote: Have you tried deleting m2 repository? I did an svn up and build yesterday, and it worked for me. Yes that I tried on the day the apache servers where down, and then it took a while until i could build my projects again, but it did not help. Does anyone now more about this issue ? Jörn
Re: Build error after updating to latest uimaj/pom.xml (rev. 807808)
Tommaso Teofili wrote: Hi Jorn, which Maven version are you using? 2.0.9 on Ubuntu linux Jörn
Re: Build error after updating to latest uimaj/pom.xml (rev. 807808)
Jörn Kottmann wrote: Tommaso Teofili wrote: Hi Jorn, which Maven version are you using? 2.0.9 on Ubuntu linux Jörn I'm using Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100) on windows. I think maven is at 2.2.x now? --Thilo
[jira] Updated: (UIMA-1535) Lucas POM issues
[
https://issues.apache.org/jira/browse/UIMA-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rico Landefeld updated UIMA-1535:
-
Attachment: UIMA-1535.patch
This patch should correct the problems 1-5 noted by Marshall
Lucas POM issues
Key: UIMA-1535
URL: https://issues.apache.org/jira/browse/UIMA-1535
Project: UIMA
Issue Type: Bug
Components: Sandbox-Lucas
Reporter: Marshall Schor
Assignee: Marshall Schor
Priority: Minor
Attachments: UIMA-1535.patch
Some issues to resolve for the Lucas POM
1) it specifies in distributionManagement
urlscp://login.coling.uni-jena.de/var/lib/maven/coling/url
This looks like it might left over from its life elsewhere. I think the
distributionManagement element should be deleted.
2) factor out ant executions for copying standard stuff - done in parent
3) There is a section of the POM specifying actions for the phase site.
We currently do not run a mvn site lifecycle as part of our build process, so
I think this will never execute. Its purpose is to copy to the
${project.build.directory}/site/downloads the downloadable artifacts: the jar
and the pear.
I think we can leave this in as a comment reminding us in the future if we go
to individually downloadable things from our main website, how we might want
to do this.
4) There is an execution in the Ant-run for building the pear directories
that will be bound up with the pear. This adds
* doc/ with a copy of the generated html and pdf from the docbook sources,
Should these be included in the PEAR? They are already included in the
binary distribution of the Sandbox.
* doc/downloads with 2 files: the lucas.xsd, and a sample CasConsumer
descriptor. Do these belong in the PEAR? They are already included in the
src and binary distribution of the Sandbox
* resources dir for the PEAR is populated with the contents of
src/test/resources. This seems a bit unusual - why are the test resources
being included in the PEAR?
5) The PearPackagingMavenPlugin is setting a classpath that includes
* $main_root/lib/cglib-nodep-2.1_3.jar - but this jar is not present. What
is it? can this be deleted?
* $main_root/lib/google-collect-snapshot-20080530.jar
* $main_root/lib/log4j-1.2.14.jar
* $main_root/lib/lucene-core-2.4.0.jar - needs updating to proper level
* $main_root/lib/lucene-snowball-2.4.0.jar
These need updating to proper level, which is no level since the level was
stripped from the /lib
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (UIMA-1531) Need a script to launch a UIMA-AS service via RunWithJarPath
[ https://issues.apache.org/jira/browse/UIMA-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik reopened UIMA-1531: - Assignee: Jerry Cwiklik Add -Duima.datapath=%UIMA_DATAPATH% -Djava.util.logging.config.file=%UIMA_LOGGER_CONFIG_FILE% %UIMA_JVM_OPTS% to the command line that launches the service in deployAsyncService.cmd. Also update runRemoteAsyncAE scripts to use dynamic loaded jars. Need a script to launch a UIMA-AS service via RunWithJarPath Key: UIMA-1531 URL: https://issues.apache.org/jira/browse/UIMA-1531 Project: UIMA Issue Type: New Feature Components: Async Scaleout Reporter: Jerry Cwiklik Assignee: Jerry Cwiklik Fix For: 2.3AS Use existing RunWithJarPath.class from the core to enable loading jars dynamically when launching UIMA AS service. Currently setUimaClasspath is called to setup static classpath before deployment of UIMA_Service. For more flexibility it would be better to load all jar files from specified locations instead of depending on them to be statically defined in setUimaClasspath. One of the reasons for supporting dynamically loaded jars is the naming scheme used by ActiveMQ. Each version comes with a differently named jars like for example apache-activemq-4.1.1.jar, activemq-all-5.2.0.jar, etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Still a uima-as directory in the sandbox
Jörn Kottmann wrote: I also think we should delete the directory, because its moved (with history) to a new location, which can be easily found. The tagged versions remains in the sandbox, in case someone is looking for the old release version. Jörn OK - based on the many opinions voiced, I've removed it. -Marshall
[jira] Updated: (UIMA-924) The UIMA AS service should notify the client via Status Listener if it is about to terminate due to excessive exceptions
[ https://issues.apache.org/jira/browse/UIMA-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-924: Affects Version/s: 2.3AS The UIMA AS service should notify the client via Status Listener if it is about to terminate due to excessive exceptions Key: UIMA-924 URL: https://issues.apache.org/jira/browse/UIMA-924 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jerry Cwiklik Assignee: Jerry Cwiklik Priority: Minor When UIMA AS service is deployed from the AS Client it should use registered status listener callback to notify the client when the service is about to terminate due to excessive exceptions. It should report the last exception which caused the termination along with context which identies the state of processing (GetMeta, CPC or Process). This information may be usefull to the client application. Hold for later release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-629) Default file names produced by XmiWriterCasConsumer don't have .xmi extension and can't be read by XmiCollectionReader
[ https://issues.apache.org/jira/browse/UIMA-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-629. --- Resolution: Fixed Fix Version/s: 2.3 Default file names produced by XmiWriterCasConsumer don't have .xmi extension and can't be read by XmiCollectionReader -- Key: UIMA-629 URL: https://issues.apache.org/jira/browse/UIMA-629 Project: UIMA Issue Type: Bug Components: Examples, Tools Affects Versions: 2.2 Reporter: Adam Lally Priority: Minor Fix For: 2.3 If the original source file name is not present in the CAS, the XmiWriterCasConsumer names the output file doc0,doc1, etc,, with no .xmi extension. The XmiCollectionReader will only read files with .xmi extensions. This is quite annoying if you're trying to break up a pipeline into two parts, writing and reading XMI files in the middle. -- 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)
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 2009/9/2 Thilo Goetz twgo...@gmx.de Jörn Kottmann wrote: Tommaso Teofili wrote: Hi Jorn, which Maven version are you using? 2.0.9 on Ubuntu linux Jörn I'm using Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100) on windows. I think maven is at 2.2.x now? --Thilo
[jira] Created: (UIMA-1543) Missing version tags in uimaj-distr POM
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-1544) make bootstrap launcher take directories which have .class files in them
make bootstrap launcher take directories which have .class files in them Key: UIMA-1544 URL: https://issues.apache.org/jira/browse/UIMA-1544 Project: UIMA Issue Type: Improvement Components: Tools Reporter: Marshall Schor Assignee: Marshall Schor Priority: Minor Fix For: 2.3 Some users don't Jar up their .class files and want to run with these directly. Add a behavior to the bootstrap that accepts these directories (identified by being directories which have no .jar files) and include them directly in the classpath. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1545) UimaBootstrap loader - print out the resulting classpath by default
[ https://issues.apache.org/jira/browse/UIMA-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1545. Resolution: Fixed Fix Version/s: 2.3 UimaBootstrap loader - print out the resulting classpath by default --- Key: UIMA-1545 URL: https://issues.apache.org/jira/browse/UIMA-1545 Project: UIMA Issue Type: Improvement Components: Tools Reporter: Marshall Schor Assignee: Marshall Schor Priority: Minor Fix For: 2.3 Print out the actual classpath set up by the bootstrap, by default. It can be suppressed by adding -DUimaBootstrapSuppressClasspathDisplay This will help future issue resolution by giving users easy way to see exactly what the classpath is they launch with. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1545) UimaBootstrap loader - print out the resulting classpath by default
UimaBootstrap loader - print out the resulting classpath by default --- Key: UIMA-1545 URL: https://issues.apache.org/jira/browse/UIMA-1545 Project: UIMA Issue Type: Improvement Components: Tools Reporter: Marshall Schor Assignee: Marshall Schor Priority: Minor Print out the actual classpath set up by the bootstrap, by default. It can be suppressed by adding -DUimaBootstrapSuppressClasspathDisplay This will help future issue resolution by giving users easy way to see exactly what the classpath is they launch with. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1543) Missing version tags in uimaj-distr POM
[ https://issues.apache.org/jira/browse/UIMA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1543. Resolution: Invalid The version info was moved to the parent (uimaj/pom.xml). The goal was to try to avoid having versions all over the place; this consolidates them into one file for all the things being released in the build. If this is bad practice, please help me understand the pro's and con's of doing it other ways. 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.
Re: Projects are not synchronized after building
Thilo Goetz wrote: Jörn Kottmann wrote: Hi, after building uima there are lots of empty src/main/resource/META-INF folders created in different projects. Can these be added to svn:ignore ? After building the docbook there are .db files created, why these are checked in ? Must they be checked in again when they change during the build ? Could we ignore these files, since they are generated ? Jörn History repeating itself: http://www.mail-archive.com/uima-dev@incubator.apache.org/msg03700.html and surrounding discussion. I think Marshall deleted some generated files, but not all of them. I think the docbook .db files are used for resolving cross-references. They change every time you change sections and such. I don't pretend to understand the docbook build, but imho those files should not be in svn. That is correct - the files are used for resolving cross references. If they are not in svn, then to do the docbook build, the pdf part has to be done twice: once to format things using perhaps incorrect values for cross references, to at least get the page numbers (almost) right, and the 2nd time, to get the cross ref page numbers right. If these are not checked in, it's possible (but perhaps unlikely) that even two passes won't quite do it. Here's the case: the first run - without page number info, lays out the pages of a doc one way, and on pass 2, it slightly alters the page layout because the characters of the page reference take a different amount of space that previously, causing some of the layout to shift pages. When the db files are approximately right, this probability drops to very low... - that's why they're checked in. -Marshall --Thilo
Re: Projects are not synchronized after building
Jörn Kottmann wrote: Hi, after building uima there are lots of empty src/main/resource/META-INF folders created in different projects. Can these be added to svn:ignore ? I hope we don't need to do this. I did some fixups to the main uimaj-pom to not generate these, and to delete them if generated (unless they're kept for the one case of IIRC the camel project). -Marshall After building the docbook there are .db files created, why these are checked in ? Must they be checked in again when they change during the build ? Could we ignore these files, since they are generated ? Jörn
Re: Build error after updating to latest uimaj/pom.xml (rev. 807808)
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. -Marshall 2009/9/2 Thilo Goetz twgo...@gmx.de Jörn Kottmann wrote: Tommaso Teofili wrote: Hi Jorn, which Maven version are you using? 2.0.9 on Ubuntu linux Jörn I'm using Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100) on windows. I think maven is at 2.2.x now? --Thilo
Re: [jira] Updated: (UIMA-1541) UIMA AS source should be reformated according to uima guideline
Jerry Cwiklik (JIRA) wrote: [ https://issues.apache.org/jira/browse/UIMA-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik updated UIMA-1541: Summary: UIMA AS source should be reformated according to uima guideline (was: BaseUIMAAsynchronousEngineCommon_impl should be reformated according to uima guideline) Modified JIRA to extend the scope of the reformatting beyond just BaseUIMAAsynchronousEngineCommon_impl.java as originally requested by Jorn. All UIMA AS source needs to be reformatted using UIMA formatting guidelines as defined in ApacheUima_EclipseCodeStylePrefs.xml Thanks, Jerry! -Marshall UIMA AS source should be reformated according to uima guideline --- Key: UIMA-1541 URL: https://issues.apache.org/jira/browse/UIMA-1541 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Jörn Kottmann Priority: Trivial The mentioned class should be reformated.
