You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2015/01/15 00:00:05 UTC
[VOTE] Release UIMA SDK 2.7.0 rc4
Hi everyone,
The next RC of core Java UIMA framework, RC4, is ready for testing.
RC 3 had a multi-threading problem and never got posted... RC 4 fixed that and
improved performance in a couple of areas.
Verses 2.6.0, this version has lots of changes. These are summarized in the
README and RELEASE_NOTES. The list of changes in Jira:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0SDK%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
The source and binary zip/tars and the Eclipse update site are staged to
http://people.apache.org/~schor/uima-release-candidates/uimaj-2.7.0-rc4
The Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapacheuima-1044/
The SVN tags are here:
http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.7.0/
and for the Eclipse Update Site:
http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-eclipse-update-site-2.7.0/
See http://uima.apache.org/testing-builds.html for suggestions on how to test
release candidates.
Please vote on release:
[ ] +1 OK to release
[ ] 0 Don't care
[ ] -1 Not OK to release, because ...
Thanks.
-Marshall
Re: [VOTE]]CANCEL] Release UIMA SDK 2.7.0 rc4
Posted by Marshall Schor <ms...@schor.com>.
Due to some problems found in testing. I'll be rolling back the release shortly.
-Marshall
On 1/14/2015 6:00 PM, Marshall Schor wrote:
> Hi everyone,
> The next RC of core Java UIMA framework, RC4, is ready for testing.
> RC 3 had a multi-threading problem and never got posted... RC 4 fixed that and
> improved performance in a couple of areas.
>
> Verses 2.6.0, this version has lots of changes. These are summarized in the
> README and RELEASE_NOTES. The list of changes in Jira:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0SDK%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
>
> The source and binary zip/tars and the Eclipse update site are staged to
> http://people.apache.org/~schor/uima-release-candidates/uimaj-2.7.0-rc4
>
> The Maven artifacts are here:
> https://repository.apache.org/content/repositories/orgapacheuima-1044/
>
> The SVN tags are here:
> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.7.0/
>
> and for the Eclipse Update Site:
> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-eclipse-update-site-2.7.0/
>
> See http://uima.apache.org/testing-builds.html for suggestions on how to test
> release candidates.
>
> Please vote on release:
>
> [ ] +1 OK to release
> [ ] 0 Don't care
> [ ] -1 Not OK to release, because ...
>
> Thanks.
>
> -Marshall
>
>
>
Re: [VOTE] Release UIMA SDK 2.7.0 rc4
Posted by Marshall Schor <ms...@schor.com>.
uima 2.7.0 rc4 testing
Eclipse install OK - ran CDE on Luna (4.4.1)
signatures OK
compare svn tag with source-release - OK (note that some cpe test checkpoint
artifacts sneaked into the source-release)
build from src after clearing local .m2 uimaj things - OK
Issues fixed: # differ by 4 due to
UIMA-4049 - Resolution is "Done" - no code fixes (OK)
UIMA-4075 - Resolution is "Not a Problem" (OK)
UIMA-4016 - Test type (OK)
UIMA-4090 - Test type (OK)
adjust example paths - ok
run document analyzer - ok
spot check Javadocs and regular docs, including copyright (was updated to 2015) - ok
check of readme, release notes
README has duplicate paragraph
(-Duima.disable_enhanced_check_wrong_add_to_index) - not a blocker
RELEASE_NOTES has a bad links "the Reference chapter" and "CAS Reference
Chapter" - not a blocker I think
check of licenses notices - OK
[X] +1 OK to release
-Marshall
On 1/14/2015 6:00 PM, Marshall Schor wrote:
> Hi everyone,
> The next RC of core Java UIMA framework, RC4, is ready for testing.
> RC 3 had a multi-threading problem and never got posted... RC 4 fixed that and
> improved performance in a couple of areas.
>
> Verses 2.6.0, this version has lots of changes. These are summarized in the
> README and RELEASE_NOTES. The list of changes in Jira:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0SDK%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
>
> The source and binary zip/tars and the Eclipse update site are staged to
> http://people.apache.org/~schor/uima-release-candidates/uimaj-2.7.0-rc4
>
> The Maven artifacts are here:
> https://repository.apache.org/content/repositories/orgapacheuima-1044/
>
> The SVN tags are here:
> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.7.0/
>
> and for the Eclipse Update Site:
> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-eclipse-update-site-2.7.0/
>
> See http://uima.apache.org/testing-builds.html for suggestions on how to test
> release candidates.
>
> Please vote on release:
>
> [ ] +1 OK to release
> [ ] 0 Don't care
> [ ] -1 Not OK to release, because ...
>
> Thanks.
>
> -Marshall
>
>
>
Re: Getting the 2.7.0 plugins to install and work in Eclipse Kepler
Posted by Marshall Schor <ms...@schor.com>.
Great work, Peter!
I've reopened the Jira, and am fixing this, for those projects which specified
the required execution environment.
The ones that didn't specify this (the debug, jcasgen, launcher, and pear
packager) don't have any Java 7 dependencies, so I didn't change those.
-Marshall
On 1/17/2015 12:04 PM, Peter Klügl wrote:
> Hi,
>
> I don't have a good feeling if we do not enforce the java version for the
> plugins since the shipped implementation requires at least that specific
> version. This could lead to nasty errors the user have no clue what caused them.
>
> I started the testing in development mode. All worked fine.
>
> Then, I built the updatesite and installed the plugins in a new Kepler, but I
> uncommented Bundle-RequiredExecutionEnvironment since I think that we really
> should include this. This resulted of course in the problems you reported.
>
> Instead of testing it without Bundle-RequiredExecutionEnvironment , I looked
> for the source of the problem and found that we simply specified a wrong
> version. We need to use
>
> <Bundle-RequiredExecutionEnvironment>JavaSE-1.7</Bundle-RequiredExecutionEnvironment>
>
>
> instead of
>
> <Bundle-RequiredExecutionEnvironment>J2SE-1.7</Bundle-RequiredExecutionEnvironment>
>
>
> I tested the CAS Editor, all seemed to work just fine.
>
> (For those that are interested: I found the problem by using the osgi console
> and manually starting the plugins that have been marked as INSTALLED. It said
> that the execution environment was not fulfilled. After checking the
> installation log for the used java version and all, I searched for the
> supported environments: http://wiki.osgi.org/wiki/Execution_Environment)
>
> There are also some plugins that do not specify
> Bundle-RequiredExecutionEnvironment and do not exlude the
> Import-Package/org.osgi.framework, e.g., uimaj-ep-jcasgen. I think we should
> enforce the java version for all plugins.
>
> Best,
>
> Peter
>
> Am 16.01.2015 um 23:54 schrieb Peter Klügl:
>> I'll take a look (tomorrow).
>>
>> Best,
>>
>> Peter
>>
>> Am 16.01.2015 um 23:50 schrieb Marshall Schor:
>>> I looked up this in the previous Ruta release, and it's the same there.
>>>
>>> I tried installing the 2.7.0 plugins on Kepler, and was able to reproduce this
>>> issue.
>>>
>>> I may have found a fix. But I'd like someone who knows the CAS Editor to check
>>> if it's all working (I was able to run it a bit, so I think it is...).
>>>
>>> The fix has 2 parts.
>>>
>>> 1) Modify the POMs for the 2 Cas Editor Projects (uimaj-ep-cas-editor, and
>>> uimaj-ep-cas-editor-ide) and add this line to the <Import-Package> element at
>>> the end of the other **negated** elements, following the
>>> !org.eclipse.core.runtime,
>>> !org.osgi.framework, <!-- newly added negated element to block this
>>> import -->
>>>
>>> After I did that the plugins would resolve in the update site, but wouldn't run
>>> in Kepler. This is because the plugins had specified
>>> Bundle-RequiredExecutionEnvironment of J2SE-1.7. To get this to work, I
>>> had to
>>> comment out the statement for Bundle-RequiredExecutionEnvironment - I did it in
>>> all the plugins (about 1/2) that had it.
>>>
>>> <!--
>>> Bundle-RequiredExecutionEnvironment>J2SE-1.7</Bundle-RequiredExecutionEnvironment-->
>>>
>>>
>>> Once I did that, and rebuilt all the plugins, and rebuilt the update site, and
>>> started with a brand-new, unzipped version of Kepler, I was able to install OK,
>>> and run OK.
>>>
>>> ************It would be great if someone could confirm this works for
>>> them...*************
>>>
>>> I plan to check this in maybe later this evening...
>>>
>>> -Marshall
>>>
>>> On 1/16/2015 11:01 AM, Peter Klügl wrote:
>>>> - compared source-release and svn-tag - OK
>>>> - del .m2/**/uima, mvn clean install svn-tag - OK
>>>> - del .m2/**/uima, mvn clean install source-release - OK
>>>> - del .m2/**/uima, mvn clean install ruta 2.3.0-SNAPSHOT with staged
>>>> uimaj 2.7.0 - OK
>>>> - installed updatesite in Kepler (4.3sr1) - FAILED
>>>>
>>>> Cannot complete the install because one or more required items could not
>>>> be found.
>>>> Software being installed: UIMA Tools (includes Runtime) 2.7.0
>>>> (org.apache.uima.tools.feature.group 2.7.0)
>>>> Missing requirement: Apache UIMA Eclipse: uimaj-ep-cas-editor 2.7.0
>>>> (org.apache.uima.caseditor 2.7.0) requires 'package org.osgi.framework
>>>> [1.8.0,2.0.0)' but it could not be found
>>>> Cannot satisfy dependency:
>>>> From: UIMA Tools (includes Runtime) 2.7.0
>>>> (org.apache.uima.tools.feature.group 2.7.0)
>>>> To: org.apache.uima.caseditor [2.7.0]
>>>> I think we observed this problem before when a user was not able to
>>>> install the UIMA Ruta Workbench because of the UIMA plugins.
>>>>
>>>> Should we really drop support for Kepler?
>>>>
>>>> Best,
>>>>
>>>> Peter
>>>>
>>>> Am 15.01.2015 um 00:00 schrieb Marshall Schor:
>>>>> Hi everyone,
>>>>> The next RC of core Java UIMA framework, RC4, is ready for testing.
>>>>> RC 3 had a multi-threading problem and never got posted... RC 4 fixed that
>>>>> and
>>>>> improved performance in a couple of areas.
>>>>>
>>>>> Verses 2.6.0, this version has lots of changes. These are summarized in the
>>>>> README and RELEASE_NOTES. The list of changes in Jira:
>>>>>
>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0SDK%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
>>>>>
>>>>>
>>>>> The source and binary zip/tars and the Eclipse update site are staged to
>>>>> http://people.apache.org/~schor/uima-release-candidates/uimaj-2.7.0-rc4
>>>>>
>>>>> The Maven artifacts are here:
>>>>> https://repository.apache.org/content/repositories/orgapacheuima-1044/
>>>>>
>>>>> The SVN tags are here:
>>>>> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.7.0/
>>>>>
>>>>> and for the Eclipse Update Site:
>>>>> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-eclipse-update-site-2.7.0/
>>>>>
>>>>>
>>>>> See http://uima.apache.org/testing-builds.html for suggestions on how to test
>>>>> release candidates.
>>>>>
>>>>> Please vote on release:
>>>>>
>>>>> [ ] +1 OK to release
>>>>> [ ] 0 Don't care
>>>>> [ ] -1 Not OK to release, because ...
>>>>>
>>>>> Thanks.
>>>>>
>>>>> -Marshall
>>>>>
>>>>
>>
>
>
>
Re: Getting the 2.7.0 plugins to install and work in Eclipse Kepler
Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Hi,
I don't have a good feeling if we do not enforce the java version for
the plugins since the shipped implementation requires at least that
specific version. This could lead to nasty errors the user have no clue
what caused them.
I started the testing in development mode. All worked fine.
Then, I built the updatesite and installed the plugins in a new Kepler,
but I uncommented Bundle-RequiredExecutionEnvironment since I think that
we really should include this. This resulted of course in the problems
you reported.
Instead of testing it without Bundle-RequiredExecutionEnvironment , I
looked for the source of the problem and found that we simply specified
a wrong version. We need to use
<Bundle-RequiredExecutionEnvironment>JavaSE-1.7</Bundle-RequiredExecutionEnvironment>
instead of
<Bundle-RequiredExecutionEnvironment>J2SE-1.7</Bundle-RequiredExecutionEnvironment>
I tested the CAS Editor, all seemed to work just fine.
(For those that are interested: I found the problem by using the osgi
console and manually starting the plugins that have been marked as
INSTALLED. It said that the execution environment was not fulfilled.
After checking the installation log for the used java version and all, I
searched for the supported environments:
http://wiki.osgi.org/wiki/Execution_Environment)
There are also some plugins that do not specify
Bundle-RequiredExecutionEnvironment and do not exlude the
Import-Package/org.osgi.framework, e.g., uimaj-ep-jcasgen. I think we
should enforce the java version for all plugins.
Best,
Peter
Am 16.01.2015 um 23:54 schrieb Peter Klügl:
> I'll take a look (tomorrow).
>
> Best,
>
> Peter
>
> Am 16.01.2015 um 23:50 schrieb Marshall Schor:
>> I looked up this in the previous Ruta release, and it's the same there.
>>
>> I tried installing the 2.7.0 plugins on Kepler, and was able to
>> reproduce this
>> issue.
>>
>> I may have found a fix. But I'd like someone who knows the CAS
>> Editor to check
>> if it's all working (I was able to run it a bit, so I think it is...).
>>
>> The fix has 2 parts.
>>
>> 1) Modify the POMs for the 2 Cas Editor Projects
>> (uimaj-ep-cas-editor, and
>> uimaj-ep-cas-editor-ide) and add this line to the <Import-Package>
>> element at
>> the end of the other **negated** elements, following the
>> !org.eclipse.core.runtime,
>> !org.osgi.framework, <!-- newly added negated element to
>> block this
>> import -->
>>
>> After I did that the plugins would resolve in the update site, but
>> wouldn't run
>> in Kepler. This is because the plugins had specified
>> Bundle-RequiredExecutionEnvironment of J2SE-1.7. To get this to
>> work, I had to
>> comment out the statement for Bundle-RequiredExecutionEnvironment - I
>> did it in
>> all the plugins (about 1/2) that had it.
>>
>> <!--
>> Bundle-RequiredExecutionEnvironment>J2SE-1.7</Bundle-RequiredExecutionEnvironment-->
>>
>>
>> Once I did that, and rebuilt all the plugins, and rebuilt the update
>> site, and
>> started with a brand-new, unzipped version of Kepler, I was able to
>> install OK,
>> and run OK.
>>
>> ************It would be great if someone could confirm this works for
>> them...*************
>>
>> I plan to check this in maybe later this evening...
>>
>> -Marshall
>>
>> On 1/16/2015 11:01 AM, Peter Klügl wrote:
>>> - compared source-release and svn-tag - OK
>>> - del .m2/**/uima, mvn clean install svn-tag - OK
>>> - del .m2/**/uima, mvn clean install source-release - OK
>>> - del .m2/**/uima, mvn clean install ruta 2.3.0-SNAPSHOT with staged
>>> uimaj 2.7.0 - OK
>>> - installed updatesite in Kepler (4.3sr1) - FAILED
>>>
>>> Cannot complete the install because one or more required items could
>>> not
>>> be found.
>>> Software being installed: UIMA Tools (includes Runtime) 2.7.0
>>> (org.apache.uima.tools.feature.group 2.7.0)
>>> Missing requirement: Apache UIMA Eclipse: uimaj-ep-cas-editor 2.7.0
>>> (org.apache.uima.caseditor 2.7.0) requires 'package org.osgi.framework
>>> [1.8.0,2.0.0)' but it could not be found
>>> Cannot satisfy dependency:
>>> From: UIMA Tools (includes Runtime) 2.7.0
>>> (org.apache.uima.tools.feature.group 2.7.0)
>>> To: org.apache.uima.caseditor [2.7.0]
>>> I think we observed this problem before when a user was not able to
>>> install the UIMA Ruta Workbench because of the UIMA plugins.
>>>
>>> Should we really drop support for Kepler?
>>>
>>> Best,
>>>
>>> Peter
>>>
>>> Am 15.01.2015 um 00:00 schrieb Marshall Schor:
>>>> Hi everyone,
>>>> The next RC of core Java UIMA framework, RC4, is ready for testing.
>>>> RC 3 had a multi-threading problem and never got posted... RC 4
>>>> fixed that and
>>>> improved performance in a couple of areas.
>>>>
>>>> Verses 2.6.0, this version has lots of changes. These are
>>>> summarized in the
>>>> README and RELEASE_NOTES. The list of changes in Jira:
>>>>
>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0SDK%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
>>>>
>>>>
>>>> The source and binary zip/tars and the Eclipse update site are
>>>> staged to
>>>> http://people.apache.org/~schor/uima-release-candidates/uimaj-2.7.0-rc4
>>>>
>>>>
>>>> The Maven artifacts are here:
>>>> https://repository.apache.org/content/repositories/orgapacheuima-1044/
>>>>
>>>> The SVN tags are here:
>>>> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.7.0/
>>>>
>>>> and for the Eclipse Update Site:
>>>> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-eclipse-update-site-2.7.0/
>>>>
>>>>
>>>> See http://uima.apache.org/testing-builds.html for suggestions on
>>>> how to test
>>>> release candidates.
>>>>
>>>> Please vote on release:
>>>>
>>>> [ ] +1 OK to release
>>>> [ ] 0 Don't care
>>>> [ ] -1 Not OK to release, because ...
>>>>
>>>> Thanks.
>>>>
>>>> -Marshall
>>>>
>>>
>
Re: Getting the 2.7.0 plugins to install and work in Eclipse Kepler
Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
I'll take a look (tomorrow).
Best,
Peter
Am 16.01.2015 um 23:50 schrieb Marshall Schor:
> I looked up this in the previous Ruta release, and it's the same there.
>
> I tried installing the 2.7.0 plugins on Kepler, and was able to reproduce this
> issue.
>
> I may have found a fix. But I'd like someone who knows the CAS Editor to check
> if it's all working (I was able to run it a bit, so I think it is...).
>
> The fix has 2 parts.
>
> 1) Modify the POMs for the 2 Cas Editor Projects (uimaj-ep-cas-editor, and
> uimaj-ep-cas-editor-ide) and add this line to the <Import-Package> element at
> the end of the other **negated** elements, following the
> !org.eclipse.core.runtime,
> !org.osgi.framework, <!-- newly added negated element to block this
> import -->
>
> After I did that the plugins would resolve in the update site, but wouldn't run
> in Kepler. This is because the plugins had specified
> Bundle-RequiredExecutionEnvironment of J2SE-1.7. To get this to work, I had to
> comment out the statement for Bundle-RequiredExecutionEnvironment - I did it in
> all the plugins (about 1/2) that had it.
>
> <!--
> Bundle-RequiredExecutionEnvironment>J2SE-1.7</Bundle-RequiredExecutionEnvironment-->
>
> Once I did that, and rebuilt all the plugins, and rebuilt the update site, and
> started with a brand-new, unzipped version of Kepler, I was able to install OK,
> and run OK.
>
> ************It would be great if someone could confirm this works for
> them...*************
>
> I plan to check this in maybe later this evening...
>
> -Marshall
>
> On 1/16/2015 11:01 AM, Peter Klügl wrote:
>> - compared source-release and svn-tag - OK
>> - del .m2/**/uima, mvn clean install svn-tag - OK
>> - del .m2/**/uima, mvn clean install source-release - OK
>> - del .m2/**/uima, mvn clean install ruta 2.3.0-SNAPSHOT with staged
>> uimaj 2.7.0 - OK
>> - installed updatesite in Kepler (4.3sr1) - FAILED
>>
>> Cannot complete the install because one or more required items could not
>> be found.
>> Software being installed: UIMA Tools (includes Runtime) 2.7.0
>> (org.apache.uima.tools.feature.group 2.7.0)
>> Missing requirement: Apache UIMA Eclipse: uimaj-ep-cas-editor 2.7.0
>> (org.apache.uima.caseditor 2.7.0) requires 'package org.osgi.framework
>> [1.8.0,2.0.0)' but it could not be found
>> Cannot satisfy dependency:
>> From: UIMA Tools (includes Runtime) 2.7.0
>> (org.apache.uima.tools.feature.group 2.7.0)
>> To: org.apache.uima.caseditor [2.7.0]
>>
>> I think we observed this problem before when a user was not able to
>> install the UIMA Ruta Workbench because of the UIMA plugins.
>>
>> Should we really drop support for Kepler?
>>
>> Best,
>>
>> Peter
>>
>> Am 15.01.2015 um 00:00 schrieb Marshall Schor:
>>> Hi everyone,
>>> The next RC of core Java UIMA framework, RC4, is ready for testing.
>>> RC 3 had a multi-threading problem and never got posted... RC 4 fixed that and
>>> improved performance in a couple of areas.
>>>
>>> Verses 2.6.0, this version has lots of changes. These are summarized in the
>>> README and RELEASE_NOTES. The list of changes in Jira:
>>>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0SDK%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
>>>
>>> The source and binary zip/tars and the Eclipse update site are staged to
>>> http://people.apache.org/~schor/uima-release-candidates/uimaj-2.7.0-rc4
>>>
>>> The Maven artifacts are here:
>>> https://repository.apache.org/content/repositories/orgapacheuima-1044/
>>>
>>> The SVN tags are here:
>>> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.7.0/
>>>
>>> and for the Eclipse Update Site:
>>> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-eclipse-update-site-2.7.0/
>>>
>>> See http://uima.apache.org/testing-builds.html for suggestions on how to test
>>> release candidates.
>>>
>>> Please vote on release:
>>>
>>> [ ] +1 OK to release
>>> [ ] 0 Don't care
>>> [ ] -1 Not OK to release, because ...
>>>
>>> Thanks.
>>>
>>> -Marshall
>>>
>>
Getting the 2.7.0 plugins to install and work in Eclipse Kepler
Posted by Marshall Schor <ms...@schor.com>.
I looked up this in the previous Ruta release, and it's the same there.
I tried installing the 2.7.0 plugins on Kepler, and was able to reproduce this
issue.
I may have found a fix. But I'd like someone who knows the CAS Editor to check
if it's all working (I was able to run it a bit, so I think it is...).
The fix has 2 parts.
1) Modify the POMs for the 2 Cas Editor Projects (uimaj-ep-cas-editor, and
uimaj-ep-cas-editor-ide) and add this line to the <Import-Package> element at
the end of the other **negated** elements, following the
!org.eclipse.core.runtime,
!org.osgi.framework, <!-- newly added negated element to block this
import -->
After I did that the plugins would resolve in the update site, but wouldn't run
in Kepler. This is because the plugins had specified
Bundle-RequiredExecutionEnvironment of J2SE-1.7. To get this to work, I had to
comment out the statement for Bundle-RequiredExecutionEnvironment - I did it in
all the plugins (about 1/2) that had it.
<!--
Bundle-RequiredExecutionEnvironment>J2SE-1.7</Bundle-RequiredExecutionEnvironment-->
Once I did that, and rebuilt all the plugins, and rebuilt the update site, and
started with a brand-new, unzipped version of Kepler, I was able to install OK,
and run OK.
************It would be great if someone could confirm this works for
them...*************
I plan to check this in maybe later this evening...
-Marshall
On 1/16/2015 11:01 AM, Peter Klügl wrote:
> - compared source-release and svn-tag - OK
> - del .m2/**/uima, mvn clean install svn-tag - OK
> - del .m2/**/uima, mvn clean install source-release - OK
> - del .m2/**/uima, mvn clean install ruta 2.3.0-SNAPSHOT with staged
> uimaj 2.7.0 - OK
> - installed updatesite in Kepler (4.3sr1) - FAILED
>
> Cannot complete the install because one or more required items could not
> be found.
> Software being installed: UIMA Tools (includes Runtime) 2.7.0
> (org.apache.uima.tools.feature.group 2.7.0)
> Missing requirement: Apache UIMA Eclipse: uimaj-ep-cas-editor 2.7.0
> (org.apache.uima.caseditor 2.7.0) requires 'package org.osgi.framework
> [1.8.0,2.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: UIMA Tools (includes Runtime) 2.7.0
> (org.apache.uima.tools.feature.group 2.7.0)
> To: org.apache.uima.caseditor [2.7.0]
>
> I think we observed this problem before when a user was not able to
> install the UIMA Ruta Workbench because of the UIMA plugins.
>
> Should we really drop support for Kepler?
>
> Best,
>
> Peter
>
> Am 15.01.2015 um 00:00 schrieb Marshall Schor:
>> Hi everyone,
>> The next RC of core Java UIMA framework, RC4, is ready for testing.
>> RC 3 had a multi-threading problem and never got posted... RC 4 fixed that and
>> improved performance in a couple of areas.
>>
>> Verses 2.6.0, this version has lots of changes. These are summarized in the
>> README and RELEASE_NOTES. The list of changes in Jira:
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0SDK%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
>>
>> The source and binary zip/tars and the Eclipse update site are staged to
>> http://people.apache.org/~schor/uima-release-candidates/uimaj-2.7.0-rc4
>>
>> The Maven artifacts are here:
>> https://repository.apache.org/content/repositories/orgapacheuima-1044/
>>
>> The SVN tags are here:
>> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.7.0/
>>
>> and for the Eclipse Update Site:
>> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-eclipse-update-site-2.7.0/
>>
>> See http://uima.apache.org/testing-builds.html for suggestions on how to test
>> release candidates.
>>
>> Please vote on release:
>>
>> [ ] +1 OK to release
>> [ ] 0 Don't care
>> [ ] -1 Not OK to release, because ...
>>
>> Thanks.
>>
>> -Marshall
>>
>
>
Re: [VOTE] Release UIMA SDK 2.7.0 rc4
Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
- compared source-release and svn-tag - OK
- del .m2/**/uima, mvn clean install svn-tag - OK
- del .m2/**/uima, mvn clean install source-release - OK
- del .m2/**/uima, mvn clean install ruta 2.3.0-SNAPSHOT with staged
uimaj 2.7.0 - OK
- installed updatesite in Kepler (4.3sr1) - FAILED
Cannot complete the install because one or more required items could not
be found.
Software being installed: UIMA Tools (includes Runtime) 2.7.0
(org.apache.uima.tools.feature.group 2.7.0)
Missing requirement: Apache UIMA Eclipse: uimaj-ep-cas-editor 2.7.0
(org.apache.uima.caseditor 2.7.0) requires 'package org.osgi.framework
[1.8.0,2.0.0)' but it could not be found
Cannot satisfy dependency:
From: UIMA Tools (includes Runtime) 2.7.0
(org.apache.uima.tools.feature.group 2.7.0)
To: org.apache.uima.caseditor [2.7.0]
I think we observed this problem before when a user was not able to
install the UIMA Ruta Workbench because of the UIMA plugins.
Should we really drop support for Kepler?
Best,
Peter
Am 15.01.2015 um 00:00 schrieb Marshall Schor:
> Hi everyone,
> The next RC of core Java UIMA framework, RC4, is ready for testing.
> RC 3 had a multi-threading problem and never got posted... RC 4 fixed that and
> improved performance in a couple of areas.
>
> Verses 2.6.0, this version has lots of changes. These are summarized in the
> README and RELEASE_NOTES. The list of changes in Jira:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0SDK%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
>
> The source and binary zip/tars and the Eclipse update site are staged to
> http://people.apache.org/~schor/uima-release-candidates/uimaj-2.7.0-rc4
>
> The Maven artifacts are here:
> https://repository.apache.org/content/repositories/orgapacheuima-1044/
>
> The SVN tags are here:
> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.7.0/
>
> and for the Eclipse Update Site:
> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-eclipse-update-site-2.7.0/
>
> See http://uima.apache.org/testing-builds.html for suggestions on how to test
> release candidates.
>
> Please vote on release:
>
> [ ] +1 OK to release
> [ ] 0 Don't care
> [ ] -1 Not OK to release, because ...
>
> Thanks.
>
> -Marshall
>