Prior to 2.3.1, our release process used the names uimaj and uima-as to refer to a common parent-pom for these projects, as well as for being poms which served to "aggregate" the multi-module build (that is, these poms had <modules> sections referring to all the submodules).
When I was doing the maven align work, I split these two purposes - so there was (now) one common parent-pom, and (several) aggregation poms; the aggregation poms allowed building parts of these multi-module projects, together. The original uimaj and uima-as projects have remained, but are currently unused. One user tried a "conventional" way of building things, by assuming the uimaj project was an appropriate target for "mvn install". We could make this so, making it an aggregator pom, essentially copying the aggregate-uimaj pom to this as a new name. I think this would make our project more "conventional", and would therefore be a good thing. If others agree, I'll make this change, and also update the docs (which now say to use the aggregate-uimaj project to build all the modules of that, etc.). Other opinions? -Marshall
