Bug 894120 - JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-P 5.3.1.ER2 and later
Summary: JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Tooling
Version: 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: GA
: 5.3.1
Assignee: Default User
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-10 18:45 UTC by Len DiMaggio
Modified: 2016-01-06 11:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-06 11:58:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker jBDS-2444 0 Blocker Closed JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-P 5.3.1.ER2 and later 2016-01-06 11:56:39 UTC

Description Len DiMaggio 2013-01-10 18:45:59 UTC
Description of problem:

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

Comment 1 JBoss JIRA Server 2013-01-10 20:02:01 UTC
Nick Boldt <nboldt> made a comment on jira JBDS-2444

Fix affectsVersion and fxiVersion to be 5.0.2-SOA and 5.0.3-SOA.

Comment 2 JBoss JIRA Server 2013-01-29 08:27:59 UTC
Andrej Podhradsky <apodhrad> updated the status of jira JBDS-2444 to Resolved

Comment 3 JBoss JIRA Server 2013-01-29 08:27:59 UTC
Andrej Podhradsky <apodhrad> made a comment on jira JBDS-2444

Fixed in 5.0.3.GA-SOA

Comment 4 JBoss JIRA Server 2013-01-29 08:28:34 UTC
Andrej Podhradsky <apodhrad> updated the status of jira JBDS-2444 to Closed

Comment 5 JBoss JIRA Server 2013-01-29 08:28:34 UTC
Andrej Podhradsky <apodhrad> made a comment on jira JBDS-2444

Verified with SOA Tooling 5.0.3.v20130128-1900-H4-GA

Comment 6 Andrej Podhradsky 2013-01-29 13:01:37 UTC
Verified with JBDS 5.0.2.GA.v20130119-0035-H249-GA + SOA Tooling 5.0.3.v20130128-1900-H4-GA

Comment 7 Andrej Podhradsky 2016-01-06 11:58:38 UTC
Fixed and included in the latest release.


Note You need to log in before you can comment on or make changes to this bug.