Created attachment 933879 [details] domain_deployment_application_version Description of problem: [domain mode] application version is 'none' for domain deployments Version-Release number of selected component (if applicable): JON 3.3 ER01.1 How reproducible: always Steps to Reproduce: Scenario #1 1. navigate to eap6 in domain mode 2. create a child resource as domain deployment 3. upload test.war and deploy to all main server group Scenario#2 1. create a bundle with test.war app 2. deploy to eap6 in domain mode (to main managed server ) Actual results: application version is 'None' Expected results: Application is versioned Additional info: screen-shot attached
Master commit 3bc7d6bfc641e6a477d08c3b4fa1208536dc9e54 Author: Jay Shaughnessy <jshaughn> Date: Wed Sep 10 14:22:01 2014 -0400 Add versioned-deployment logic to domain deployments. This includes resource upgrade for existing resources. Also, tweak the operations to use the correct path value as opposed to the version-stripped resource key. Release/jon3.3.x commit b00520710a6dc7949327bb73da141608e12e53fc Author: Jay Shaughnessy <jshaughn> Date: Wed Sep 10 14:22:01 2014 -0400 (cherry picked from commit 3bc7d6bfc641e6a477d08c3b4fa1208536dc9e54) Signed-off-by: Jay Shaughnessy <jshaughn> Test Notes: Should include resource upgrade for an existing version-named domain deployment, as well as deployment of a new resource. And then subsequent server group assignment.
Moving to ON_QA as available for test with the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=385149
Created attachment 938462 [details] domain_delp_version
during the bundle deployment - bundle version is not considered as version for app, app version is detected from app file name *only* marking as verified in JON 3.3 ER03 screen-shot attached