curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randgalt <>
Subject [GitHub] curator pull request #204: [CURATOR-378] Update mvn parent pom, plugin and o...
Date Wed, 15 Mar 2017 02:35:49 GMT
Github user Randgalt commented on a diff in the pull request:
    --- Diff: pom.xml ---
    @@ -62,22 +62,22 @@
             <!-- versions -->
    -        <maven-project-info-reports-plugin-version>2.7</maven-project-info-reports-plugin-version>
    -        <maven-bundle-plugin-version>2.3.7</maven-bundle-plugin-version>
    -        <maven-javadoc-plugin-version>2.10.3</maven-javadoc-plugin-version>
    -        <doxia-module-confluence-version>1.6</doxia-module-confluence-version>
    +        <maven-project-info-reports-plugin-version>2.9</maven-project-info-reports-plugin-version>
    +        <maven-bundle-plugin-version>3.2.0</maven-bundle-plugin-version>
    +        <maven-javadoc-plugin-version>2.10.4</maven-javadoc-plugin-version>
    +        <doxia-module-confluence-version>1.7</doxia-module-confluence-version>
    -        <javassist-version>3.18.1-GA</javassist-version>
    +        <javassist-version>3.20.0-GA</javassist-version>
    -        <guava-version>16.0.1</guava-version>
    +        <guava-version>19.0</guava-version>
    --- End diff --
    As we now shade Guava into Curator I don't think it's that big of a deal which version
we put in our POM. I'd say use the most commonly used version so that we don't screw up anyone
else's build.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message