-
Notifications
You must be signed in to change notification settings - Fork 87
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
build does not work with java 10+ #8
Labels
Milestone
Comments
hohwille
added
SCM
Software-configuration-management (maven, travis, etc.)
enhancement
New feature or request
labels
Sep 20, 2018
hohwille
added a commit
to hohwille/devon4j
that referenced
this issue
Sep 20, 2018
devonfw#9: fixed dependencies so security also works with Java8 and Java9-11
hohwille
added a commit
that referenced
this issue
Sep 24, 2018
PR #10 merged, hence done. |
hohwille
added a commit
to hohwille/devon4j
that referenced
this issue
Sep 24, 2018
devonfw#9: fixed dependencies so security also works with Java8 and Java9-11
hohwille
added a commit
that referenced
this issue
Oct 23, 2018
hohwille
added a commit
that referenced
this issue
Oct 29, 2018
* #8: fixed build to work with Java8 and Java9-11 #9: fixed dependencies so security also works with Java8 and Java9-11 * #13: removed deprecated code * #14: decoupling from mmm-util-entity (mmm-util-core is still used for exception/I18N stuff) oasp/oasp4j#684: replaced AbstractJsonDeserializer with JacksonUtil * #13: removed more deprecated code * #14: not considered a todo anymore. With dropping this exception support we would lose valuable features and making it optional seems to be overcomplicated. * #14: completed (adapted bean-mapping, moved PersistenceEntity also to basic for simplicity, decoupled web component, upgraded to modularized mmm-util and reduced dependency to mmm-util-exception) * #21: try to cache maven repo to make build more stable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We have to update surefire so the build can work with new java versions. This applies both to the devon4j pom as well as to what we deliver with our archetype. IMHO we also need to update the compiler plugin.
As EOL is comming closer we should therefore get prepared.
See also junit-team/junit4#1513
The text was updated successfully, but these errors were encountered: