You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Tommaso Teofili <to...@gmail.com> on 2013/03/04 08:47:30 UTC
releasing addons modules
Hi all,
I'm hoping to have some time this week to work on the release of (some of)
the addons.
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.
Also we would need to remove the current 2.3.1 (aggregate) addons Jira
version from the uima-addons-parent 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 hope it's clear :-)
Regards,
Tommaso
Re: releasing addons modules
Posted by Tommaso Teofili <to...@gmail.com>.
Hi Richerd,
2013/3/7 Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>
> Why don't you do a release of the full add-ons from the add-ons root
> folder?
> If all add-ons have the same version, then why do the tedious work of
> releasing
> them all separately?
>
here're some reasons we discussed in the past:
1. some of the modules haven't been touched (so far) for some time and
wouldn't make sense to release them (CFE, SimpleServer and others)
2. some others may have a release cycle different from the others (e.g.
Solrcas may have different versions based on latest Solr 3x and 4x so it
wouldn't make sense to try to trigger a new addons release for each Solr
version upgrade, and the same may apply for TikaAnnotator and Lucas)
3. this would make easier to develop and release the addons that have need
some improvement and the community is more interested in
Apart from that it may make sense at some point to identify a subset of the
current uima-addons modules and release a 2.4.x uima-addons with only such
modules inside, mostly for people to more easily obtain the complete list
of addons we actively develop.
In the end my main concern is move forward on the projects that have some
activity more cleanly and quickly than we'd have to do by releasing the
whole package.
I hope it clarifies things a bit.
Have a nice day,
Tommaso
>
> -- Richard
>
> Am 06.03.2013 um 23:05 schrieb Tommaso Teofili <tommaso.teofili@gmail.com
> >:
>
> > 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
>
>
> --
> -------------------------------------------------------------------
> Richard Eckart de Castilho
> Technical Lead
> Ubiquitous Knowledge Processing Lab (UKP-TUD)
> FB 20 Computer Science Department
> Technische Universität Darmstadt
> Hochschulstr. 10, D-64289 Darmstadt, Germany
> phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
> eckart@ukp.informatik.tu-darmstadt.de
> www.ukp.tu-darmstadt.de
> Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
> -------------------------------------------------------------------
>
>
Re: releasing addons modules
Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
Why don't you do a release of the full add-ons from the add-ons root folder?
If all add-ons have the same version, then why do the tedious work of releasing
them all separately?
-- Richard
Am 06.03.2013 um 23:05 schrieb Tommaso Teofili <to...@gmail.com>:
> 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
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD)
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Re: releasing addons modules
Posted by Tommaso Teofili <to...@gmail.com>.
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 <ms...@schor.com>
>
> 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 <to...@gmail.com>
> >>
> >>>
> >>>
> >>> 2013/3/4 Marshall Schor <ms...@schor.com>
> >>>
> >>>> 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
> >>>>
> >>>
> >
> >
>
>
Re: releasing addons modules
Posted by Marshall Schor <ms...@schor.com>.
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 <to...@gmail.com>
>>
>>>
>>>
>>> 2013/3/4 Marshall Schor <ms...@schor.com>
>>>
>>>> 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
>>>>
>>>
>
>
Re: releasing addons modules
Posted by Tommaso Teofili <to...@gmail.com>.
many thanks!
2013/3/6 Peter Klügl <pk...@uni-wuerzburg.de>
> Hi,
>
> I added you to the Administrators.
>
> Best,
>
> Peter
>
>
> 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 <to...@gmail.com>
>>
>>
>>>
>>> 2013/3/4 Marshall Schor <ms...@schor.com>
>>>
>>> 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
>>>>
>>>>
>>>
>
Re: releasing addons modules
Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Hi,
I added you to the Administrators.
Best,
Peter
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 <to...@gmail.com>
>
>>
>>
>> 2013/3/4 Marshall Schor <ms...@schor.com>
>>
>>> 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
>>>
>>
Re: releasing addons modules
Posted by Tommaso Teofili <to...@gmail.com>.
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 <to...@gmail.com>
>
>
>
> 2013/3/4 Marshall Schor <ms...@schor.com>
>
>>
>> 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
>>
>
>
Re: releasing addons modules
Posted by Tommaso Teofili <to...@gmail.com>.
2013/3/4 Marshall Schor <ms...@schor.com>
>
> 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
>
Re: releasing addons modules
Posted by Marshall Schor <ms...@schor.com>.
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