accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4383) Configure animal-sniffer-maven-plugin to fail when new unsupported JDK APIs are used
Date Thu, 21 Jul 2016 22:52:20 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388566#comment-15388566
] 

Christopher Tubbs commented on ACCUMULO-4383:
---------------------------------------------

My jenkins won't catch Java 6 problems, because I can't really get Java 6 to work with my
version of Jenkins and Maven. (dependency jars have newer class files in them... polluting
the classpath... hard to resolve). That's probably less of an issue with 1.7 branch and Java
7. Sooner we close out the 1.6 branch, the better for issues like this.

> Configure animal-sniffer-maven-plugin to fail when new unsupported JDK APIs are used
> ------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4383
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4383
>             Project: Accumulo
>          Issue Type: Task
>          Components: build
>            Reporter: Josh Elser
>            Assignee: Christopher Tubbs
>             Fix For: 1.6.6, 1.7.3, 1.8.1
>
>
> Benson gave us a great little pointer to http://www.mojohaus.org/animal-sniffer/animal-sniffer-maven-plugin/
> We should configure this plugin to run during our build to catch when we accidentally
use JDK APIs which only exist in a newer version of Java than what we target for a specific
release line.
> For example, mid-2016, we have problems with JDK8 APIs slipping into release lines which
still need to support JDK7. We had a similar problem when switching from JDK6 to JDK7.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message