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

Jerry Cwiklik updated UIMA-5511:
--------------------------------
    Description: 
Add javadoc plugin to ducc's parent pom.xml. Since each ducc subproject imports 
parent pom and javadoc plugin is not defined, maven uses javadoc plugin from 
uima super pom where this plugin configuration is quite old. It sets java 
source level to 1.5.

The consequence is that the build fails (when building with -Papache-release).

The error is:
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:jar (attach-javadocs) on 
project uima-ducc-user: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - 
/users1/cwiklik/releases/builds/uima-ducc/trunk/uima-ducc-user/src/main/java/org/apache/uima/ducc/user/service/UimaASServiceContainer.java:114:
 error: try-with-resources is not supported in -source 1.5
[ERROR] try (FileOutputStream outs = new FileOutputStream(outf)) {
[ERROR] ^
[ERROR] (use -source 7 or higher to enable try-with-resources)

By providing javadoc plugin in the paren pom we effectively override uima super 
pom settings for this plug-in. Set the java source level to whatever maven 
compiler plugin  source is set to. The try-with-resources is available since 
java 1.7.

  was:
Ducc's javadoc plugin is in the wrong pom. Instead of being in the parent-pom 
its in the base 
 pom. Since all Ducc sub-projects inherit from parent-pom and javadoc is not 
found there, they end up inheriting this plugin from uima super pom where these 
plugins are setup for java 5 not java 7. The consequence is that the build 
fails (when building with -Papache-release).

The error is:
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:jar (attach-javadocs) on 
project uima-ducc-user: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - 
/users1/cwiklik/releases/builds/uima-ducc/trunk/uima-ducc-user/src/main/java/org/apache/uima/ducc/user/service/UimaASServiceContainer.java:114:
 error: try-with-resources is not supported in -source 1.5
[ERROR] try (FileOutputStream outs = new FileOutputStream(outf)) {
[ERROR] ^
[ERROR] (use -source 7 or higher to enable try-with-resources)

The try-with-resources is available since java 1.7.

        Summary: UIMA-DUCC: add javadoc plugin to parent pom.xml  (was: 
UIMA-DUCC: move javadoc plugin from base pom to parent pom)

> UIMA-DUCC: add javadoc plugin to parent pom.xml
> -----------------------------------------------
>
>                 Key: UIMA-5511
>                 URL: https://issues.apache.org/jira/browse/UIMA-5511
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.2.1-Ducc
>
>
> Add javadoc plugin to ducc's parent pom.xml. Since each ducc subproject 
> imports parent pom and javadoc plugin is not defined, maven uses javadoc 
> plugin from uima super pom where this plugin configuration is quite old. It 
> sets java source level to 1.5.
> The consequence is that the build fails (when building with -Papache-release).
> The error is:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:jar (attach-javadocs) on 
> project uima-ducc-user: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - 
> /users1/cwiklik/releases/builds/uima-ducc/trunk/uima-ducc-user/src/main/java/org/apache/uima/ducc/user/service/UimaASServiceContainer.java:114:
>  error: try-with-resources is not supported in -source 1.5
> [ERROR] try (FileOutputStream outs = new FileOutputStream(outf)) {
> [ERROR] ^
> [ERROR] (use -source 7 or higher to enable try-with-resources)
> By providing javadoc plugin in the paren pom we effectively override uima 
> super pom settings for this plug-in. Set the java source level to whatever 
> maven compiler plugin  source is set to. The try-with-resources is available 
> since java 1.7.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to