[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...
]
Brian Fitzpatrick commented on JBIDE-5829:
------------------------------------------
I'm bumping this to Later then. It works as is for now, even with the "ancient
antipattern".
Down the line we can probably change this, but unless this is breaking anything beyond
your sensibilities, I don't have a good way to solve this for this release...
Especially since BPEL projects are not Java projects and therefore there isn't a good
way to get "source" folders unless you found one. But adding in checks for this
this late in the game doesn't make sense to me.
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: Brian Fitzpatrick
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