Yes, I can reproduce... looks like although the files are there, the artifacts and
Looks like a bug that has mostly gone unnoticed... Thanks for reporting... hope your build works; if not I'm around to help debug :-) -Marshall On 1/28/2019 9:54 AM, Peter Klügl wrote: > Yes, I only see 2.10.3 on our official update site. > > > For Ruta: I will update the update site for RC1 > > > Peter > > > Am 28.01.2019 um 15:51 schrieb Marshall Schor: >> Hi Peter, >> >> Re: the Uima V2: >> >> Here's the intent: >> To have 2.10.2 and 2.10.3 on our official update site. >> To have the older versions here: >> >> http://archive.apache.org/dist/uima/archive-eclipse-update-site/uimaj-2.3.1-2.10.1/ >> >> I did a quick look at the official one, and see 2 releases (2.10.2 and >> 2.10.3); >> >> What did you observe when testing? Did the update site not have 2.10.2 when >> actually used? >> >> -Marshall >> >> On 1/28/2019 4:07 AM, Peter Klügl wrote: >>> Ah ok. >>> >>> >>> Yes, this was not intentional. >>> >>> >>> I thought that the condition did work even if the property is missing >>> since the build downloaded the old bundles. So, I thought the default is >>> 'false'. >>> >>> >>> How should we proceed? >>> >>> >>> I can build a new update site with the same staged artifacts since the >>> update site build is still a separate/manual step in the release process. >>> >>> I could also do a new RC2. >>> >>> Or we proceed and accept that the older versions are missing. For me, >>> this is not a problem. in my opinion, the users should install the >>> latest version anyway. And we could fix this for the next release. >>> >>> >>> Btw, when I was testing this, I observed the same issue for the uimaj v2 >>> bundles in our official update site. >>> >>> >>> Best, >>> >>> >>> Peter >>> >>> >>> >>> Am 25.01.2019 um 20:05 schrieb Marshall Schor: >>>> to see this, uncheck the "Show only the latest versions of available >>>> software". >>>> >>>> For the www.apache.org/dist/uima/eclipse-update-site/ruta, you see versions >>>> >>>> 2.1.0, 2.2.0, 2.2.1, 2.3.0, 2.3.1, 2.4.0, 2.5.0, 2.6.0, 2.6.1 >>>> >>>> for the new update site, only 2.7.0 >>>> >>>> This isn't necessarily a bad thing, see >>>> https://uima.apache.org/dev-eclipse-plugin-archiving. >>>> >>>> But it seems it wasn't intentional. >>>> What has gone wrong is that the update site build pom needs to add a >>>> property: >>>> <dropPrevVersions>false</dropPrevVersions> >>>> >>>> If not specified, it is defaulting to true in the pom test on line 154 in >>>> the >>>> eclipse-update-site's pom.xml. >>>> >>>> -Marshall >>>> >>>> On 1/25/2019 1:50 PM, Peter Klügl wrote: >>>>> Hi, >>>>> >>>>> >>>>> this should not have changed. I see 2.1.0 and later bundles for the staged >>>>> update site: >>>>> >>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/features/ >>>>> >>>>> >>>>> >>>>> I have not checked if it is possible install older version during my >>>>> review. >>>>> >>>>> What do you mean exactly? The update process in Eclispe? >>>>> >>>>> >>>>> >>>>> Best, >>>>> >>>>> >>>>> Peter >>>>> >>>>> >>>>> Am 25.01.2019 um 19:46 schrieb Marshall Schor: >>>>>> The eclipse update site no longer has any previous release versions of >>>>>> the >>>>>> plugins. >>>>>> >>>>>> Is this intentional? >>>>>> >>>>>> -Marshall >>>>>>
