You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Jörn Kottmann <ko...@gmail.com> on 2012/06/01 00:08:51 UTC
Re: Contributing uimaFIT to Apache UIMA
On 05/31/2012 10:02 PM, Richard Eckart de Castilho wrote:
> We (uimaFIT developers) would like a transition to Apache to cause minimal
> hassle for existing users. If possible, it should be limited to updating the
> imports for a new package name and changing a dependency/jar.
Is it a must to change the package names? This will break it
for the existing user base.
Jörn
Re: Contributing uimaFIT to Apache UIMA
Posted by Thilo Goetz <tw...@gmx.de>.
On 01/06/12 05:26, Marshall Schor wrote:
>
>
> On 5/31/2012 6:08 PM, Jörn Kottmann wrote:
>> On 05/31/2012 10:02 PM, Richard Eckart de Castilho wrote:
>>> We (uimaFIT developers) would like a transition to Apache to cause
>>> minimal
>>> hassle for existing users. If possible, it should be limited to
>>> updating the
>>> imports for a new package name and changing a dependency/jar.
>>
>> Is it a must to change the package names? This will break it
>> for the existing user base.
>
> It seems not to be a requirement. But there's some evidence in other
> projects that didn't do this that it caused some problems down the road.
The sooner you do this, the less painful it will be. For me it
would be a requirement for the first release. Rebranding might
be the only thing you do for a first release.
--Thilo
>
> In the past, we built some auto-fixup tooling for this kind of
> conversion. See
> http://uima.apache.org/d/uimaj-2.4.0/overview_and_setup.html#ugr.project_overview_migrating_from_ibm_uima
> ; it had tooling to do package renaming, IIRC.
>
> Another thing which is likely required is to change the Maven "group-id"
> to org.apache.uima - I think the auto-release tooling might have some
> dependencies on this, given Maven's convention-over-configuration
> orientation.
>
> -Marshall
>>
>> Jörn
>>
Re: Contributing uimaFIT to Apache UIMA
Posted by Marshall Schor <ms...@schor.com>.
On 5/31/2012 6:08 PM, Jörn Kottmann wrote:
> On 05/31/2012 10:02 PM, Richard Eckart de Castilho wrote:
>> We (uimaFIT developers) would like a transition to Apache to cause minimal
>> hassle for existing users. If possible, it should be limited to updating the
>> imports for a new package name and changing a dependency/jar.
>
> Is it a must to change the package names? This will break it
> for the existing user base.
It seems not to be a requirement. But there's some evidence in other projects
that didn't do this that it caused some problems down the road.
In the past, we built some auto-fixup tooling for this kind of conversion. See
http://uima.apache.org/d/uimaj-2.4.0/overview_and_setup.html#ugr.project_overview_migrating_from_ibm_uima
; it had tooling to do package renaming, IIRC.
Another thing which is likely required is to change the Maven "group-id" to
org.apache.uima - I think the auto-release tooling might have some dependencies
on this, given Maven's convention-over-configuration orientation.
-Marshall
>
> Jörn
>