2 Replies Latest reply on Mar 12, 2007 9:22 AM by Paul Gier

    Common assembly and module folder names

    Paul Gier Master

      Would it be useful to have a release of common that combines the modules into a single jar? Other projects that depend on common could then just point to the combined jar in the repository instead of depending on the individual modules directly.

      I'd also like to change the names of the common projects module folders so that they match the maven artifactIds. This will make assembly a little easier if we do want to have a combined jar.

      So I would change the folder names to
      common
      |-jboss-common-core
      |-jboss-common-logging-jdk
      |-jboss-common-logging-spi
      `-jboss-common-logging-log4j

      And the artifactIds in the repositories will match these names.

        • 1. Re: Common assembly and module folder names
          Scott Stark Master

          I suppose. I guess the only issue is what are we going to do if we do make minor independent releases of the underlying projects. Say we do a 2.0.1 release of common, and then do 2.0.2 and 2.0.3 release of jboss-common-logging-log4j for whatever reason.

          Are there going to be jboss-common-2.0.2 and 2.0.3 releases as well, or will we release 2.0.2 and 2.0.3 versions of everything even without changes?

          We just need a plan on how this is going to be managed.

          • 2. Re: Common assembly and module folder names
            Paul Gier Master

            We will still be able to do independent releases. So we could do a 2.0.1 release of the combined common, and then do a 2.0.2 release of just common-logging-log4j, and then 2.0.2 of just common-core, etc.

            Or we could have just the separate releases. Is it even useful to have a combined jar file in addition to the individual releases? Maybe it would be better to just keep the releases separate?