[jbosstools-issues] [JBoss JIRA] (JBTIS-470) BPEL plugins are not automatically updated
Max Rydahl Andersen (JIRA)
issues at jboss.org
Wed Aug 19 16:53:26 EDT 2015
[ https://issues.jboss.org/browse/JBTIS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099964#comment-13099964 ]
Max Rydahl Andersen commented on JBTIS-470:
-------------------------------------------
I'm saying C is bad, so why not just suggest B.
If we do C we *must* always bump our feature to get the updates done on eclipse.org bpel side - I do not think that is what we want.
We can still have hard-tied dependencies by using limited version range in the require, right ?
> 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