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 (JIRA)" <de...@uima.apache.org> on 2018/11/29 21:45:00 UTC
[jira] [Closed] (UIMA-5914) Eclipse Update Site for 2.10.2 needs
dist svn tag
[ https://issues.apache.org/jira/browse/UIMA-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-5914.
--------------------------------
Resolution: Fixed
> Eclipse Update Site for 2.10.2 needs dist svn tag
> -------------------------------------------------
>
> Key: UIMA-5914
> URL: https://issues.apache.org/jira/browse/UIMA-5914
> Project: UIMA
> Issue Type: Task
> Components: Eclipse plugins
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
>
> While checking the eclipse update site for uimaj 2.10.3 after jar-signing the plugins/features, I noticed that although the update site has both the 2.10.2 and 2.10.3 jars, the Eclipse FeaturesAndBundlesPublisher only generated the contents/artifacts jars with the metadata for the 2.10.3. This wasn't an issue when running the same process for uv3 3.0.1.
> The consequence: when installing, if you uncheck the box to show just the most recent version, the 2.10.2 version doesn't show up.
> My educated guess is that this might be caused by having switched the minimum JVM level for 2.10.3 from Java 7 to Java 8, and the Eclispe FeaturesAndBundlesPublisher disallowing mixing of JVM minimum level requirements.
> To work around this, I'm planning on doing an "svn tag" on the Eclipse update site for uimaj to create a separately addressable update site for the 2.10.2 (in case anyone needs that). In the news article and website download page, I'll add a note about this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)