7 Replies Latest reply on Mar 7, 2008 12:41 PM by Paul Gier

    maven-buildmagic-thirdparty-plugin Enhancements to put in re

    Andrew Rubinger Master

      As it currently stands, the jboss-deploy-plugin (now the maven-buildmagic-thirdparty-plugin - love the clearer name BTW), copies artifacts from "mvn deploy" into the path specified by "jboss.repository.root", intended to be the target for the local WC of https://svn.jboss.org/repos/repository.jboss.com.

      Which is fine for local dev, but for QA environments where we don't have access to do an "svn ci" to the thirdparty repo after "mvn deploy", there's currently no way to get the artifacts into 3rdparty via a cron'd Hudson run.

      So the end result is that we must manually deploy artifacts each night such that they're kept current for AS builds, and stuff easily falls out of sync. QA asked me about this today specifically for the EJB3 Aggregator run.

      How can we change this? Some ideas:

      * Enhance maven-buildmagic-thirdparty-plugin to automatically invoke appropriate SVN actions (either via Process to 'svn' or Java SVN lib)

      * Enhance maven-buildmagic-thirdparty-plugin to WebDAV the necessary artifacts and descriptors artifacts, overwriting what's there (Apache Slide, maybe). This solution is simpler but won't account for version control (in SVN anyway, I'm not sure what's hooked up under the DAV protocol supporting that location now).

      * Do nothing; Paul will be done with making 3rdparty go the way of the Dodo soon enough and everything will be in the Maven2 repos.

      Thoughts?

      S,
      ALR

        • 1. Re: maven-buildmagic-thirdparty-plugin Enhancements to put i
          Paul Gier Master

           

          "ALRubinger" wrote:

          How can we change this? Some ideas:

          * Enhance maven-buildmagic-thirdparty-plugin to automatically invoke appropriate SVN actions (either via Process to 'svn' or Java SVN lib)

          * Enhance maven-buildmagic-thirdparty-plugin to WebDAV the necessary artifacts and descriptors artifacts, overwriting what's there (Apache Slide, maybe). This solution is simpler but won't account for version control (in SVN anyway, I'm not sure what's hooked up under the DAV protocol supporting that location now).

          * Do nothing; Paul will be done with making 3rdparty go the way of the Dodo soon enough and everything will be in the Maven2 repos.

          Thoughts?

          S,
          ALR


          I'm not sure how the WebDAV option would work because we don't currently have a snapshot repository for thirdparty stuff. Our thirdparty snapshots are handled the same as releases in the thirdparty repo by checking into svn. So we would need a new repository for that.

          So I think option 1 or 3 makes more sense. I guess it's a question of how urgent it is. Is it mainly ejb builds that need to be uploaded regularly to the thirdparty repo?




          • 2. Re: maven-buildmagic-thirdparty-plugin Enhancements to put i
            Andrew Rubinger Master

             

            "pgier" wrote:
            I'm not sure how the WebDAV option would work because we don't currently have a snapshot repository for thirdparty stuff. Our thirdparty snapshots are handled the same as releases in the thirdparty repo by checking into svn. So we would need a new repository for that.


            Oh, I was expecting to be able to use repository.jboss.org and write both snapshots and releases right in there.

            dav:/> pwd
            Current collection is `https://repository.jboss.org/'.
            dav:/> ls
            Listing collection `/': succeeded.
            Coll: > admin 0 Dec 31 1969
            Coll: > labs 0 Mar 7 10:39
             > .svnignore 36 May 12 2005
             > remove-svn.sh 164 May 12 2005
             > set-ignore.sh 246 May 12 2005


            ...guess not?

            "pgier" wrote:
            So I think option 1 or 3 makes more sense. I guess it's a question of how urgent it is. Is it mainly ejb builds that need to be uploaded regularly to the thirdparty repo?


            That I'm aware of, just EJB3, but technically it's any Maven-based project that's imported as a 3rdparty lib. If this is a week or two, that's cool, I can just take care of it.

            So sure, if we're going to be trashing 3rdparty soon, the problems mentioned here become conveniently rectified implicitly. :)

            S,
            ALR

            • 3. Re: maven-buildmagic-thirdparty-plugin Enhancements to put i
              Paul Gier Master

              Ha, the dav url to repository.jboss.org points to the jboss labs svn repo? That's weird, I wonder how that happened.

              So can you commit to svn over webdav? I didn't know that could be done. But if that works, it could be a solution to our current issue of having to check out the whole repository before committing.



              • 4. Re: maven-buildmagic-thirdparty-plugin Enhancements to put i
                Andrew Rubinger Master

                Yep, looks like we found some more work for my buddy Blake @ HelpDesk. :)

                I wasn't even thinking of committing to svn via WebDAV. I'd thought that committing to SVN put the files in a repo, where some cron'd process then copied the current revision over to repository.jboss.org...so was looking to bypass the whole SVN part of the equation and just write directly using DAV.

                More evidence mounting to be rid of 3rdparty for once and all. :)

                In the meantime, I think option 3 makes the most sense. I can live with a few minutes of manual tasks in my workflow each day to avoid a few hours of work on a feature that'll be useless once your (Paul) stuff is done.

                S,
                ALR

                • 5. Re: maven-buildmagic-thirdparty-plugin Enhancements to put i
                  David Lloyd Master

                   

                  "pgier" wrote:
                  So can you commit to svn over webdav? I didn't know that could be done. But if that works, it could be a solution to our current issue of having to check out the whole repository before committing.


                  Why do you have to check out the whole repository before committing?

                  • 6. Re: maven-buildmagic-thirdparty-plugin Enhancements to put i
                    Andrew Rubinger Master

                     

                    "david.lloyd@jboss.com" wrote:
                    Why do you have to check out the whole repository before committing?


                    I don't; I get around this by doing a non-recursive checkout of the parent folder to which I want to add.

                    S,
                    ALR

                    • 7. Re: maven-buildmagic-thirdparty-plugin Enhancements to put i
                      Paul Gier Master

                       

                      "david.lloyd@jboss.com" wrote:
                      "pgier" wrote:
                      So can you commit to svn over webdav? I didn't know that could be done. But if that works, it could be a solution to our current issue of having to check out the whole repository before committing.


                      Why do you have to check out the whole repository before committing?


                      Technically I don't have to check out the whole repo, I could just commit to the folder I want like Andrew said. But since I end up committing stuff all over the place in no predictable order, it ends up easier to just check out the whole thing. If there was a way I could send commits with my username without checking out first, it would make things a little more convenient.