3 Replies Latest reply on Jan 22, 2006 1:06 PM by Marshall Marshall

    Share server configurations among developers using JBoss IDE

    Weiping Yang Newbie

      I would like to place all server configurations under CVS (check in/out under Eclipse IDE) so that the configurations can be shared among developers.

      The ideal setup would be to have both source code and server configuration under CVS so that any body can just check out the source project and configuration into local environment (with Eclipse and JBoss installed of course) and ready to code/debug/test without worrying about the configuration files

      My initial thought would be to clone the ${JBOSS_INSTALL}/server/default folder under a totally separated folder and place this folder as part of a project under JBoss IDE.

      Then, question is how to make JBoss IDE recognize this folder and deploy the apps into it?

      Any suggestions would be appreciated

        • 1. Re: Share server configurations among developers using JBoss
          Marshall Marshall Expert

          You can configure JBossIDE to use your own custom filesystem copy deployment targets:

          1) Go to Window > Preferences > JBoss-IDE > Deployer.
          2) On the bottom half of the page there is a list labeled "List of user-defined targets"
          3) Click the Add button next to that list and it will add the directory you select as custom deployment target for use in the "Deploy To" menu.

          • 2. Re: Share server configurations among developers using JBoss
            Weiping Yang Newbie

            Thanks for your reply

            I did that. I created another directory c:\proj\vapdeploy and I was able to deploy the ear to the directory.

            I also changed the jboss-service.xml to scan that directory as follows:

            file:/c:/proj/vapdeploy/


            However, I got this error when starting the server

            09:51:06,530 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

            --- Packages waiting for a deployer ---
            org.jboss.deployment.DeploymentInfo@4b297d88 { url=file:/c:/proj/vapdeploy/FiboApp.ear }
            deployer: null
            status: null
            state: INIT_WAITING_DEPLOYER
            watch: file:/c:/proj/vapdeploy/FiboApp.ear
            altDD: null
            lastDeployed: 1137945066530
            lastModified: 1137945066515
            mbeans:

            --- Incompletely deployed packages ---
            org.jboss.deployment.DeploymentInfo@4b297d88 { url=file:/c:/proj/vapdeploy/FiboApp.ear }
            deployer: null
            status: null
            state: INIT_WAITING_DEPLOYER
            watch: file:/c:/proj/vapdeploy/FiboApp.ear
            altDD: null
            lastDeployed: 1137945066530
            lastModified: 1137945066515
            mbeans:

            I guess my question is once you deploy the file to the directory, how do you direct JBoss to look for the ear files and actually deploy it to the server?

            Thanks for your assistance

            Weiping





            "mculpepper@jboss.com" wrote:
            You can configure JBossIDE to use your own custom filesystem copy deployment targets:

            1) Go to Window > Preferences > JBoss-IDE > Deployer.
            2) On the bottom half of the page there is a list labeled "List of user-defined targets"
            3) Click the Add button next to that list and it will add the directory you select as custom deployment target for use in the "Deploy To" menu.


            • 3. Re: Share server configurations among developers using JBoss
              Marshall Marshall Expert

              FYI, This is a general JBoss usage question, and should be asked in the JBoss user forums in the future.

              That being said, you'll need to go into conf/jboss-service.xml and find the section that looks like this:

              <mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
              


              Once you're there, scroll down until you see the "URLs" attribute:
              <attribute name="URLs">
               deploy/
              </attribute>
              


              Add a comma to the end of "deploy/" and add your directory after the comma.