[
https://issues.jboss.org/browse/JBIDE-9646?page=com.atlassian.jira.plugin...
]
Nick Boldt updated JBIDE-9646:
------------------------------
Summary: JBT BPEL is 0.7.0 (old JBoss fork) but JBDS BPEL is 0.5.0 (new Eclipse fork)
[was org.eclipse.bpel.apache.ode.deploy.ui has no provider or plugin name] (was:
org.eclipse.bpel.apache.ode.deploy.ui has no provider or plugin name)
rename jira to reflect new snafu. somehow the JBT SOA Tooling site is pulling from old
0.7.0 bits instead of the new 0.5.0 versions @ Eclipse.
JBT BPEL is 0.7.0 (old JBoss fork) but JBDS BPEL is 0.5.0 (new
Eclipse fork) [was org.eclipse.bpel.apache.ode.deploy.ui has no provider or plugin name]
-------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-9646
URL:
https://issues.jboss.org/browse/JBIDE-9646
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: BPEL, UpStream
Affects Versions: 3.3.0.M3
Reporter: Nick Boldt
Assignee: Robert (Bob) Brodt
Priority: Minor
Fix For: 3.3.0.Beta1
Attachments: snapshot15.png, snapshot16.png, snapshot7.png
Minor nitpick -- the providerName and pluginName are not being displayed correctly.
This is either due to a missing directive in the manifest.mf telling Eclipse this is a
plugin, or your build.properties doesn't include mention of your plugin.properties
(and license.html) files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira