You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Joe Bohn (JIRA)" <ji...@apache.org> on 2008/08/27 23:21:44 UTC
[jira] Created: (GERONIMO-4271) Allow plugins with dependencies on
older geronimo 2.1.* components to install on Geronimo 2.1.3
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (GERONIMO-4271) Allow plugins with dependencies
on older geronimo 2.1.* components to install on Geronimo 2.1.3
Posted by Joe Bohn <jo...@earthlink.net>.
clarification ... I attempted to update the *wiki* with all of the
places ...
Joe Bohn wrote:
> I just went in and attempted to update all the places where version
> updates are necessary for both the release branch (soon to be tag) and
> the updates to the branch that will continue.
>
> Joe
>
> Joe Bohn wrote:
>>
>> 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.
>>>>
>>
>>
>
>
Re: [jira] Created: (GERONIMO-4271) Allow plugins with dependencies
on older geronimo 2.1.* components to install on Geronimo 2.1.3
Posted by Joe Bohn <jo...@earthlink.net>.
I just went in and attempted to update all the places where version
updates are necessary for both the release branch (soon to be tag) and
the updates to the branch that will continue.
Joe
Joe Bohn wrote:
>
> 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.
>>>
>
>
Re: [jira] Created: (GERONIMO-4271) Allow plugins with dependencies
on older geronimo 2.1.* components to install on Geronimo 2.1.3
Posted by Joe Bohn <jo...@earthlink.net>.
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.
>>
Re: [jira] Created: (GERONIMO-4271) Allow plugins with dependencies
on older geronimo 2.1.* components to install on Geronimo 2.1.3
Posted by Donald Woods <dw...@apache.org>.
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.
>
Re: [jira] Resolved: (GERONIMO-4271) Allow plugins with dependencies
on older geronimo 2.1.* components to install on Geronimo 2.1.3
Posted by Joe Bohn <jo...@earthlink.net>.
I added the unversioned car entries to trunk last night before I
resolved the JIRA. I just didn't mark the JIRA as resolved in 2.2
because I thought that would be misleading given that the subject
specifically mentions 2.1.* components on 2.1.3 and I think it is a bit
presumptive to assume that we can run 2.1.* components on 2.2.
Joe
Donald Woods wrote:
> Do we need to also include some for of this in trunk, like at least the
> unversioned xxxx//car entries?
>
>
> -Donald
>
>
> Joe Bohn (JIRA) wrote:
>> [
>> https://issues.apache.org/jira/browse/GERONIMO-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Joe Bohn resolved GERONIMO-4271.
>> --------------------------------
>>
>> Resolution: Fixed
>> Fix Version/s: 2.1.3
>>
>>> 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
>>> Fix For: 2.1.3
>>>
>>>
>>> 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.
>>
Re: [jira] Resolved: (GERONIMO-4271) Allow plugins with dependencies
on older geronimo 2.1.* components to install on Geronimo 2.1.3
Posted by Donald Woods <dw...@apache.org>.
Do we need to also include some for of this in trunk, like at least the
unversioned xxxx//car entries?
-Donald
Joe Bohn (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/GERONIMO-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Joe Bohn resolved GERONIMO-4271.
> --------------------------------
>
> Resolution: Fixed
> Fix Version/s: 2.1.3
>
>> 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
>> Fix For: 2.1.3
>>
>>
>> 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.
>
[jira] Resolved: (GERONIMO-4271) Allow plugins with dependencies on
older geronimo 2.1.* components to install on Geronimo 2.1.3
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn resolved GERONIMO-4271.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.1.3
> 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
> Fix For: 2.1.3
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.