[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5829) Update BPEL deployment plug-ins with JBoss-specific IDs
[
https://jira.jboss.org/jira/browse/JBIDE-5829?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-5829:
--------------------------------------------
Just to be clear, "bpelContent" and "esbcontent" are simply defaults
but *nothing* should be hardcoded to it.
I had actually hoped we would just use "src" or "bpel" or
"esb" for short. Its an ancient WTP antipattern to call things
"<moduletype>Content".
But that is for Later to fix.
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