At this point, the build procedure is:
1) run the build.xml in the uimaj-eclipse-update-site project with the
target set to build-features. You can do this in Eclipse by right
clicking the build.xml file and picking Run-As Ant-build ...
2) copy the features built here into the same project's top
[
https://issues.apache.org/jira/browse/UIMA-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727892#action_12727892
]
Marshall Schor commented on UIMA-1422:
--
several fixes made, now update site appears to
Improve/fix build process for Eclipse Plugins
-
Key: UIMA-1422
URL: https://issues.apache.org/jira/browse/UIMA-1422
Project: UIMA
Issue Type: Bug
Components: Eclipse plugins
R
I prefer simplicity, and would like the Cas Editor installed just like
all the other tooling, when you install the tooling. Then it is ready
if and when needed :-).
+1
Jörn
Jörn Kottmann wrote:
> Marshall Schor wrote:
>> After some extra thought - it seems to me that the caseditor might not
>> want to be a separate feature, but instead be included with the tools.
>>
>> So - I won't do another uimaj-eclipse-feature-caseditor project, but
>> rather update the existing
Marshall Schor wrote:
After some extra thought - it seems to me that the caseditor might not
want to be a separate feature, but instead be included with the tools.
So - I won't do another uimaj-eclipse-feature-caseditor project, but
rather update the existing uimaj-eclipse-feature-tools to inclu
Marshall Schor wrote:
Next issue:
There is a new feature for 2.3.0, the caseditor. In the current build
approach, each feature needs a separate "feature" project (Eclipse likes
this organization). There was no uimaj-eclipse-feature-caseditor
project, so I made one :-) and will check it in shor
After some extra thought - it seems to me that the caseditor might not
want to be a separate feature, but instead be included with the tools.
So - I won't do another uimaj-eclipse-feature-caseditor project, but
rather update the existing uimaj-eclipse-feature-tools to include this
plugin.
Let's d
Well, there's more egg on my face :-)
The correction below is wrong - the version should be
2.3.0.incubation-SNAPSHOT
(I forgot the -SNAPSHOT).
With that fix, the update site actually built, and installed partially
successfully into Eclipse 3.5 (which I didn't even know had been
released). Parti
... Typo in the stanzas for feature, they had the attribute
version="2.2.2.incubating" - should be
2.3.0.incubating-SNAPSHOT.
>
> url="features/org.apache.uima.tools_2.3.0.incubating-SNAPSHOT.jar"
> id="org.apache.uima.tools" version="2.2.2.incubating">
>
Next - a workaround to build the feature jars for 2.3 version.
I modified the build.xml to include this, and ran it:
After I ran that target, I re-ran the main target ("all"), and it
reported building the site OK. Now to "test" it...
-Marshall
Next issue:
There is a new feature for 2.3.0, the caseditor. In the current build
approach, each feature needs a separate "feature" project (Eclipse likes
this organization). There was no uimaj-eclipse-feature-caseditor
project, so I made one :-) and will check it in shortly.
Meanwhile, there's
[
https://issues.apache.org/jira/browse/UIMA-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann closed UIMA-1421.
---
Resolution: Fixed
The TypeGroupedContentProvider now uses the bulk remove operation of the viewer.
>
Removing a huge number of annoations is slow
Key: UIMA-1421
URL: https://issues.apache.org/jira/browse/UIMA-1421
Project: UIMA
Issue Type: Bug
Components: CasEditor
Affects Versions:
Agreeing with what Thilo found earlier: It appears that there is a 1/2
done change to the process regarding the feature jars. The result is
the build of the feature jars was taken out of the update site build.xml
script, but no build for this exists elsewhere. Hence, no feature jars
are being bu
Thilo Goetz wrote:
> Marshall Schor wrote:
>
>> Thilo Goetz wrote:
>>
>>> ...
>>> I have tried looking into those issues, but I'm a
>>> little puzzled by our whole eclipse plugin setup.
>>> The plugins are done in a way that looks very odd
>>> to me, but that may just be my lack of experi
Marshall Schor wrote:
>
> Thilo Goetz wrote:
>> ...
>> I have tried looking into those issues, but I'm a
>> little puzzled by our whole eclipse plugin setup.
>> The plugins are done in a way that looks very odd
>> to me, but that may just be my lack of experience.
>> None of the plugins (except
Thilo Goetz wrote:
> ...
> I have tried looking into those issues, but I'm a
> little puzzled by our whole eclipse plugin setup.
> The plugins are done in a way that looks very odd
> to me, but that may just be my lack of experience.
> None of the plugins (except for the cas editor)
> has a prope
Sorry, I started looking at this, but got distracted by the July 4th
holiday ;-) Looking at it again, now... -Marshall
Thilo Goetz wrote:
> Thilo Goetz wrote:
>
>> Thilo Goetz wrote:
>>
>>> All,
>>>
>>> I was trying to follow up on Burn's comments on
>>> https://issues.apache.org/jira/bro
[
https://issues.apache.org/jira/browse/UIMA-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann closed UIMA-1420.
---
Resolution: Fixed
The Annotation Editor now uses the annotation model of the eclipse painter to
push
Annotation Editor updates are too slow when it displays a huge number of
annotations
Key: UIMA-1420
URL: https://issues.apache.org/jira/browse/UIMA-1420
Project: UIM
[
https://issues.apache.org/jira/browse/UIMA-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727485#action_12727485
]
Jörn Kottmann commented on UIMA-1183:
-
This issue is maybe related to UIMA-1408.
> visu
[
https://issues.apache.org/jira/browse/UIMA-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann closed UIMA-1419.
---
Resolution: Fixed
Annotate/Find dialog now has buttons to change the bounds of the created
annotation
Hello
Despite all this, I'm able to run our plugins from
eclipse. Everything seems to be working normally.
I get a small number of plugin-not-found warings at
startup, and continuous JDOM warnings throughout,
but that doesn't seem to affect functionality.
Everytime I try to run the Cas Edito
24 matches
Mail list logo
