geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Bohn <joe.b...@earthlink.net>
Subject Re: [jira] Created: (GERONIMO-4271) Allow plugins with dependencies on older geronimo 2.1.* components to install on Geronimo 2.1.3
Date Fri, 29 Aug 2008 14:49:05 GMT

There are a lot of version updates that are not called out in the 
release process.  The only real way to tackle them all is to grep 
through the source for all current version references when updating for 
a release.  That is how I did it for the last 2 releases.  I can attempt 
to document all of them ... but we still need to manually verify as we 
release.

Joe


Donald Woods wrote:
> Do we need to update the release process to remind us to update these 
> entries for future 2.1.x releases?
> 
> 
> -Donald
> 
> 
> Joe Bohn (JIRA) wrote:
>> Allow plugins with dependencies on older geronimo 2.1.* components to 
>> install on Geronimo 2.1.3
>> -----------------------------------------------------------------------------------------------

>>
>>
>>                  Key: GERONIMO-4271
>>                  URL: https://issues.apache.org/jira/browse/GERONIMO-4271
>>              Project: Geronimo
>>           Issue Type: Improvement
>>       Security Level: public (Regular issues)
>>     Affects Versions: 2.1.3
>>             Reporter: Joe Bohn
>>             Assignee: Joe Bohn
>>
>>
>> Currently plugins that have version specific dependencies on other 
>> components cannot be install in a later Geronimo version.  For 
>> example, a sample built with dependencies on Geronimo 2.1.2 components 
>> can not be installed in a 2.1.3-SNAPSHOT server.  We can enable this 
>> support by including artifact-alias entries for 2.1, 2.1.1, and 2.1.2 
>> components that map to the 2.1.3-SNAPSHOT equivalent component.  When 
>> we release Geronimo 2.1.3 these alias entries will be updated 
>> accordingly.
>>


Mime
View raw message