Bug 778105 (SOA-616) - Fallout from SOA-164 overwrites quickstarts.properties-example
Summary: Fallout from SOA-164 overwrites quickstarts.properties-example
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-616
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Build Process
Version: 4.2 CP02
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.3 IR4
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-01 10:45 UTC by Julian Coleman
Modified: 2008-10-09 09:23 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-09 09:23:52 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777654 0 urgent CLOSED Quickstarts included in EAP version do not deploy 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 778364 0 medium CLOSED Fallout from SOA-164 overwrites quickstarts.properties-example 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-616 0 None None None Never

Internal Links: 777654 778364

Description Julian Coleman 2008-07-01 10:45:17 UTC 
Affects: Interactive Demo/Tutorial
Complexity: Low
project_key: SOA

There is no longer any need to overwrite quickstarts.properties-example, as was done as a fix for SOA-164.
Comment 1 Julian Coleman 2008-07-01 15:28:09 UTC 
Link: Added: This issue is related to SOA-164
Comment 2 Julian Coleman 2008-07-01 15:30:06 UTC 
Fixed in revision 1376 of:

  builders/eap/build.xml
  builders/esb/build.xml
  resource/default-config-files

Commit message:

  Remove overwrite of ESB quickstarts.properties-example, as changes to the
  quickstarts no longer require the workaround.
Comment 3 nwallace 2008-09-25 18:56:01 UTC 
Link: Added: This issue related SOA-847
Comment 4 Julian Coleman 2008-10-09 09:23:52 UTC 
Verified against embedded and standalone in IR5.
Note You need to log in before you can comment on or make changes to this bug.