[
https://issues.apache.org/jira/browse/TAMAYA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386426#comment-16386426
]
ASF GitHub Bot commented on TAMAYA-330:
---------------------------------------
GitHub user acoburn opened a pull request:
https://github.com/apache/incubator-tamaya/pull/17
Update maven plugins to support jdk9+ builds
Resolves TAMAYA-330
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/acoburn/incubator-tamaya TAMAYA-330
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-tamaya/pull/17.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #17
----
commit b2af8c7020d44bb04e0b6bc053fe6de4dfa48acb
Author: Aaron Coburn <acoburn@...>
Date: 2018-03-04T18:03:47Z
Update maven plugins to support jdk9+ builds
Resolves TAMAYA-330
----
> Make it possible to build Tamaya on JDK 9+
> ------------------------------------------
>
> Key: TAMAYA-330
> URL: https://issues.apache.org/jira/browse/TAMAYA-330
> Project: Tamaya
> Issue Type: Improvement
> Components: API, Core, Extensions
> Environment: jdk9 and jdk10 build environments.
> Reporter: Aaron Coburn
> Priority: Minor
> Fix For: 0.4-incubating
>
>
> While the current codebase is _usable_ in JDK 9+ environments, it is not
> possible to _build_ the source code with JDK 9 or later.
> The limiting factor is the karaf plugin requiring some Java EE libraries that
> are no longer available by default (javax.xml.bind and javax.activation).
> Adding an explicit dependency within the plugin configuration resolves this.
> Also, for JDK 10, the javadoc plugin is unable to parse the JVM version
> string. This is due to the fact that the javadoc plugin uses commons-lang3
> version 3.5; upgrading that plugin's dependency to commons-lang3 3.7 fixes
> this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
