[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5829) Update BPEL deployment plug-ins with JBoss-specific IDs
[
https://jira.jboss.org/browse/JBIDE-5829?page=com.atlassian.jira.plugin.s...
]
Robert (Bob) Brodt commented on JBIDE-5829:
-------------------------------------------
Yikes! I think this JIRA is getting out of hand ;)
1. the plug-in ID conflict issues will go away once the JBoss and Eclipse BPEL codelines
become one, and we start consuming only the Eclipse project. This will definitely not make
it into the beta, but will be in the final.
2. the "bpelContent" folder name issue is already tracked with JBIDE-6170. Not
sure if this will make it into the beta
3. deployment to tomcat/ODE is being tracked with JBIDE-6588. Not sure if this will make
it into the beta
Any objections to leaving this open for now until after the beta code freeze when it will
be triaged again?
Update BPEL deployment plug-ins with JBoss-specific IDs
-------------------------------------------------------
Key: JBIDE-5829
URL: https://jira.jboss.org/browse/JBIDE-5829
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm
Reporter: Brian Fitzpatrick
Assignee: Robert (Bob) Brodt
Priority: Critical
Fix For: 3.2.x
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira