[
https://issues.apache.org/jira/browse/UIMA-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann updated UIMA-355:
---
Attachment: pde2-patch.txt
Patch for the assemble-plugin.xml file.
It adds the version to the included
There are 2 ways that Eclipse uers may use UIMA Runtime plugin:
1. Use the UIMA plugin jars from the Java project (which is NOT a plugin
project) as external Jars or Library
2. Use the UIMA plugin as "a plugin" from a Plugin project
For the #1, users need to modified their setting everytime a new
Jörn Kottmann wrote:
I strongly dislike jar file names with version numbers in them. Every
time you get a new version you have to update classpath settings in
script files, eclipse run configurations, or whever else jar files are
referred to by name. I just think it's very impractical and would
Michael, I was looking over PearAnalysisEngineWrapper.java and I think
there's something missing.
When you create your CAS you aren't telling it the ClassLoader for the
PEAR. So if JCAS were used and the JCas classes were in the PEAR, I
think you would get class not found exceptions. Have you t
I strongly dislike jar file names with version numbers in them. Every
time you get a new version you have to update classpath settings in
script files, eclipse run configurations, or whever else jar files are
referred to by name. I just think it's very impractical and would be
annoying to our us
On 3/22/07, Michael Baessler <[EMAIL PROTECTED]> wrote:
I don't like the idea to have different names for the same version of
the jar. I think it will be better to have the same name for all jars.
As I understand the uimaj-core-2.2-incubating-SNAPSHOT.jar naming schema
is the default that maven g
Adam Lally wrote:
I want to get the other committers' opinion on this. It has to do
with Joern's proposed patch to the uimaj-ep-runtime plugin so that mvn
eclipse:eclipse will create a PDE project instead of a regular Java
project.
Because of mvn eclipse:eclipse has limited configuration option
[
https://issues.apache.org/jira/browse/UIMA-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Baessler closed UIMA-354.
-
Resolution: Fixed
I updated the PackageBrowser API as well as the UIMA documentation.
> UIMA datap
Write documentation for the Cas Editor
--
Key: UIMA-357
URL: https://issues.apache.org/jira/browse/UIMA-357
Project: UIMA
Issue Type: Task
Components: Sandbox
Reporter: Jörn Kottmann
[
https://issues.apache.org/jira/browse/UIMA-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann updated UIMA-155:
---
Attachment: update.txt
Contains a few bugfixes and makes the code less dependent on org.eclipse.ui.ide.
I want to get the other committers' opinion on this. It has to do
with Joern's proposed patch to the uimaj-ep-runtime plugin so that mvn
eclipse:eclipse will create a PDE project instead of a regular Java
project.
Because of mvn eclipse:eclipse has limited configuration options, it
appears we'd
[
https://issues.apache.org/jira/browse/UIMA-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483151
]
Adam Lally commented on UIMA-355:
-
I see that you'e updated the names of the jar files in the manifest. They used
be
[
https://issues.apache.org/jira/browse/UIMA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Baessler closed UIMA-356.
-
Resolution: Fixed
> fix IBM dependency in CVD log properties file
> ---
[
https://issues.apache.org/jira/browse/UIMA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Baessler updated UIMA-356:
--
Component/s: Tools
> fix IBM dependency in CVD log properties file
>
fix IBM dependency in CVD log properties file
-
Key: UIMA-356
URL: https://issues.apache.org/jira/browse/UIMA-356
Project: UIMA
Issue Type: Bug
Affects Versions: 2.1
Reporter: Micha
15 matches
Mail list logo
