Bug 1009338 - auto.xml file is not portable among eap versions
Summary: auto.xml file is not portable among eap versions
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Installer
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Thomas Hauser
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-18 08:59 UTC by Petr Kremensky
Modified: 2017-10-10 00:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-22 09:19:41 UTC
Type: Enhancement

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

Description Petr Kremensky 2013-09-18 08:59:55 UTC 
Description of problem:
We are using auto.xml (file generated by installer for multiple installation of same EAP instance) in dist-diff tests.

In 6.1.1 we were able to use auto.xml generated by EAP 6.1.0 installer, but with 6.2.0 we get:
[ Automated installation FAILED! ]

Would it be too much of an effort to make auto.xml portable among versions? 
We could start with 6.2 and every new feature in upcoming EAP releases would use default configuration if it is not present in auto.xml generated by older release.
Comment 1 Thomas Hauser 2013-09-18 14:16:42 UTC 
This is occurring because the 6.2.0 installer has many new features that are not referenced at all in the 6.1.0 / 6.1.1 installer. IzPack reads the auto.xml and can't decide or use these new options, so it fails.

Changing this behavior would require extensive modification to IzPack.
Note You need to log in before you can comment on or make changes to this bug.