It looks like we're all using somewhat different levels of the tool build chain
for building eclipse plugins.
I think this is not a problem; the problem with uima-as 2.9.0 was traced to a
faulty content.jar upload.
Nevertheless, it's probably best to not tinker too much with this... I had
thought of suggesting everyone upgrade to, say, Neon.2 level (the latest) but
that has a (probably quite small) possibility of creating artifacts that older
versions of Eclipse might have trouble loading - I hope not, but you never know
without testing.
Peter is using one from 2014, I was using 2013, but tried 2016 (Neon.2).
I would suggest to Jerry that he upgrade his plugin versions to some version
from 2013 or 2014. (his is from 2011).
You can see the date in Eclipse version strings, e.g.
/plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
---------------------------------------------XXXX-------------
-M
On 2/6/2017 9:40 AM, Peter Klügl wrote:
> Sorry for the delayed response, missed the mail.
>
>
> <uima-maven-build-eclipse-home>C:/work/eclipse/luna_rcp_uima/eclipse</uima-maven-build-eclipse-home>
>
> <eclipse-equinox-launcher>${uima-maven-build-eclipse-home}/plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar</eclipse-equinox-launcher>
>
> <uima-eclipse-jar-processor>${uima-maven-build-eclipse-home}/plugins/org.eclipse.equinox.p2.jarprocessor_1.0.300.v20131211-1531.jar</uima-eclipse-jar-processor>
>
>
> Am 03.02.2017 um 21:55 schrieb Marshall Schor:
>> I think there's a good chance the reason the Eclipse update site broke with
>> my
>> latest upload of 3.0.0.alpha was due to version changes in building tools.
>>
>> The tool chain version is configured typically in your .m2/settings.xml
>> file, on
>> the lines that might look like the following
>>
>> <properties>
>> <!-- Kepler 4.3.2 level -->
>>
>> <uima-maven-build-eclipse-home>C:/p/eclipse/432kepler</uima-maven-build-eclipse-home>
>>
>> <!-- eclipse432 kepler -->
>>
>> <eclipse-equinox-launcher>${uima-maven-build-eclipse-home}/plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar</eclipse-equinox-launcher>
>>
>> <uima-eclipse-jar-processor>${uima-maven-build-eclipse-home}/plugins/org.eclipse.equinox.p2.jarprocessor_1.0.300.v20130327-2119.jar</uima-eclipse-jar-processor>
>>
>> <!-- Neon 4.6.2 level -->
>> <!--
>> uima-maven-build-eclipse-home>C:/p/eclipse/461neon</uima-maven-build-eclipse-home-->
>>
>> <!-- eclipse462 neon.2 -->
>> <!--
>> eclipse-equinox-launcher>${uima-maven-build-eclipse-home}/plugins/org.eclipse.equinox.launcher_1.3.201.v20161025-1711.jar</eclipse-equinox-launcher-->
>> <!--
>> uima-eclipse-jar-processor>${uima-maven-build-eclipse-home}/plugins/org.eclipse.equinox.p2.jarprocessor_1.0.500.v20160504-1450.jar</uima-eclipse-jar-processor-->
>>
>> Peter and Jerry, can you say what levels you have for building the plugins
>> you
>> build?
>>
>> I'm trying to see if I can better understand the cause of the recent Eclipse
>> plugin repository errors.
>>
>> -Marshall
>
