Re: [jira] Commented: (UIMA-559) Cas Editor: Add a facility to choose the type of a new annotation in the AnnotationEditor
It compiled for me after I converted the project to a plugin project. So it compiles in Eclipse for me now, but not on the command line. Maven is trying to download Eclipse 3.3 artifacts, but they don't exist in the repository. Does it build for you on the command line? --Thilo Jörn Kottmann wrote: Done. Joern, the CasEditor project doesn't compile for me atm. Do you have instructions on how to set things up so it compiles in Eclipse? I would prefer to make sure that things still compile after I've applied your patches (so I know I haven't screwed up ;-) You need to generate the eclipse files with mvn eclipse:eclipse inside the CasEditor folder. After that it should have no errors, do not forget to refresh the eclipse workspace. I tested this a few minutes ago on my machine, please tell me if you still get errors. The CasEditor needs eclipse 3.3, maybe you are still using eclipse 3.2 Jörn
Re: [jira] Commented: (UIMA-559) Cas Editor: Add a facility to choose the type of a new annotation in the AnnotationEditor
thank u thilo, for spending ur valuable time for me.i have seen that link now i know what not to post,that code is working i have given locations insted of location.i haven same mail ids for both forums thats why i do get confused which one is this. once agin thanku vijay On 9/6/07, Thilo Goetz [EMAIL PROTECTED] wrote: It compiled for me after I converted the project to a plugin project. So it compiles in Eclipse for me now, but not on the command line. Maven is trying to download Eclipse 3.3 artifacts, but they don't exist in the repository. Does it build for you on the command line? --Thilo Jörn Kottmann wrote: Done. Joern, the CasEditor project doesn't compile for me atm. Do you have instructions on how to set things up so it compiles in Eclipse? I would prefer to make sure that things still compile after I've applied your patches (so I know I haven't screwed up ;-) You need to generate the eclipse files with mvn eclipse:eclipse inside the CasEditor folder. After that it should have no errors, do not forget to refresh the eclipse workspace. I tested this a few minutes ago on my machine, please tell me if you still get errors. The CasEditor needs eclipse 3.3, maybe you are still using eclipse 3.2 Jörn
Re: [jira] Commented: (UIMA-559) Cas Editor: Add a facility to choose the type of a new annotation in the AnnotationEditor
Does it build for you on the command line? No, for the same reason. Even if these artifacts can be downloaded it is currently not possible build the Cas Editor as RCP application. There is already a jira issue for this. Jörn
[jira] Updated: (UIMA-565) Cas Editor: Improve startup process
[ https://issues.apache.org/jira/browse/UIMA-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-565: --- Description: Startup should be like its done for ecipse ide application, with workspace locking and prompt for the workspace. Summary: Cas Editor: Improve startup process (was: Cas Editor: Lock workspace instance) This issue should reuse the code from the eclipse ide application. The eclipse code is licensed as epl. This means that it must be included as binary. Tough it must be modified so that it can be used by the Cas Editor. How can we solve this ? Cas Editor: Improve startup process --- Key: UIMA-565 URL: https://issues.apache.org/jira/browse/UIMA-565 Project: UIMA Issue Type: Improvement Components: Sandbox Reporter: Jörn Kottmann Assignee: Jörn Kottmann Startup should be like its done for ecipse ide application, with workspace locking and prompt for the workspace. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-561) Cas Editor: Junit Plugin tests cannot be run
[ https://issues.apache.org/jira/browse/UIMA-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-561: --- Attachment: UIMA-561-2.patch Hi Thilo, can please try to run the unit tests. If it does not work you must maybe add the plugintest folder manually as source folder. All tests should pass. Jörn Cas Editor: Junit Plugin tests cannot be run Key: UIMA-561 URL: https://issues.apache.org/jira/browse/UIMA-561 Project: UIMA Issue Type: Bug Components: Sandbox Reporter: Jörn Kottmann Assignee: Jörn Kottmann Attachments: UIMA-561-2.patch, UIMA-561.patch Its not possible to start the junit plugin tests from eclipse. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-567) Support for application specified logging facility
Support for application specified logging facility -- Key: UIMA-567 URL: https://issues.apache.org/jira/browse/UIMA-567 Project: UIMA Issue Type: New Feature Components: C++ Framework Reporter: Bhavani Iyer .Applications embedding the UIMA C++ runtine need to be able to route log messages generated by the C++ framework and by UIMA C++ componenets to logging facilities used by the application. Currently, the UIMA C++ SDK only supports logging to a file and routing log messages to Java if called from a Java application. To support this requirement to support custom loggers, the SDK will be extended as follows: 1) define a Logger interface to be implemented by users to wrap the application specific logger. 2) provide APIs in the ResourceManager class to register/unregister Loggers. The ResourceManager will maintain reference to all the registered loggers. 3) modify the LogFacility class to route the log messages to all registered loggers. 4) reimplement the current logging to file and java logger to conform to this design. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
