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.

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

JBMETA-400: ensure using the new time API works correctly for ISO 8601 dates #110

Merged
merged 2 commits into from Mar 24, 2017

Conversation

wolfc
Copy link
Contributor

@wolfc wolfc commented Mar 24, 2017

@@ -28,7 +28,7 @@
<parent>
<groupId>org.jboss</groupId>
<artifactId>jboss-parent</artifactId>
<version>21</version>
<version>11</version>
Copy link
Contributor Author

@wolfc wolfc Mar 24, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using parent 19 (currently in use by EAP 7.0) in conjunction with JDK 9 gives Maven compatibility errors.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please use version 22, it has important changes wrt to building on JDK9.
It is what all projects are moving to, WildFly master & upcoming EAP 7.1 uses that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That version is not available for EAP 7.0. For now I'm going to revert to 11 and revisit once we get to actually needing it. In other words, once we actually have a properly filed issue that outlines any Java 9 problems with the current build.

@wolfc wolfc merged commit d9e8a01 into jboss:master Mar 24, 2017
wolfc added a commit that referenced this pull request Mar 24, 2017
JBMETA-400: ensure using the new time API works correctly for ISO 8601 dates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants