You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2014/08/25 21:11:02 UTC

[jira] [Closed] (OPTIQ-363) Use dependencyManagement and pluginManagement in POM files

     [ https://issues.apache.org/jira/browse/OPTIQ-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde closed OPTIQ-363.
-----------------------------


Close issues resolved in release 0.9.0-incubating (2014-08-25).

> Use dependencyManagement and pluginManagement in POM files
> ----------------------------------------------------------
>
>                 Key: OPTIQ-363
>                 URL: https://issues.apache.org/jira/browse/OPTIQ-363
>             Project: Optiq
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>             Fix For: 0.9.0-incubating
>
>
> Some of the module pom files reference optiq-core and optiq-avatica with a version string, and this causes problems resolving dependencies.
> The fix is to put version strings in one and only one place. That place is the root pom. Use the dependencyManagement section in the root pom, declaring the versions of all dependencies. Similarly, use a pluginManagement section to contain plugin versions.
> In the sub-poms, dependencies and plugins must not have version strings.
> To help merging, all lists of dependencies and plugins must be sorted by groupId, artifactId.



--
This message was sent by Atlassian JIRA
(v6.2#6252)