incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan D. Cabrera" <>
Subject Re: maven repository
Date Fri, 30 May 2008 21:36:21 GMT

On May 30, 2008, at 2:23 PM, James Carman wrote:

> On Fri, May 30, 2008 at 5:17 PM, Janne Jalkanen
> <> wrote:
>>> As an end user, I would _hate_ to have to change all of my code to
>>> reference a totally new package structure after the podling  
>>> graduates.
>>> That's a major pain...
>> With JSPWiki we have plenty of plugins and other extensions donated  
>> by
>> people over the years.  Every binary break means that we obsolete  
>> most of
>> this stuff (unless we can take the responsibility of recompiling
>> everything).  Every binary break means that we will have to answer  
>> questions
>> from people running obsolete software because they can't afford the  
>> cost of
>> the upgrade because they have money invested in the customizations.
>> So it's not only the pain of upgrading the package definitions;  
>> changing
>> packages issues a damaging blow to the ecosystem nurtured in the  
>> incubator.
>> Sometimes the impact can be minimal; sometimes it could be rather  
>> bad.
> The package names have to change when a podling comes into the
> incubator (to the org.apache namespace).  So, the "blow" has to happen
> anyway.  I'm not suggesting we enforce this for existing podlings
> necessarily, but future ones should probably do it.  Once the podling
> graduates, the plugins would need to change the package name they use
> because they are now based on an official ASF library.  Is
> find/replace really that difficult?

Yes, it is.  When your entire community and the communities that rely  
on them have to do it, yes it is.  Remember, some podlings incubate  
for years and so these roots can go way out.

Frankly, I am really, really, surprised that this is being entertained  
at all.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message