Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support Neodymium build in an Java 11 environment #73

Closed
occupant23 opened this issue Feb 8, 2019 · 2 comments
Closed

Support Neodymium build in an Java 11 environment #73

occupant23 opened this issue Feb 8, 2019 · 2 comments
Assignees
@occupant23
Labels
codeDone The issue is rechecked for development branch codeReadyForRecheck The issue is fixed/implemented AND merged into development, but needs to be rechecked there High Priority improvement
Milestone
v3.1.0

Comments

@occupant23
Copy link
Contributor

occupant23 commented Feb 8, 2019 •
edited
Loading

See what needs to be done.
@occupant23 occupant23 added this to the v3.1.0 milestone Feb 8, 2019
@occupant23 occupant23 self-assigned this Feb 8, 2019
occupant23 pushed a commit that referenced this issue Feb 8, 2019
#73: Support Neodymium build in an Java 11 environment
7dec206
@occupant23 occupant23 added the codeReadyForRecheck The issue is fixed/implemented AND merged into development, but needs to be rechecked there label Feb 8, 2019
@occupant23
Copy link
Contributor Author

added the following workaround to the pom.xml in order to do this without skipping the java doc for local builds.

<configuration>
    <source>8</source>
</configuration>

This can be undone when maven-javadoc-plugin v3.1.0 is released since this should fix the issue.
(See here for mor info: https://issues.apache.org/jira/browse/MJAVADOC-555)

@jowerner
Copy link

Works for me, with and without your modification. I'm using OpenJDK 11.

@jowerner jowerner added the codeDone The issue is rechecked for development branch label Feb 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@occupant23 occupant23

Labels
codeDone The issue is rechecked for development branch codeReadyForRecheck The issue is fixed/implemented AND merged into development, but needs to be rechecked there High Priority improvement
Projects
None yet
Milestone
v3.1.0
Development

No branches or pull requests
2 participants
@jowerner @occupant23