Bug 712436 - Default ANT target is not executed when deploying bundle via JON/RHQ.
Default ANT target is not executed when deploying bundle via JON/RHQ.
Status: NEW
Product: RHQ Project
Classification: Other
Component: Provisioning (Show other bugs)
3.0.1
x86_64 Linux
medium Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-10 11:42 EDT by Duncan Doyle
Modified: 2011-10-07 15:00 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Duncan Doyle 2011-06-10 11:42:36 EDT
Description of problem:
When you create a Bundle recipe file and define a 'default' ANT target (for example 'main'), this target will be executed by the RHQ Bundle Deployer, i.e. the command line test tool. However, when you deploy your bundle with JBoss Operations Network (2.4.1), this default ANT target is not executed

Version-Release number of selected component (if applicable):
JBoss Operations Network 2.4.1

How reproducible:
Create an ANT bundle recipe with a default ANT target which, for example, creates a file in a certain directory. Deploy that bundle with the command line RHQ Bundle Deployer, the file will be created. Deploy the same bundle via JON, the file will not be created.

Steps to Reproduce:
1. Create a ANT Bundle file with a default ANT target which creates a file in a directory and deploy that bundle via JON
  
Actual results:
The default ANT target is not executed, so no file gets created.

Expected results:
Default target gets executed, file gets created.

Additional info:
Talked with Mazz about this on IRC and the problem is due to GIT commit: 8b50ba816d704ced7668a7fa6aa869416ba0c043 . This commit commented out the following code:
// Should we execute the default target here?
//project.executeTarget(project.getDefaultTarget());

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