Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-13263

Workspace metadata deployment does not work for AS 6

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 4.0.1.Final
    • 4.0.0.Final
    • server
    • None

    • JBoss AS 6.1.0

    • Hide

      1. Create an AS6 server
      2. Create a dynamic web project
      3. Start AS6
      4. Deploy the web project
      5. Check the console - the project doesn't get deployed - FAIL

      Show
      1. Create an AS6 server 2. Create a dynamic web project 3. Start AS6 4. Deploy the web project 5. Check the console - the project doesn't get deployed - FAIL
    • Release Notes
    • Hide

      Change the deployment to JBoss AS deploy folder or custom.
      1. Double-click server in Server view to open the server editor
      2. Go to Deployment tab
      3. Set deployment settings to either "Use the JBoss deploy folder"

      Show
      Change the deployment to JBoss AS deploy folder or custom. 1. Double-click server in Server view to open the server editor 2. Go to Deployment tab 3. Set deployment settings to either "Use the JBoss deploy folder"
    • Hide
      By default, JBoss Application Server deployment scanners monitor the workspace metadata for applications to deploy. API changes caused duplicate deployment scanners to be created for JBoss Application Server 7. In rectifying this issue, tooling modifications inadvertently caused no deployment scanners to be created for JBoss Application Server 6. As a result, applications selected for deployment on JBoss Application Server 6 failed to deploy. Modifications have been reworked to ensure a deployment scanner is created for JBoss Application Server 6 and, consequently, applications will deploy to JBoss Application Server 6.
      Show
      By default, JBoss Application Server deployment scanners monitor the workspace metadata for applications to deploy. API changes caused duplicate deployment scanners to be created for JBoss Application Server 7. In rectifying this issue, tooling modifications inadvertently caused no deployment scanners to be created for JBoss Application Server 6. As a result, applications selected for deployment on JBoss Application Server 6 failed to deploy. Modifications have been reworked to ensure a deployment scanner is created for JBoss Application Server 6 and, consequently, applications will deploy to JBoss Application Server 6.
    • Documented as Resolved Issue

      When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed.

              manderse@redhat.com Max Andersen
              exd-mmalina Martin Malina
              Michelle Murray Michelle Murray (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: