Bug 780605 (SOA-3045) - ER2 build for SOA-P 4.3 CP05 is missing the notifications quickstart
Summary: ER2 build for SOA-P 4.3 CP05 is missing the notifications quickstart
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3045
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB, Examples
Version: 4.3 CP05 ER2,4.3 CP05 ER3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP05 ER3
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-26 16:31 UTC by Len DiMaggio
Modified: 2011-04-26 16:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-26 16:32:07 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3045 0 Major Closed ER2 build for SOA-P 4.3 CP05 is missing the notifications quickstart 2012-11-16 19:55:25 UTC

Description Len DiMaggio 2011-04-26 16:31:39 UTC
project_key: SOA

find /opt/local/43CP05ER2 -name notifications -print 
<null>

It was there in CP04:

find /opt/local/43CP04GA -name notifications -print
/opt/local/43CP04GA/jboss-soa-p.4.3.0/jboss-as/samples/quickstarts/notifications
/opt/local/43CP04GA/jboss-soa-p.4.3.0/jboss-as/samples/quickstarts/notifications/src/org/jboss/soa/esb/samples/quickstart/notifications
/opt/local/43CP04GA/jboss-soa-p-standalone.4.3.0/jboss-esb/samples/quickstarts/notifications
/opt/local/43CP04GA/jboss-soa-p-standalone.4.3.0/jboss-esb/samples/quickstarts/notifications/src/org/jboss/soa/esb/samples/quickstart/notification

Comment 1 Len DiMaggio 2011-04-26 16:32:07 UTC
Verified in ER3

find /opt/local/43CP05ER3 -name notifications -print
/opt/local/43CP05ER3/jboss-soa-p.4.3.0/jboss-as/samples/quickstarts/notifications
/opt/local/43CP05ER3/jboss-soa-p.4.3.0/jboss-as/samples/quickstarts/notifications/src/org/jboss/soa/esb/samples/quickstart/notifications


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