1 2 Previous Next 20 Replies Latest reply on Feb 9, 2010 10:03 AM by Przemysław Chmielewski

    SVN trunk restructuring for Seam 3.0

    Shane Bryzak Master

      For those of you that like to live on the bleeding edge and use SVN trunk, it is currently undergoing a restructure in preparation for work to begin on Seam 3.0.  As a result of this, the trunk build is currently broken however we are working hard to get it to a stable state ASAP. The latest (somewhat more stable) 2.1 branch can now be found at the following location:


      http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_1/

        • 1. Re: SVN trunk restructuring for Seam 3.0
          Christian Bauer Master

          I've updated the SVN checkout instructions on the Downloads page.

          • 2. Re: SVN trunk restructuring for Seam 3.0
            Dan Allen Master

            Unfortunately, because of how the branches are organized (under community and enterprise folders), you cannot do an svn switch to migrate a working copy to the new location. That's only relevant if you are holding patches against the repository. Your best bet is to run svn diff and the reapply the patch after you check out a fresh copy.


            If anyone knows a better trick, please document it here.

            • 3. Re: SVN trunk restructuring for Seam 3.0
              Tomaz Cerar Master

              Dan,


              svn switch works just fine...


              just ran this in root folder


              svn sw http://anonsvn.jboss.org/repos/seam/branches/community/Seam21/


              and it worked with no problem



              cheers,
              tomaz

              • 5. Re: SVN trunk restructuring for Seam 3.0
                Dan Allen Master

                Ah, it's the --relocate flag that doesn't work. Relocate is a hot replacement of the metadata. I guess it only supports the same repository depth. Switch by itself appears to be able to accommodate any migration (or at least this one).


                Btw, the point of --relocate is to avoid communication with the repository in case any files changed in the interim (basically avoids an implicit update).

                • 6. Re: SVN trunk restructuring for Seam 3.0
                  Nikolay Elenkov Master

                  I realize that the trunk is still being restructured, and this maybe fixed later,
                  but currently the checkout instructions point to the wrong SVN URL:



                  # Anonymous SVN checkout of the 3.0 development branch:
                  svn co http://anonsvn.jboss.org/repos/seam/trunk seam



                  That checks out trunk/, which seems to contain the old 2.1 stuff.
                  To get the new Seam 3.0 stuff, one needs to checkout everything (branches and all).


                  svn co http://anonsvn.jboss.org/repos/seam



                  Shouldn't all trunk code be under trunk/?

                  • 7. Re: SVN trunk restructuring for Seam 3.0
                    Dan Allen Master

                    I've updated the Downloads page to explain how the Seam 3 SVN repository is organized, as it is different from Seam 2. Seam 2 is a organized as a single project (thus one repository), built using Ant. Seam 3 is entirely modular and is divided into multiple repositories (docs, examples, modules, sandbox), each built using Maven 2. In order to get all of Seam 3, you have to check out each repository individually.


                    Don't expect everything to work just yet. If you check it out now, you are part of the process ;)


                    If you are a Maven 2 guru, I encourage you to play with the examples and give me feedback about how I've setup the deployment using the Maven 2 plugins. I am trying to make the examples as clean as possible, quintessential examples of how to use Maven 2.


                    We are also looking for feedback on the m2eclipse plugin. Our understanding is that it is still quite unstable/unreliable. Now that we are using a Maven 2 build, it is essential that this plugin be reliable in the future. Please beat on it and report bugs to the m2eclipse guys. If they don't listen, please contact us (in particular Max) and explain the situation. We need stability!

                    • 8. Re: SVN trunk restructuring for Seam 3.0
                      Nikolay Elenkov Master

                      Dan Allen wrote on Apr 23, 2009 23:18:


                      I've updated the Downloads page to explain how the Seam 3 SVN repository is organized, as it is different from Seam 2. Seam 2 is a organized as a single project (thus one repository), built using Ant. Seam 3 is entirely modular and is divided into multiple repositories (docs, examples, modules, sandbox), each built using Maven 2. In order to get all of Seam 3, you have to check out each repository individually.


                      Thanks. I get the idea now. It is still quite confusing though.


                      repos/seam is now both the repository for Seam2 (with trunk/, branches/, etc.)
                      and contains the repositories for Seam3 (docs/, modules/) etc. If you really want
                      a 'clean slate' for Seam3, there should probably be a repos/seam3 for the new stuff.
                      Just my two cents.



                      If you are a Maven 2 guru, I encourage you to play with the examples and give me feedback about how I've setup the deployment using the Maven 2 plugins. I am trying to make the examples as clean as possible, quintessential examples of how to use Maven 2.


                      Far form a guru, but I use it a fair bit. I'll give it a try. The poms look promising :)



                      We are also looking for feedback on the m2eclipse plugin. Our understanding is that it is still quite unstable/unreliable.


                      I find it quite stable. I have been using it with multimodule projects (
                      both Seam and Spring) and it works pretty well. I gave up on trying to run SeamTests from Eclipse though.
                      But that is not really relevant for Seam3, is it.



                      • 9. Re: SVN trunk restructuring for Seam 3.0
                        Dan Allen Master

                        Thanks. I get the idea now. It is still quite confusing though.


                        It seems that way at first, but it is so much cleaner to have the separation...and you get used to it pretty quickly.



                        repos/seam is now both the repository for Seam2 (with trunk/, branches/, etc.)
                        and contains the repositories for Seam3 (docs/, modules/) etc. If you really want
                        a 'clean slate' for Seam3, there should probably be a repos/seam3 for the new stuff.
                        Just my two cents.


                        Shane just hasn't gotten to it yet. Likely that folder is going to get nuked or relocated to some other URL so that it is out of the way. The real Seam 2 trunk is the 2.1 branch.

                        • 10. Re: SVN trunk restructuring for Seam 3.0
                          Nikolay Elenkov Master

                          Dan Allen wrote on Apr 24, 2009 08:28:



                          Thanks. I get the idea now. It is still quite confusing though.


                          It seems that way at first, but it is so much cleaner to have the separation...and you get used to it pretty quickly.


                          I meant the repository layout is confusing. The separations does make a lot of sense.
                          Does separate repositories imply different release cycles as well?



                          Shane just hasn't gotten to it yet. Likely that folder is going to get nuked or relocated to some other URL so that it is out of the way. The real Seam 2 trunk is the 2.1 branch.


                          I see. I guess I'll wait for things to settle down a bit and see how it looks then.


                          BTW, I'm getting an error when I try to deploy the booking example,
                          but I'll start a new thread for that.

                          • 11. Re: SVN trunk restructuring for Seam 3.0
                            Fabricio Lemos Newbie

                            How do you import the projects into eclipse? I tried Checkout as Maven project from SCM but it did not work well. So I'm doing a simple checkout and using mvn eclipse:eclipse.


                            Did anyone got lucky with m2eclipse-subversion integration?

                            • 12. Re: SVN trunk restructuring for Seam 3.0
                              Clint Popetz Apprentice

                              How do you import the projects into eclipse? I tried Checkout as Maven project from SCM but it did not work well. So I'm doing a simple checkout and using mvn eclipse:eclipse.

                              Did anyone got lucky with m2eclipse-subversion integration?


                              I use mvn eclipse:eclipse, but if you have the seam/modules/trunk checked out, you can do File -> Import -> Maven Projects and point it at that root to get a set of m2eclipse projects.

                              • 13. Re: SVN trunk restructuring for Seam 3.0
                                Dan Allen Master

                                How do you import the projects into eclipse? I tried Checkout as Maven project from SCM but it did not work well. So I'm doing a simple checkout and using mvn eclipse:eclipse.

                                Did anyone got lucky with m2eclipse-subversion integration?


                                Last week I finally got a chance to give the m2eclipse plugin a try and managed to get all the Web Beans and Seam artifacts setup pretty quickly. I now strongly recommend the use of m2eclipse with the Seam project. Overall it does a pretty good job at managing the Maven 2 projects.


                                I'm in the process of preparing some instructions for using mvn eclipse:m2eclipse to get the projects created so Eclipse can import them w/o having to use the wizard. Though using the m2eclipse import wizard works well too.


                                I'm also discouraging the use of mvn eclipse:eclipse because my feeling is that it is very hackish. It hurts Eclipse not to know that it is dealing with a Maven 2 project, which is why before using m2eclipse I was using NetBeans.


                                As for checking out from SCM, I always checkout from the commandline. Frankly, I don't trust an IDE to do that for me...so I can't help you there other than to recommend checking out the project externally and then pointing Eclipse at the working copy.

                                • 14. Re: SVN trunk restructuring for Seam 3.0
                                  Fabricio Lemos Newbie

                                  I ended up using the import that Popetz told about. It gave me the same errors, but, after I called Maven - Update Project Configuration, it starts working. After I figured it out I could checkout Web Bean through the SCM integration.


                                  m2eclipse is a little unstable but have really nice features. Workspace resolution and Source Download are a must have.


                                  Thank you

                                  1 2 Previous Next