-
Notifications
You must be signed in to change notification settings - Fork 93
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
ArgoUML does not compile with Java8 or Java 11, small adaptations necessary #14
Comments
…a 11, small adaptations necessary Fix the ListSet class to use the Spliterator so that it compiles with Java 8. Fix classes that inherit from DefaultListModel to make the addAll() public instead of protected. Change-Id: I91836a692dbc6125540502e6c96d87016a827bde
What do you mean by Java8? Is there two Java8? When buildnig and testing on my Linux host I successfully use another Java8: As I hope you noticed from my comment on the Change in Gerrithub, your changes makes many tests fail on that Jenkins-server. |
The java version is one thing, the target compilation version is another. I guess the issue comes from parentpom/pom.xml which has the definition:
I've changed that locally to use:
From maven, I'm using:
And from Intellij Idea, I was using JDK 1.8.0162 with target version 1.8. |
When running the unit tests with maven, I'm getting:
The failed test is
|
Rebase the argouml project (repo sync, repo rebase). I have fixed that now. |
ArgoUML shouldn't really care about what version of Java it is compiled by and for. Should we stop specifying compileSource in parentpom? |
The I've rebased and changed the parent pom to:
and now I'm getting the following
For me it seems reasonable to compile and use JRE 8 as target. |
ArgoUML is compiled with Java 5 or 6 but it is desirable to use Java8 or higher.
There are only a few places to correct in order to compile with Java8
By fixing these, I was able to build and run ArgoUML compiled with Java8 and even Java 11.
(OpenJDK under Ubuntu 20.04LTS).
The text was updated successfully, but these errors were encountered: