You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2015/03/24 09:13:52 UTC
[jira] [Commented] (UIMA-4301) UIMAJ Javadocs Jenkins build failing
[ https://issues.apache.org/jira/browse/UIMA-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377471#comment-14377471 ]
Richard Eckart de Castilho commented on UIMA-4301:
--------------------------------------------------
The Java source and target levels can be controlled via properties that are used as default values by most plugins:
* maven.compiler.source
* maven.compiler.target
If we use those to set the compiler levels instead of overriding them per plugin, we should be able to avoid this kind of problem in the future.
> UIMAJ Javadocs Jenkins build failing
> ------------------------------------
>
> Key: UIMA-4301
> URL: https://issues.apache.org/jira/browse/UIMA-4301
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 2.7.1SDK
>
>
> The new generic code makes use of the "diamond" operator, which is valid in Java 7 but not in Java 5. Jenkins build (only?) seems to run a Javadoc goal with the execution id of "default-cli". Normal maven build does not run this goal... The parent pom had been updated to specify source level 7 but not for the execution id of default-cli. Add this configuration as a work-around to get the Jenkins build to work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)