5 Replies Latest reply on Mar 15, 2006 2:07 AM by Tom Baeyens

    Subversion repository plan?

    Stacey Vetzal Newbie

      Hi All,

      Will jBPM be moving to the Subversion repository any time soon? I've noticed some reference to a migration at JBoss towards Maven, which I think is a fabulous idea - above all it will help contributers and observers more easily visualize how the projects are structured.

      I'd like to contribute some things, but they all use a Maven build. Subversion will be critical to the hierarchial project structure (CVS is inherently flat) that Maven will demand.

        • 1. Re: Subversion repository plan?
          Jim Rigsbee Newbie

           

          "svetzal" wrote:
          Subversion will be critical to the hierarchial project structure (CVS is inherently flat) that Maven will demand.


          I do not agree. I currently use CVS with Maven and have no issues. The chief benefit of SVN is that it versions folder structures as well. This is not necessary to have a successful Maven implementation.

          I think that SVN is a good thing. But we don't need to hold up a Maven move for that.

          Regards, Jim

          • 2. Re: Subversion repository plan?
            Stacey Vetzal Newbie

            I agree that it is not necessary to hold up a Maven build port strictly for the sake of Subversion. I did not intend to imply that Subversion was required, simply that it would make things easier and more clear for us.

            In my experience CVS's strict project structure (ie. all projects exist strictly off the root of the repository) leads to a tremendous number of projects when you bring Maven into the mix. And take a look at the already massive number of projects in the JBoss CVS repository.

            Now, take a look at jBPM - we have the WAR, the SAR, and the sample workflow. In Maven, naturally these become 3 sub-projects.

            So now instead of someone checking out "jbpm.3", they have to check out 3 distinct CVS projects just to build the full suite. It won't be immediately obvious looking at the repository which projects you need, and if we want to use POM inheritance (which we do) it's not immediately apparent which of the 3 projects contains the master POM.

            ie.

            jbpm
            +--webtool
            +--service
            +--sample_workflow

            With Subversion, you can check out from 1 point, and the 3 subprojects will follow along, keeping a nice hierarchial folder structure where it's obvious where the master POM and sub-projects are, and allowing the MultiProject Maven plugin to work nicely.

            Now, honestly I can't recall trying to check a structure like this into CVS. It's possible that my brain just can't get past the (Maven)Project <-> (CVS)Project mismatch. Have you worked with Maven / CVS in this manner?

            • 3. Re: Subversion repository plan?
              Jim Rigsbee Newbie

              Yes, I have done this with CVS. We would check out a major component like jbpm.3 and all of its baby projects would fall under this directory. Sub-component dependencies need to be within the same CVS module.

              As Tom has mentioned in previous posts, this will involve quite a bit of restructure from what we have now. See http://jboss.com/index.html?module=bb&op=viewtopic&t=77833 for the entire discussion thread.

              Regards, Jim

              • 4. Re: Subversion repository plan?
                Stacey Vetzal Newbie

                 

                "jimrigsbee" wrote:
                As Tom has mentioned in previous posts, this will involve quite a bit of restructure from what we have now. See http://jboss.com/index.html?module=bb&op=viewtopic&t=77833 for the entire discussion thread.


                Awesome - thanks for the link Jim, this gives me a good idea what you guys are thinking. I'll remember your comment about success with subprojects in a CVS project.

                • 5. Re: Subversion repository plan?
                  Tom Baeyens Master

                  one large cvs module containing all the subprojects was indeed the idea. if you have any idea of that giving difficulties let me know.

                  i'm waiting for the decision on jboss build. they will probably switch to maven as well. (alternatively they stick to a custom jboss build system that also includes a repository) i planned to follow their decision, but after reading this discussion, i'm tempted to go for maven anyway.

                  i have some more work to finish before i can start on the restructuring: mainly web app redesign.

                  regards, tom.