Bug 745838 (EDG-61) - datagrid installer is not idempotent
Summary: datagrid installer is not idempotent
Keywords:
Status: CLOSED NEXTRELEASE
Alias: EDG-61
Product: JBoss Data Grid 5
Classification: JBoss
Component: Infinispan
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: EAP 5.1.0 EDG TP
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/EDG-61
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-30 15:44 UTC by Richard Achmatowicz
Modified: 2011-10-11 17:05 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-30 15:54:17 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 745835 0 high CLOSED Provide build.sh for installation of EDG server profile 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker EDG-61 0 None Closed datagrid installer is not idempotent 2011-10-24 02:53:05 UTC

Internal Links: 745835

Description Richard Achmatowicz 2010-11-30 15:44:22 UTC 
Complexity: Low
project_key: EDG

There is a problem with the installation of the datagrid profile when svn update is used: 
files which are copied to create the datagrid profile are not replaced with fresh copies and comments change from this:
<!-- a comment -->
to this:
<!--<!-- a comment --> -->
which generates a parsing exception.
This is due to copy commands not setting the attribute overwrite="true".

This happens in the file cluster/src/installers/datagrid/build.xml which is the build.xml file called by the datagrid installer.
Simplest way to fix this is to delete any existing datagrid directory before beginning.
Comment 1 Richard Achmatowicz 2010-11-30 15:44:23 UTC 
Link: Added: This issue Cloned from JBPAPP-5466
Comment 2 Richard Achmatowicz 2010-11-30 15:54:02 UTC 
Added ant task 

<delete dir="${server.datagrid}"/>

to the beginning of the datagrid server profile construction.
Note You need to log in before you can comment on or make changes to this bug.