On Thu, Nov 18, 2010 at 10:26 AM, Marshall Schor <[email protected]> wrote: > The current build approach has some issues. A major one is that the trunk is > not currently buildable (because uimaj projects have a parent pom dependency > at > version 1 which is only in the staging area, and not really released yet).
As I understand it, releasing the parent pom will immediately solve most if not all current build problems. > After some iterations and discussions with colleagues, here's the next > "improvement" which I think will fix these problems. The main idea is to make > the "main" aggregator project for each multi-module build (e.g., the "uimaj" > project for the uimaj SDK) also be a parent-pom for all those modules in the > multi-module build, as is conventional Maven practice. And this step will further reduce the need to make updates to the parent pom. > Some scenarios, assuming we've voted and released the parent-pom tooling. These all look good to me. > I'd like to do this change. It would involve: > > 1) voting out the already existing parent-pom-1 and uima-build-resources-1 > artifacts so they could be put in Maven central, and referred to. > 2) creating the uimaj project as the overall aggregator and parent-pom of the > uimaj projects, and having it depend on the released version one of the > projet-wide pom +1
