[
https://jira.jboss.org/jira/browse/JBIDE-5829?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-5829:
--------------------------------------------
I got some sleep and looked at this and is finding I can't figure out what has
actually changed in this plugin that alter its behavior ?
I see this patch:
http://fisheye.jboss.org/browse/JBossTools/trunk/bpel/plugins/org.eclipse...
which is broken btw. since it hardcodes the "bpelContent" folder. That's
just wrong since I should be able to name it whatever I want.
This patch also relates to this:
http://fisheye.jboss.org/changelog/JBossTools/trunk/bpel/plugins/org.ecli...
And the new things about bpel wizard and project info I see as in
org.eclipse.bpel.runtimes.
Thus for me it just looks like this two plugins provide apache ode specfiic descriptor
file support - nothing riftsaw or jboss tools specific in here ? (beyond the locating
where to put the files by default initially - but that would be the same for our stuff or
apache ode...)
What changes is there in here which are specific to us ?
Update BPEL deployment plug-ins with JBoss-specific IDs
-------------------------------------------------------
Key: JBIDE-5829
URL:
https://jira.jboss.org/jira/browse/JBIDE-5829
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.1.0.CR2
Attachments: patch.txt
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
While reviewing the state of the BPEL editor, it came up that the deployment plug-ins
(the o.e.bpel.apache.ode.* plugins), though they included JBoss Riftsaw-specific code,
were still the same plug-in IDs & project names as were in the BPEL project at
Eclipse.org.
These need to change so we don't run into conflicts with the Eclipse project.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira