1 Reply Latest reply on Apr 11, 2007 4:35 AM by Carlo de Wolf

    Break up jboss common?

    Paul Gier Master

      Would it be a problem to break up jboss common into separate projects? Basically it would be the same as it is now, except with no build directory, and the module poms would extend directly from the jboss-parent.

      I brought up the idea of creating an aggregate artifact for the common components, but there didn't seem to be any need for this, so I'm wondering if the build aggregate folder is even necessary.

      The advantages would be
      You wouldn't need to check out the build directory (and the rest of the svn trunks structure) to build a single component.
      Releases could be done for each component as needed, instead of all of common together.
      The build folder could be removed providing a little bit simpler directory structure.