On 3/4/2013 2:47 AM, Tommaso Teofili wrote: > Hi all, > > I'm hoping to have some time this week to work on the release of (some of) > the addons. Nice! > I noticed all of the modules depend on the uima-addons-parent which is > basically just a reactor pom (mostly useful to aggregate modules), the only > important bits which may affect the release is the jiraVersion. > Since we planned to release on a per module basis maybe we can create > different "jira releases" on Jira and write them inside each module's pom > so that for Solrcas 2.3.2 we create a Jira release in Jira and write down > such Jira version in the Solrcas pom and release with that. +1 > > Also we would need to remove the current 2.3.1 (aggregate) addons Jira > version from the uima-addons-parent Probably don't need to fiddle with this, just override it in the individual add-on project's pom?
> and release a uima-addons-parent 2.3.2 > which doesn't have such information inside so that it doesn't affect its > modules. I think this may not be needed, because I believe (?) that a pom's setting of a property will override any setting that might be there from any of its parent's poms. Did I misunderstand something, or am I mistaken on how maven overrides work here? -Marshall
