You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Kim van der Riet (JIRA)" <ji...@apache.org> on 2018/07/09 16:56:00 UTC
[jira] [Resolved] (QPIDIT-131) module versions on master dont match
and are incorrect
[ https://issues.apache.org/jira/browse/QPIDIT-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim van der Riet resolved QPIDIT-131.
-------------------------------------
Resolution: Fixed
The pom version on master has now been set to {{0.3.0-SNAPSHOT}} as suggested. All the .pom files are now consistent.
> module versions on master dont match and are incorrect
> ------------------------------------------------------
>
> Key: QPIDIT-131
> URL: https://issues.apache.org/jira/browse/QPIDIT-131
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Task
> Components: Installation
> Affects Versions: 0.3.0
> Reporter: Robbie Gemmell
> Assignee: Kim van der Riet
> Priority: Major
> Fix For: 0.3.0
>
>
> The various modules version numbers on master dont match. The root pom is versions 0.2.0-rc1 while the children are still at 0.1.0 by virtue of having stale parent definitions. Thats its own issue since 0.1.0 was already released so new release modules definitely shouldn't have that version.
> Separately from not aligning with each other, they should really all be at 0.3.0-SNAPSHOT by now but aren't yet.
> See QPIDIT-130 for some an example on how to ease managing the module versions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org