Bug 778370 (SOA-853) - reconfigure macro in schema/build.xml destroys original files
Summary: reconfigure macro in schema/build.xml destroys original files
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-853
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Build Process
Version: 4.2 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP03
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-25 19:28 UTC by nwallace
Modified: 2008-10-23 10:25 UTC (History)
0 users

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778190 0 urgent CLOSED The schema tool is broken for files when multiple changes as required 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-853 0 None None None Never

Internal Links: 778190

Description nwallace 2008-09-25 19:28:59 UTC
Date of First Response: 2008-10-23 06:25:38
project_key: SOA

The reconfigure macro moves files to {file}.orig, and then moves them instead of copying them - which destroys the original file.      If the second move in the sequence were a copy instead of a move, it would be possible to rerun the schema script.    I think the intention was to preserve the original file - the subsequent copies don't overwrite the .orig files.   

      <macrodef name="reconfigure">
            <attribute name="file"/>
            <attribute name="old"/>
            <attribute name="new"/>
            <sequential>
                <move file="@{file}" tofile="@{file}.orig"/>
                <move file="@{file}.orig" tofile="@{file}">
                    <filterchain>
                        <replacestring from="@{old}" to="@{new}"/>
                    </filterchain>
                </move>
            </sequential>
        </macrodef>

Comment 1 nwallace 2008-09-25 19:28:59 UTC
Link: Added: This issue related SOA-695


Comment 2 nwallace 2008-09-25 19:29:33 UTC
Link: Added: This issue is duplicated by SOA-567


Comment 3 nwallace 2008-09-25 19:30:14 UTC
Can we have confirmation that fixes are in place for 4.2CP03.

Comment 4 Julian Coleman 2008-10-23 10:25:38 UTC
We will not fix this for 4.2CP03.


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