[JBoss JIRA] Created: (JBIDE-5829) Update BPEL deployment plug-ins with JBoss-specific IDs

[JBoss JIRA] Created: (JBIDE-6588)...

[JBoss JIRA] Created: (JBDS-1455)...

Brian Fitzpatrick (JIRA)

Wednesday, 10 February 2010 Wed, 10 Feb '10

12:53 p.m.

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 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

Show replies by date

Brian Fitzpatrick (JIRA)

Wednesday, 10 February Wed, 10 Feb

12:55 p.m.

New subject: [JBoss JIRA] Updated: (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 updated JBIDE-5829: ------------------------------------- Attachment: patch.txt This patch changes the plug-ins to "org.jboss.tools.bpel.deploy.model and *.deploy.ui". Not sure if we need to change the wizard names/ids or anything else, but it seems to work fine.

...

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

Brian Fitzpatrick (JIRA)

12:57 p.m.

New subject: [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: ------------------------------------------ Max, once you've gotten some sleep, can you take a look at this patch and see if anything looks out of whack? Once we get it in and delivered, we can let Nick know and he can hopefully tweak the build.

...

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.

Max Rydahl Andersen (JIRA)

Thursday, 11 February Thu, 11 Feb

7:35 a.m.

New subject: [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: -------------------------------------------- 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.

Max Rydahl Andersen (JIRA)

7:35 a.m.

New subject: [JBoss JIRA] Commented: (JBIDE-5829) Update BPEL deployment plug-ins with JBoss-specific IDs

...

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.

Brian Fitzpatrick (JIRA)

8:28 a.m.

New subject: [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: ------------------------------------------ My original comment was that I merely refactored the plug-ins and plug-in IDs to not conflict with the original org.eclipse.bpel IDs and whether I should refactor the actual code & wizard IDs. :) After our chat yesterday I wasn't sure what exactly you wanted out of this beyond refactoring the plug-in IDs, so that's all I did. So you want the package names, wizard IDs, etc. refactored as well? As far as the "bpelContent" folder, I saw that and we ran into an issue with the BPEL Project Examples where that folder is actually "bpel" instead of "bpelContent". When I checked with Gary, that folder is supposed to always be "bpelContent" just as ESB has its consistent "esbcontent" folder.

...

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.

Max Rydahl Andersen (JIRA)

Friday, 12 February Fri, 12 Feb

12:01 p.m.

New subject: [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.

Max Rydahl Andersen (JIRA)

12:31 p.m.

New subject: [JBoss JIRA] Updated: (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 updated JBIDE-5829: --------------------------------------- Assignee: Brian Fitzpatrick (was: Max Rydahl Andersen)

...

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.

Brian Fitzpatrick (JIRA)

5:42 p.m.

New subject: [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.

Brian Fitzpatrick (JIRA)

Monday, 15 February Mon, 15 Feb

8:24 a.m.

New subject: [JBoss JIRA] Updated: (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 updated JBIDE-5829: ------------------------------------- Fix Version/s: 3.2.next (was: 3.1.0.CR2)

...

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.2.next 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.

Brian Fitzpatrick (JIRA)

Wednesday, 28 April Wed, 28 Apr

9:57 a.m.

New subject: [JBoss JIRA] Assigned: (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 reassigned JBIDE-5829: ---------------------------------------- Assignee: Robert (Bob) Brodt (was: Brian Fitzpatrick) Bob, I'm not sure this is still as much an issue if we get the ability to actually become Eclipse BPEL committers, but I'm going to put it into your bucket for now.

...

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: Robert (Bob) Brodt Priority: Critical Fix For: 3.2.next 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.

Brian Fitzpatrick (JIRA)

Wednesday, 26 May Wed, 26 May

10:48 a.m.

New subject: [JBoss JIRA] Updated: (JBIDE-5829) Update BPEL deployment plug-ins with JBoss-specific IDs

[ https://jira.jboss.org/browse/JBIDE-5829?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick updated JBIDE-5829: ------------------------------------- Component/s: bpel

...

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.next 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

Brian Fitzpatrick (JIRA)

Friday, 27 August Fri, 27 Aug

12:04 p.m.

New subject: [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... ] Brian Fitzpatrick commented on JBIDE-5829: ------------------------------------------ Bob, this is an old bug. I seem to recall a different JIRA about separate Riftsaw vs. generic ODE deployment mechanisms. Was that ever resolved?

...

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.

Robert (Bob) Brodt (JIRA)

1:42 p.m.

New subject: [JBoss JIRA] Commented: (JBIDE-5829) Update BPEL deployment plug-ins with JBoss-specific IDs

...

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.

Robert (Bob) Brodt (JIRA)

Tuesday, 14 September Tue, 14 Sep

10:52 a.m.

New subject: [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.

Brian Fitzpatrick (JIRA)

11:39 a.m.

New subject: [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... ] Brian Fitzpatrick commented on JBIDE-5829: ------------------------------------------ No arguments here.

...

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.

Robert (Bob) Brodt (JIRA)

Friday, 17 September Fri, 17 Sep

10:42 a.m.

New subject: [JBoss JIRA] Updated: (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 updated JBIDE-5829: -------------------------------------- Fix Version/s: 3.2.0.CR1 (was: 3.2.x) Moved to 3.2.0.CR1

...

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.0.CR1 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.

Brian Fitzpatrick (JIRA)

Wednesday, 6 October Wed, 6 Oct

3:34 p.m.

New subject: [JBoss JIRA] Updated: (JBIDE-5829) Update BPEL deployment plug-ins with JBoss-specific IDs

[ https://jira.jboss.org/browse/JBIDE-5829?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick updated JBIDE-5829: ------------------------------------- Component/s: (was: bpm)

...

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 Reporter: Brian Fitzpatrick Assignee: Robert (Bob) Brodt Priority: Critical Fix For: 3.2.0.Beta2 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.

Feng Qian (JIRA)

Friday, 8 October Fri, 8 Oct

3:59 a.m.

New subject: [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... ] Feng Qian commented on JBIDE-5829: ---------------------------------- Should we change these ids? We will finally use eclipse bpel, so I think we don't need to update these ids for now. Just need to fix JBIDE-6588,right?

...

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 Reporter: Brian Fitzpatrick Assignee: Feng Qian Priority: Critical Fix For: 3.2.0.Beta2 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.

Feng Qian (JIRA)

Thursday, 14 October Thu, 14 Oct

12:17 a.m.

New subject: [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... ] Feng Qian commented on JBIDE-5829: ---------------------------------- Any ideas?

...

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 Reporter: Brian Fitzpatrick Assignee: Feng Qian Priority: Critical Fix For: 3.2.0.Beta2 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.

Feng Qian (JIRA)

Wednesday, 20 October Wed, 20 Oct

12:49 a.m.

New subject: [JBoss JIRA] Updated: (JBIDE-5829) Update BPEL deployment plug-ins with JBoss-specific IDs

[ https://jira.jboss.org/browse/JBIDE-5829?page=com.atlassian.jira.plugin.s... ] Feng Qian updated JBIDE-5829: ----------------------------- Fix Version/s: 3.2.0.CR1 (was: 3.2.0.Beta2) put it to later

...

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 Reporter: Brian Fitzpatrick Assignee: Feng Qian Priority: Critical Fix For: 3.2.0.CR1 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.

Feng Qian (JIRA)

Thursday, 9 December Thu, 9 Dec

2:25 a.m.

New subject: [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... ] Feng Qian commented on JBIDE-5829: ---------------------------------- Bob, as long as we are to use eclipse bpel six months later, I think we have no requirement to fix this issue for CR1, right?

...

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 Reporter: Brian Fitzpatrick Assignee: Feng Qian Priority: Critical Fix For: 3.2.0.CR1 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Robert (Bob) Brodt (JIRA)

Tuesday, 21 December Tue, 21 Dec

3:52 p.m.

New subject: [JBoss JIRA] Updated: (JBIDE-5829) Update BPEL deployment plug-ins with JBoss-specific IDs

[ https://issues.jboss.org/browse/JBIDE-5829?page=com.atlassian.jira.plugin... ] Robert (Bob) Brodt updated JBIDE-5829: -------------------------------------- Fix Version/s: LATER (was: 3.2.0.CR1) This can wait until LATER

...

Update BPEL deployment plug-ins with JBoss-specific IDs ------------------------------------------------------- Key: JBIDE-5829 URL: https://issues.jboss.org/browse/JBIDE-5829 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Reporter: Brian Fitzpatrick Assignee: Robert (Bob) Brodt Priority: Critical Fix For: LATER 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira

5590

days inactive

5904

days old

jbosstools-issues@lists.jboss.org

Manage subscription

22 comments

4 participants

tags (0)

participants (4)

Brian Fitzpatrick (JIRA)
Feng Qian (JIRA)
Max Rydahl Andersen (JIRA)
Robert (Bob) Brodt (JIRA)

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[JBoss JIRA] Created: (JBIDE-5829) Update BPEL deployment plug-ins with JBoss-specific IDs