-
Bug
-
Resolution: Done
-
Critical
-
8.0.0.GA
-
None
When one tries to add a featurepack to existing EAP installation and the tries to cancel it when prompted, the installation is performed anyway:
MYFACES_VERSION=4.0.2 ./bin/jboss-eap-installation-manager.sh fp add --fpl=org.jboss.eap:eap-myfaces-feature-pack --layers=myfaces --repositories=mrrc::https://maven.repository.redhat.com/ga/,central::https://repo1.maven.org/maven2 --verbose
Installing feature pack `org.jboss.eap:eap-myfaces-feature-pack` in server `/tmp/test2/jboss-eap-8.0/.`
Continue adding the feature pack? [y/N]:N
Installation cancelled
Feature-packs resolved.
Packages installed.
Downloaded artifacts.
JBoss modules installed.
Configurations generated.
JBoss examples installed.
Operation completed in 44.61 seconds.
The result of above command on filesystem is exactly the same as with the willingly performed installation (it only differs in installation timestamps):
MYFACES_VERSION=4.0.2 ./bin/jboss-eap-installation-manager.sh fp add --fpl=org.jboss.eap:eap-myfaces-feature-pack --layers=myfaces --repositories=mrrc::https://maven.repository.redhat.com/ga/,central::https://repo1.maven.org/maven2 --verbose
Installing feature pack `org.jboss.eap:eap-myfaces-feature-pack` in server `/tmp/test2/jboss-eap-8.0/.`
Continue adding the feature pack? [y/N]:y
Applying changes
Feature-packs resolved.
Packages installed.
Downloaded artifacts.
JBoss modules installed.
Configurations generated.
JBoss examples installed.
Operation completed in 41.12 seconds.
This is clearly not what user would expect as the EAP installation is updated contrary to instructions.
- is incorporated by
-
JBEAP-26573 (8.0.z) Upgrade jboss-eap-installation-manager (prospero) to 1.1.8.Final
-
- Closed
-
