1 Reply Latest reply on Sep 19, 2005 2:20 PM by Ruel Loehr

    Moving src to Subversion?

    Charles Crouch Expert

      Some of the admin-console developers would benefit tremendously if it was possible to commit code to the admin-console over plain HTTPS. Its my understanding that this is not possible when using CVS. It is however feasible if the source was stored in a Subversion repository. So I would like to hear comments from the QA/build team, or anyone else for that matter, on the implications of moving the admin-console source to a SVN repo.

      Things I'm thinking about:

      - Would the build files we use still get the same care and attention they currently get if the src was in its own SVN repo? For instance the changes to support the repository.jboss.com are great and we'd like to continue benefitting from changes like this in the future.

      - How could we include a binary version of the admin-console in the src checkout of JBossAS, via repository.jboss.com?

      - The admin-console is not currently part of the regular JBossAS build, though it is included in the Eclipse project set. Eventually I would have liked it to be part of the build, but moving to SVN would prevent that. What's the best way to mimic the compile time checking that we'd get if we were part of the main build? I'm thinking testsuite tests for the areas of JBossAS functionality which the admin-console depends on?

      - Once the admin-console is sufficiently functional, stable and tested it will be bundled into the AS distribution. Would being in our own SVN repo impact this, I'm thinking not.

        • 1. Re: Moving src to Subversion?
          Ruel Loehr Novice

           

          Would the build files we use still get the same care and attention they currently get if the src was in its own SVN repo? For instance the changes to support the repository.jboss.com are great and we'd like to continue benefitting from changes like this in the future.


          In general, when a project moves to its own as you are describing, (e.g. JBoss Cache) they take care of their build files. However, this certainly doesn't leave you out in the cold. Any upgrades to build systems will be available for all projects. It may take a little more work to integrate changes, but I foresee no problems.

          - How could we include a binary version of the admin-console in the src checkout of JBossAS, via repository.jboss.com?


          Not a problem at all. Instructions for repository maintenance can be found here and I am always available to help. http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBuild

          - The admin-console is not currently part of the regular JBossAS build, though it is included in the Eclipse project set. Eventually I would have liked it to be part of the build, but moving to SVN would prevent that. What's the best way to mimic the compile time checking that we'd get if we were part of the main build? I'm thinking testsuite tests for the areas of JBossAS functionality which the admin-console depends on?

          This gets a little tricky. What you have described so far is a standalone project. If this is true grabbing you will be grabbing all of your dependencies as binaries from the repository. We must ensure that everything you need is indeed available as a binary. A quick glance at the buildfile shows that you include the classpath for j2ee, j2se and varia. We'll have to figure out how to handle this. As far as testing, yes, some type of testsuite tests for the functionality you depend on will be in order.

          - Once the admin-console is sufficiently functional, stable and tested it will be bundled into the AS distribution. Would being in our own SVN repo impact this, I'm thinking no

          You would simply include the admin-console jar in the appopriate spot of JBossAS