5 Replies Latest reply on Aug 29, 2005 12:42 PM by ruel.loehr

    JBoss Thirdparty Build Port to Head Branch

      One of the issues I encountered when working in the 4.0 branch was that the testsuite/build.xml references a libraries.xml and modules.xml instead of the libraries.ent and modules.ent files.

      I would like to perform the same change as in the 4.0 branch which involves changing the testsuite to use the .ent versions of these files and removing the xml versions from the repository.

      Are there any issues with doing this in head?

      Ruel Loehr
      JBoss QA

        • 1. Re: JBoss Thirdparty Build Port to Head Branch

          No issue, go ahead.

          • 2. Re: JBoss Thirdparty Build Port to Head Branch
            starksm64

            Certainly since the libraries.ent is generated, there should be only one used everywhere. The only reason the xml versions were introduced was to prototype the ant 1.6 features including its import mechanism which required a different format.

            • 3. Re: JBoss Thirdparty Build Port to Head Branch

              Working in a branch off of head I have ported the thirdparty download to head. I am shooting for releasing this and the accompanying cruisecontrol changes early next week.

              mkdir test
              cd test
              cvs co -r REPO_BRANCH_HEAD jboss-head.x
              cd jboss-head/build
              ./build.sh


              When creating the module that does not include the thirdparty I followed the same naming schema as we used in 4.0. Does this still hold as adequate?

              Ruel Loehr
              JBoss QA

              • 4. Re: JBoss Thirdparty Build Port to Head Branch
                starksm64

                No, as there is no reason to keep jboss-head the same since this is the pure development branch. There is no reason to be able to build an old tagged release of jboss-head. Just send out a warning email to dev and ask if someone has a workspace in a state that should delay the change. The only thing I can see being an issue was needing to update thirdparty to test uncommitted changes.

                • 5. Re: JBoss Thirdparty Build Port to Head Branch

                  The changes to head have been deployed.

                  Checkout to a clean directory

                  cvs co jboss-head
                  cd jboss-head
                  cd build
                  ./build.sh


                  I have made an announcement on the dev list and will update the eclipse .classpath files.

                  Please let me know if you encounter any issues.