Should we upgrade all the bundles to include the compliance attribute in JBoss ON?

Solution Verified - Updated -

Issue

  • The attribute compliance is now mandatory, should we have to upgrade all the bundles?
  • Could we force the default value of the compliance attribute if it is not present in the bundle?
  • Should we upgrade all the bundles to include the compliance attribute in JBoss ON?
  • Attempt to upload the bundle with the recipe file:
<?xml version="1.0"?> <project name="ClusterWebApp" default="main" xmlns:rhq="antlib:org.rhq.bundle"> 
    <rhq:bundle name="ClusterWebApp" version="1.1" description="test ClusterWebApp bundle"> 
        <rhq:deployment-unit name="ClusterWebApp"> 
            <rhq:file name="ClusterWebApp.war" /> 
        </rhq:deployment-unit> 
    </rhq:bundle> 
    <target name="main"/> 
</project>

is rejected with the message:

Failed to upload bundle distribution file : java.lang.Exception:Failed to parse the bundle Ant script.
org.rhq.bundle.ant.InvalidBuildFileException:The deployment unit must specifically declare compliance mode of the destination directory.

  • manageRootDir="false" in version 3.1 was replaced with compliance="filesAndDirectories" in version 3.3. Is version 3.3 backward compatible or do I have to update all of my existing bundles before I can deploy them?

Environment

  • Red Hat JBoss Operations Network (JON) 3.2.0, 3.2.1, 3.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.