2 Replies Latest reply on Jan 31, 2007 1:37 PM by David Lloyd

    JBoss configuration build

    David Lloyd Master

      If you run the create.jbpm.server.config ant task in jbpm.3/jboss/configuration, it deletes the whole jboss installation that is located at ${jboss.home}.

      If you set ${jboss.home} to be a non-existant directory, the build fails.

      Why is this directory required to exist if it is only going to be deleted?

        • 1. Re: JBoss configuration build
          Tom Baeyens Master

          maybe it is the parent directory of ${jboss.home} that needs to exist. it's in the parent directory that the jboss zip file is unzipped.

          does the ant script itself give a clue ?

          • 2. Re: JBoss configuration build
            David Lloyd Master

             

            "tom.baeyens@jboss.com" wrote:
            maybe it is the parent directory of ${jboss.home} that needs to exist. it's in the parent directory that the jboss zip file is unzipped.

            does the ant script itself give a clue ?


            In this case, the parent does exist. Looking in depth I think this is the problem:

            <target name="clean.jboss.install" description="deletes the current jboss installation at ${jboss.home}">
             <delete dir="${jboss.home}" />
             </target>


            The problems here are:

            * The will fail on error
            * This task is executed by default - perhaps it is better to fail if the directory exists rather than delete it automatically, and let the user manually delete or rename the directory if it does exist