Announcement Announcement Module
Collapse
No announcement yet.
Maven2ized site alpha (with javadocs) Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Maven2ized site alpha (with javadocs)

    I am in the process of writing a script to maven2ize spring-rich.
    I am already able to compile spring rich already and let maven generate some stuff, such as javadocs for example.
    Next weekend I 'll clean it up some more and do petclinic too.
    After that I 'll share the files to actually maven2ize it, starting making snapshot's, talk to Ollie, Larry and the other developers if they 'd actually want to take it in or not.
    But for now I already uploaded the maven generated sites to my website.
    However I haven't gotten a chance to merge them yet.
    Also the changelogs don't show anything yet (fixable later).

    http://users.telenet.be/geoffrey/Del...nt/site/parent (general info)
    http://users.telenet.be/geoffrey/Del...ient/site/core (javadocs)
    http://users.telenet.be/geoffrey/Del...t/site/sandbox (javadocs)
    http://users.telenet.be/geoffrey/Del...site/resources

    Once again, it's not finished by far yet, so don't base your decision on it yet wheter or not you like maven2 over ANT...

  • #2
    Links to wiki & jira are messed up, but fixed locally.

    Comment


    • #3
      I am actually not a developer (yet?), that's wrong too in the project team page.

      Comment


      • #4
        You'd probably be best off bringing this up on the Spring Rich Developers' list.

        Comment


        • #5
          Originally posted by Ben Alex
          You'd probably be best off bringing this up on the Spring Rich Developers' list.
          Already did

          Ben,

          Some of the dependencies spring-richtclient needs aren't in ibiblio, so I 've made a remote repository in my ${basedir} (untill I can put that online somewhere). Have you had this problem in acegi and how did you fix it?
          I 've maven2ized glazedlist (1.5.0 will be on ibiblio soon but breaks spring-richclient), but many others are still to do, including the spring-binding snapshot etc.

          Is Spring (besides acegi) going the maven2 way (I noticed some project.xml's in their sources)?
          Does spring have any conventions on their maven2 repositories?

          Comment


          • #6
            Hi Geoffrey

            Way to go! Excellent move.

            I definitely recommend the addition of findbugs, pmd, checkstyle, simian and cobertura, and, of course, qalab! (http://qalab.sourceforge.net). as well as links to the jars that are built.

            My company launched this little open-source project that keeps track of the number of QA issues detected by pmd/findbugs/simian/cobertura/checstyle over time. We're working on an m2 plugin at the moment but have noticed that the cobertura plug in is badly broken...

            Best regards

            Benoit

            Comment


            • #7
              In maven 2, the checkstyle and pmd report didn't work out-of-the-box. I 'll look into and add them and findbugs, etc working after petclinic.

              qalab looks nice, have you talked to Brett Porter on the maven user list about it, especially about the shared functionality with the maven dashboard plugin?

              Comment


              • #8
                if you need any help with the project dependencies, let me know. I setup a maven2 repository with spring-rcp snapshots that i've been maintaining on my own for quite a while.

                http://maven.codecrate.com/spring-rcp/

                Maven2 is great, and it would be a *huge* deal for spring-rcp to start publishing public snapshots.

                Comment


                • #9
                  I also think that spring-rcp would *highly* benefit from componatizing it's codebase. it should be modularized according to function:
                  * binding
                  * forms
                  * core
                  * etc

                  Maven2 makes this a snap, and it would greatly help pull new developers in if they didn't have to know "all of spring-rcp". just look at jgoodies (forms, looks, binding, etc)...

                  Comment


                  • #10
                    Originally posted by wireframe
                    I also think that spring-rcp would *highly* benefit from componatizing it's codebase. it should be modularized according to function:
                    * binding
                    * forms
                    * core
                    * etc

                    Maven2 makes this a snap, and it would greatly help pull new developers in if they didn't have to know "all of spring-rcp". just look at jgoodies (forms, looks, binding, etc)...
                    I most definitly agree.
                    Spring itself goes far in this too, like hibernate2 and hibernate3 seperated.
                    I am already splitting up petclinic in common, server, client and standalone for the maven2ization.
                    Problem with the springrich is I don't dare do it now, as I have no idea where a good breakline would be to avoid cyclic dependencies. I 'll make some modules like binding, form, tiger (compiling with 1.5) and put everything in "core" for now, so the others can worry about migrating stuff out.

                    Tiger depends on form, binding.
                    Form depends on binding.
                    Binding depends on core.
                    Any other modules that would be handy?

                    Comment


                    • #11
                      I think this is a great start, and you've got to start somewhere. Once these smaller modules are in place, it should become clear if there are any other componets that could be pulled out as well.

                      I also think that this modularization could be a big help for the developers that run the spring-rcp project. There's been a lot of talk lately about needing a strong lead developer to take hold of the project, but it would be much more effective to have multiple smaller projects with multiple stake holders. One single "dictator" for the project is not going to be effective. Spring-RCP is a lot like the main springframework. There are multiple components and there's no single developer that owns or knows the entire project. it's more of a loose collaboration of developers, each with their own expertise.

                      I'm no spring-rcp expert, but if the project was componatized, I would feel much more comfortable digging in and contributing to the pieces that I use and enhance the most...

                      Comment


                      • #12
                        If any componentization was to occur, it would be good to do it along dependencies line as Spring RC is quite "heavy" when it comes to the extra required jars... like aopappliance/jxr/caucho/swingx...

                        Thanks!

                        Comment


                        • #13
                          Originally posted by wireframe
                          There's been a lot of talk lately about needing a strong lead developer to take hold of the project, but it would be much more effective to have multiple smaller projects with multiple stake holders. One single "dictator" for the project is not going to be effective.
                          I believe we need an overall strong leader (and don't see anyone doing a better job then Ollie at this time), but deviding reponsibility more would be a good idea.
                          If the maven2ization would be accepted, I 'd gladly take reponsiblity for keeping the build process consistent.
                          The rule "no part of the code is sacred" should be changed into "no part of the code is sacred, but the module's leader will warn you to keep the code consistent if you mess up".

                          Comment


                          • #14
                            Originally posted by benoitx
                            If any componentization was to occur, it would be good to do it along dependencies line as Spring RC is quite "heavy" when it comes to the extra required jars... like aopappliance/jxr/caucho/swingx...

                            Thanks!
                            The maven2ization makes full use of maven2's dependency properties (transitive, required/optional, etc) and every dependency is documented on the maven generated site.

                            Comment


                            • #15
                              Indeed it is very useful information but what I'm getting at is that by looking at the Spring RC CORE:
                              http://users.telenet.be/geoffrey/Del...endencies.html

                              The transitive dependencies are rather scary! A massive amount of them and... in my project, I do not need half of them... So my suggestion would be to release different jars and introduce new dependencies only when absolutely required... (like encache only when one uses Hibernate on the client!) etc

                              My 0.02-worth suggestion...

                              Benoit

                              Comment

                              Working...
                              X