[jbosstools-issues] [JBoss JIRA] (JBTIS-470) BPEL plugins are not automatically updated

Max Rydahl Andersen (JIRA) issues at jboss.org
Wed Aug 19 08:23:28 EDT 2015


    [ https://issues.jboss.org/browse/JBTIS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099789#comment-13099789 ] 

Max Rydahl Andersen commented on JBTIS-470:
-------------------------------------------

It is not my opinion.

It is the defacto rules for both Eclipse and any JBoss Tools plugins. 

Its documented at https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/versioning.adoc

Short version: you just don't downversion. It makes no logical sense. You need to update your features and plugins sanely and the docs we got above outline how.


> BPEL plugins are not automatically updated
> ------------------------------------------
>
>                 Key: JBTIS-470
>                 URL: https://issues.jboss.org/browse/JBTIS-470
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>          Components: BPEL, distribution
>    Affects Versions: 8.0.3.GA
>         Environment: JBDS-IS 8.0.3.CR2
>            Reporter: Andrej Podhradsky
>            Assignee: Robert (Bob) Brodt
>
> BPEL plugins are not automatically updated. The problem is that the BPEL feature is still in version 1.3.100.Final-v20141204-2031-B13 but its feature.xml contains 
> {code:xml}
> <import feature="org.eclipse.bpel.feature" version="1.0.0" match="compatible" />
> <import feature="org.eclipse.bpel.common.feature" version="1.0.0" match="compatible" />
> <import feature="org.eclipse.bpel.apache.ode.runtime.feature" version="1.0.0" match="compatible" />
> {code}
> which means that it installs any BPEL plugin compatible with 1.0.0. Note that during updating only feature version is considered, so in this case it is not automatically updated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the jbosstools-issues mailing list