2 Replies Latest reply on Mar 23, 2007 1:36 AM by Paul Gier

    More Mavenization

    Paul Gier Master

      I added most of the remaining maven assemblies. I ran into a couple of questions while creating them.

      Metatype (API) and Spring (impl) only generate one artifact, should these be packaged as metatype-api and spring-impl? Or can they just use the default maven packaging to create a single jar?

      The container sub-project has a lot of parts, is there a way to simplify this? Like having a single SPI artifact for all of this subproject?

      Also, I am planning to remove the ant build scripts from SVN tonight as long as there are no objections.

        • 1. Re: More Mavenization
          Ales Justin Master

           

          "pgier" wrote:

          Metatype (API) and Spring (impl) only generate one artifact, should these be packaged as metatype-api and spring-impl? Or can they just use the default maven packaging to create a single jar?

          What's the difference? Just name?

          "pgier" wrote:

          The container sub-project has a lot of parts, is there a way to simplify this? Like having a single SPI artifact for all of this subproject?

          I think not.
          Since that is what we wanted - fine grained artifacts == use what you need.

          "pgier" wrote:

          Also, I am planning to remove the ant build scripts from SVN tonight as long as there are no objections.

          Np with me, as long as things work.
          What's the deal with QA and MC - regarding microcontainer-head-testsuite?

          • 2. Re: More Mavenization
            Paul Gier Master

             

            "alesj" wrote:

            Np with me, as long as things work.
            What's the deal with QA and MC - regarding microcontainer-head-testsuite?


            Just let me know if something breaks, and I will try to fix it as soon as possible :)