Bug 653880 - "clean directory" option during bundle deployment does not work as it should
Summary: "clean directory" option during bundle deployment does not work as it should
Keywords:
Status: CLOSED DUPLICATE of bug 659142
Alias: None
Product: RHQ Project
Classification: Other
Component: Provisioning
Version: 3.0.0
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-16 11:03 UTC by bkramer
Modified: 2018-11-14 09:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-14 16:16:03 UTC
Embargoed:


Attachments (Terms of Use)

Description bkramer 2010-11-16 11:03:32 UTC
Description of problem:

When deploying a bundle to a directory with "clean directory" option unset, all the files that were initially in the destination directory (even if they were not part of the bundle) will be removed. At the same time, directories that were initially in the destination directory will not be deleted. 


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

How reproducible:
It is reproducible every time.

Steps to Reproduce:

1) create a bundle;
2) create a temp directory (containing different files and directories);
3) deploy bundle on the temp directory with "Clean" option unset;
4) After successful deployment check the content of the deployment directory.

  
Actual results:

The content of the destination directory is not preserved. All the files that were in the destination directory before a bundle is deployed are deleted.


Expected results:

When "clean directory" option is not set, the content of the destination folder should be preserved.

Comment 1 John Mazzitelli 2010-12-14 16:16:03 UTC
after looking at this, it appears this is a dup of bug 659142. gonna see if we can address that 659142 soon, in which case this issue would also be fixed.

*** This bug has been marked as a duplicate of bug 659142 ***


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