8 Replies Latest reply on Mar 31, 2008 8:41 AM by dimitris

    Putting MC artifacts to our maven repo

    alesj

      What's the easiest way to push these new releases to our Maven2 repo?
      The instructions here
      - http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenReleaseProcess
      Suggest you do this:


      Perform the release

      Next run the perform step which will checkout the files from the tag, do a build, and deploy the generated artifacts.

      mvn release:perform

      The deployment is done to the local file system (a local checkout of the jboss maven2 repository), so you will need to commit the new files after they are deployed.

      Note that the release process updates your project's pom.xml to change the <version> to the next version. You need to check this updated pom into cvs/SVN.


      The thing is that I've done that, but than later on modified those files. :-(
      Don't ask me why. :-)
      But now I cannot run that again. Some mvn complain again.

      Is there an easier way than plain hand copying from my local repo to fit our global repo?
      What about these maven-metadata.xml files:
      - http://repository.jboss.org/maven2/org/jboss/jboss-mdr/maven-metadata.xml
      Who modifies those in the first place?

        • 1. Re: Putting MC artifacts to our maven repo

           

          "alesj" wrote:

          The thing is that I've done that, but than later on modified those files. :-(
          Don't ask me why. :-)
          But now I cannot run that again. Some mvn complain again.


          Surprisingly enough. :-)

          You can't modify the files AFTERwards, the build/artifacts wouldn't be reproducable.

          If you want to start again, delete the tag from SVN.

          • 2. Re: Putting MC artifacts to our maven repo
            alesj

             

            "adrian@jboss.org" wrote:

            You can't modify the files AFTERwards, the build/artifacts wouldn't be reproducable.

            If you want to start again, delete the tag from SVN.

            What about if I push the one's that are in my local repo?
            Since all the right versions are there.

            • 3. Re: Putting MC artifacts to our maven repo

               

              "alesj" wrote:
              "adrian@jboss.org" wrote:

              You can't modify the files AFTERwards, the build/artifacts wouldn't be reproducable.

              If you want to start again, delete the tag from SVN.

              What about if I push the one's that are in my local repo?
              Since all the right versions are there.


              If you can reproduce them I don't have a problem. They're not GA releases
              so its not like we'll have to support them for very long. :-)

              • 4. Re: Putting MC artifacts to our maven repo
                alesj

                 

                "adrian@jboss.org" wrote:

                If you can reproduce them I don't have a problem. They're not GA releases
                so its not like we'll have to support them for very long. :-)

                What about those maven-metadata.xml* files?
                Are they crucial for things to be in-synch?

                • 5. Re: Putting MC artifacts to our maven repo

                   

                  "alesj" wrote:
                  "adrian@jboss.org" wrote:

                  If you can reproduce them I don't have a problem. They're not GA releases
                  so its not like we'll have to support them for very long. :-)

                  What about those maven-metadata.xml* files?
                  Are they crucial for things to be in-synch?


                  No they just list what is in the repository and which is the current version.

                  If you edit them and don't know how to regenerate the checksums then
                  just delete the check sum file(s).

                  Its the binaries/poms that are important.

                  • 6. Re: Putting MC artifacts to our maven repo
                    dimitris

                    Somewhat related, looking into https://svn.jboss.org/repos/repository.jboss.org/maven2/org/jboss/jboss-common-core/maven-metadata.xml

                    a) I can see version 2.2.3.GA missing. Given this one was used by other components, I conclude the maven-metadata.xml is not necessary?
                    b) Anyone knows if ordering is important?
                    c) What's the meaning of v2.0.5.GA as it is recorded below?

                    After a quick search, I didn't much about the maven-metadata schema.

                    <?xml version="1.0" encoding="UTF-8" ?>
                    <metadata>
                     <groupId>org.jboss</groupId>
                     <artifactId>jboss-common-core</artifactId>
                     <version>2.0.5.GA</version>
                     <versioning>
                     <release>2.2.4.GA</release>
                     <versions>
                     <version>2.0.5.GA</version>
                     <version>2.2.2.GA</version>
                     <version>2.2.1.GA</version>
                     <version>2.2.4.GA</version>
                     </versions>
                     <lastUpdated>20080328111223</lastUpdated>
                     </versioning>
                    </metadata>
                    


                    Another problem I noticed is the moment you are doing the 'mvn release:perform' you need to have checked all the versions of a component, in-order to get access to the maven-metadata.xml, so the new version is correctly added. That means a lot of garbage in your local filesystem, just to do a simple release.

                    • 7. Re: Putting MC artifacts to our maven repo

                      Dimitris,

                      Why are you asking questions about maven/build system on the MC forum? :-)

                      • 8. Re: Putting MC artifacts to our maven repo
                        dimitris

                        I know, I piggybacked on the last answer, sorry :)

                        Moved here:
                        http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140104#4140104