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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBTIS-470:
----------------------------------

category.xml is irrelevant here. Issue is whether or not you want o.j.t.bpel.feature to forceably drag in the latest o.e.bpel.* stuff. (Is it really required?)

IF YOU DO, then you have to update one of three things:

a) the connector in your discovery plugin's plugin.xml to include these three o.e.bpel.* features, to make Eclipse see the new features and offer them via Central
b) the org.jboss.tools.bpel.feature's feature.xml to include a different requirement range, to force users to upgrade to something newer via Help > Check for updates
c) the org.jboss.tools.bpel.feature's feature.xml to use INCLUDE instead of REQUIRE, to hard-couple the dependency and see new stuff via Help > Check for updates

IF YOU DO NOT, then there's nothing to do here but explain to QE / users that 1.0.4 is good enough, and they don't need 1.0.5 (but can intentionally choose to update to that if they want).

Maybe you should ask [~bbrodt] what he wants to happen to his existing 8.0.2 / 1.0.4 users. Should they automatically move up to 1.0.5? or is 1.0.4 good enough?



> 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)