[jbosstools-issues] [JBoss JIRA] (JBTIS-470) BPEL plugins are not automatically updated
[
https://issues.jboss.org/browse/JBTIS-470?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBTIS-470:
----------------------------------
( a ) won't cause the update to happen via Help > Check for updates, but you would
see them as updateable in Central.
I could not parse this sentence:
{quote}But C (using include) is something we discourage greatly so not sure why we not
only suggest doing b - make sure the feature.xml has proper ranges ?{quote}
Are you saying we should do BOTH ( b ) and ( c ) ? Or just ( b ) ?
(I don't see the problem w/ using INCLUDE, if there's a hard-tied dependency
between o.j.t.bpel and o.e.bpel versions. If it's flexible, then REQUIRE is fine.)
Anyway, it's all just email-from-JIRA-spam until [~bbrodt] tells us what HE wants to
do here.
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)