rhq:file and rhq:url-file each support the ability to indicate where the file should be copied on the destination machine. rhq:archive and rhq:url-archive does not support those attributes. However, it would be nice to be able to tell where you want the archive to be stored. Note this probably only makes sense when exploded="false" since the zip file doesn't exist if its exploded. <rhq:archive name="test.zip" exploded="false" destinationDir="subdir" ... would mean the test.zip would get copied in ${rhq.deploy.dir}/subdir. <rhq:url-archive url="http://server/files/test.zip" exploded="false" destinationDir="subdir" ... would mean the test.zip would be downloaded from that URL and stored in ${rhq.deploy.dir}/subdir. Today, you have no choice but to have the downloaded file stored directly in ${rhq.deploy.dir}.
After some discussion decided that only the "destinationDir" attribute should be supported and not to support renaming archives. Also, currently supporting this only when exploded=false. Wiki updated: https://docs.jboss.org/author/display/RHQ/Ant+Bundles#AntBundles-rhq%3Aarchive master commit e26efc5c109e10da6418defa48b565c9b0c6097c Author: Jay Shaughnessy <jshaughn> Date: Fri Apr 25 15:34:22 2014 -0400 Add "destinationDir" attribute for the archive targets. Note that it can only be used in conjunction with "exploded=false".
master commit 074e649afda89f314679a0c65676aa41f80f420b Author: Jay Shaughnessy <jshaughn> Date: Tue Apr 29 11:44:04 2014 -0400 - Fix API back-compat issues in DeploymentData constructors - Fix ambiguous constructors issue in DeploymentData when using various null params - Fix some related jdoc - Update our code base to not use deprecated calls in DeploymentProperties and DeploymentData.
Bulk closing of RHQ 4.11 issues, now that RHQ 4.12 is out. If you find an issue with those, please open a new BZ, linking to the old one.