You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "zoe slattery (JIRA)" <ji...@apache.org> on 2011/02/08 15:54:57 UTC
[jira] Created: (ARIES-571) Revert the changes in
parent/default-parent/pom.xm that calculate import ranges based on
${project.version}
Revert the changes in parent/default-parent/pom.xm that calculate import ranges based on ${project.version}
-----------------------------------------------------------------------------------------------------------
Key: ARIES-571
URL: https://issues.apache.org/jira/browse/ARIES-571
Project: Aries
Issue Type: Bug
Affects Versions: 0.4
Reporter: zoe slattery
Assignee: zoe slattery
Fix For: 0.4
Under Aries-262 changes were made in the default parent pom which make each module calculate a versions range for the Aries packages that it imports based on it's own ${project.version}. For example, Blueprint at version 0.4-SNAPSHOT will build manifests in blueprint modules that will import Util packages in the range [0.4,1). At release time this means that we must release Util 0.4, even if it has no changes over 0.3, at the same time as we release Blueprint 0.4
The changes checked in under this JIRA reverts this.
Note - this is only a small part of what was fixed under ARIES-262.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (ARIES-571) Revert the changes in
parent/default-parent/pom.xm that calculate import ranges based on
${project.version}
Posted by "zoe slattery (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zoe slattery resolved ARIES-571.
--------------------------------
Resolution: Fixed
> Revert the changes in parent/default-parent/pom.xm that calculate import ranges based on ${project.version}
> -----------------------------------------------------------------------------------------------------------
>
> Key: ARIES-571
> URL: https://issues.apache.org/jira/browse/ARIES-571
> Project: Aries
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: zoe slattery
> Assignee: zoe slattery
> Fix For: parent-0.4.0
>
>
> Under Aries-262 changes were made in the default parent pom which make each module calculate a versions range for the Aries packages that it imports based on it's own ${project.version}. For example, Blueprint at version 0.4-SNAPSHOT will build manifests in blueprint modules that will import Util packages in the range [0.4,1). At release time this means that we must release Util 0.4, even if it has no changes over 0.3, at the same time as we release Blueprint 0.4
> The changes checked in under this JIRA reverts this.
> Note - this is only a small part of what was fixed under ARIES-262.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (ARIES-571) Revert the changes in
parent/default-parent/pom.xm that calculate import ranges based on
${project.version}
Posted by "zoe slattery (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zoe slattery closed ARIES-571.
------------------------------
> Revert the changes in parent/default-parent/pom.xm that calculate import ranges based on ${project.version}
> -----------------------------------------------------------------------------------------------------------
>
> Key: ARIES-571
> URL: https://issues.apache.org/jira/browse/ARIES-571
> Project: Aries
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: zoe slattery
> Assignee: zoe slattery
> Fix For: parent-0.4.0
>
>
> Under Aries-262 changes were made in the default parent pom which make each module calculate a versions range for the Aries packages that it imports based on it's own ${project.version}. For example, Blueprint at version 0.4-SNAPSHOT will build manifests in blueprint modules that will import Util packages in the range [0.4,1). At release time this means that we must release Util 0.4, even if it has no changes over 0.3, at the same time as we release Blueprint 0.4
> The changes checked in under this JIRA reverts this.
> Note - this is only a small part of what was fixed under ARIES-262.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ARIES-571) Revert the changes in
parent/default-parent/pom.xm that calculate import ranges based on
${project.version}
Posted by "zoe slattery (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zoe slattery updated ARIES-571:
-------------------------------
Fix Version/s: (was: 0.4)
parent-0.4.0
> Revert the changes in parent/default-parent/pom.xm that calculate import ranges based on ${project.version}
> -----------------------------------------------------------------------------------------------------------
>
> Key: ARIES-571
> URL: https://issues.apache.org/jira/browse/ARIES-571
> Project: Aries
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: zoe slattery
> Assignee: zoe slattery
> Fix For: parent-0.4.0
>
>
> Under Aries-262 changes were made in the default parent pom which make each module calculate a versions range for the Aries packages that it imports based on it's own ${project.version}. For example, Blueprint at version 0.4-SNAPSHOT will build manifests in blueprint modules that will import Util packages in the range [0.4,1). At release time this means that we must release Util 0.4, even if it has no changes over 0.3, at the same time as we release Blueprint 0.4
> The changes checked in under this JIRA reverts this.
> Note - this is only a small part of what was fixed under ARIES-262.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira