Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 880647

Summary:	Move SOA related property from JBDS core to SOA tooling
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Len DiMaggio <ldimaggi>
Component:	Tooling	Assignee:	Default User <jbpapp-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	atangrin, dlesage, soa-p-jira
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-11 19:25:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Len DiMaggio 2012-11-27 13:54:47 UTC

Description of problem:

See: https://issues.jboss.org/browse/JBDS-2406

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 JBoss JIRA Server 2012-11-27 16:20:53 UTC

Nick Boldt <nboldt> made a comment on jira JBDS-2406

[~ldimaggio] can you flesh out this request a little? What property? Is it something that SOA tooling would simply override when installed to allow more/different RTs to be understood, or something that has to be MOVED OUT of JBDS Core and into JBDS SOA somewhere?

Also, where might it live? In https://github.com/jbosstools/jbosstools-runtime-soa ? Seems the logical place but that project was scheduled for demolition in favour of its contents moving to the three parent projects, Drools, jbpm, and esb (or perhaps droolsjbpm and esb?).

Comment 2 JBoss JIRA Server 2012-11-28 17:41:45 UTC

Max Rydahl Andersen <max.andersen> made a comment on jira JBDS-2406

Updated the title to be more specific.

And no, I don't see this happening in JBDS 5.x and in worst case not even in JBDS 6 since current design of ESB and WTP tooling does not allow for this.

Feature request should be made for JBDS 6/7 and worked out between dev of esb and server tooling.

(note, a possible solution for ESB is that instead of requiring a new facet version for *eveyr* release of ESB (4.0.1,4.0.2,4.0.3, ....4.0.11, etc.) would be it got a 4.0.12+ version that would not require constant updates.

Comment 3 JBoss JIRA Server 2013-01-09 14:13:57 UTC

Rob Stryker <rob.stryker> updated the status of jira JBDS-2406 to Resolved

Comment 4 JBoss JIRA Server 2013-01-09 14:13:57 UTC

Rob Stryker <rob.stryker> made a comment on jira JBDS-2406

Please check the patches over in JBIDE-13209. I've closed about 7 of these now. God. 

I am assuming this is in regards to the add/remove project wizard, not the facets, as the add/remove wizard was the issue that was driving this bug.

Comment 6 Anne-Louise Tangring 2013-11-11 19:25:51 UTC

Can be closed - this is done in JBTIS