5 Replies Latest reply on Apr 3, 2008 2:28 PM by Paul Gier

    Maven release artifacts

    Heiko Braun Master

      In order to simplify integration with AS 5, it would be helpful to create maven artifacts of our binaries that follow a naming convention. Currently the only artifacts that's manually being released to the repo is jbossws-spi (org.jboss.ws:jbossws-spi:jar)

        • 1. Re: Maven release artifacts
          Heiko Braun Master

          This leads to the question if we want to migrate the build to maven or simply add maven release capabilities to it, which is probably easier but may cause issue in the long run, when more and more project migrate. Maybe there is a partly solution? Like brining in Ivy for dependency management? Basically I see the only benefit I see is leveraging maven repositories. We need to be able to publish to and retrieve from a maven repository.

          • 2. Re: Maven release artifacts
            Richard Opalka Master

             

            "heiko.braun@jboss.com" wrote:
            This leads to the question if we want to migrate the build to maven or simply add maven release capabilities to it, which is probably easier but may cause issue in the long run, when more and more project migrate. Maybe there is a partly solution? Like brining in Ivy for dependency management? Basically I see the only benefit I see is leveraging maven repositories. We need to be able to publish to and retrieve from a maven repository.


            I'm not a Maven fan and I don't believe in Maven + AS future, see:

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

            So I'm saying don't migrate to maven builds instead of ant builds.

            • 3. Re: Maven release artifacts
              Heiko Braun Master

              If maven will oppose so many problem it will render itself useless anyway. But until then we have to face it: AS has chosen to use maven and we need to deal with integration. Which basically means leveraging the maven repositories.

              I am looking for a smart way to hook into that without having to migrate our build completely.

              • 4. Re: Maven release artifacts
                Richard Opalka Master

                 

                "heiko.braun@jboss.com" wrote:
                If maven will oppose so many problem it will render itself useless anyway.

                Yes, let's let it to stay the test of time ;)
                "heiko.braun@jboss.com" wrote:
                I am looking for a smart way to hook into that without having to migrate our build completely.

                I agree. We have to deal with the integration issue. I would do it in the way we do it now in our spy, just release it to local maven repository and force developer to commit it there manually ;)

                • 5. Re: Maven release artifacts
                  Paul Gier Master

                   

                  "richard.opalka@jboss.com" wrote:
                  "heiko.braun@jboss.com" wrote:
                  I am looking for a smart way to hook into that without having to migrate our build completely.

                  I agree. We have to deal with the integration issue. I would do it in the way we do it now in our spy, just release it to local maven repository and force developer to commit it there manually ;)


                  Just wanted to add that this is currently the only way to deploy to the maven releases repository (i.e. deploy locally and then commit to svn).
                  This page has some information about how to commit to the maven repository (http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenReleaseRepository)

                  Please use the maven deploy plugin or the ant tasks when deploying to the repository, so that the correct metadata is generated.