one more thing I noticed, the apache-release profile is defined inside uima-addons reactor pom which shouldn't be used for individual release of artifacts (it's been used for the whole uima-addons package, e.g. for uima-addons 2.3.1) so I'd propose to move the apache-release profile to uima-addons-parent (2.3.2-SNAPSHOT), release that and then release each individual modules with that new version of the uima-addons-parent. Without that we'd have to duplicate such information in each addon's pom.
Any objections? Tommaso 2013/3/6 Marshall Schor <[email protected]> > > On 3/6/2013 12:53 PM, Peter Klügl wrote: > > Hi, > > > > I added you to the Administrators. > > > > Best, > > > > Peter > > +1 :-) Marshall > > > > > > Am 06.03.2013 18:02, schrieb Tommaso Teofili: > >> Hi all, > >> > >> can anyone with needed privileges either create Jira release versions > 2.3.2 > >> (unreleased) for AlchemyAPIAnnotator ,SolrCas, LuCas, TikaAnnotator, > >> ConceptMapper (just for start then maybe we'll need it for others as > well) > >> or allow me to do that (by administrating UIMA Jira project)? > >> > >> Thanks in advance, > >> Tommaso > >> > >> > >> 2013/3/4 Tommaso Teofili <[email protected]> > >> > >>> > >>> > >>> 2013/3/4 Marshall Schor <[email protected]> > >>> > >>>> 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? > >>>> > >>> no I think you're right, just I think it'd be somewhat unclean to have > the > >>> parent bound to a jiraVersion which is completely unrelated to the > modules, > >>> but I agree we can go with the existing one (I'd have to revert the > addons > >>> to use uima-addons-parent 2.3.1 to avoid snapshot dependencies) by just > >>> overriding that setting. > >>> > >>> Regards, > >>> Tommaso > >>> > >>> > >>> > >>>> -Marshall > >>>> > >>> > > > > > >
