Replies: 7 comments 5 replies
-
|
Hi, |
Beta Was this translation helpful? Give feedback.
-
|
I'm using Netbeans. I can open/edit/debug core, but I can't run individual tests from NetBeans. For example I copied AutoCompleteSupportTestApp to a separate NetBeans project and can run/debug that way. If I open other subprojects, for example extensions/icu4j, when I open a file, GlazedListsICU4J.java for example, the imports that resolve into the "core" jar are not found (error highlights from IDE). I'm investigating this from the NetBeans side. I suspect the rather archaic build.gradle files are at the root of the issue. I want to add some tests for AutoCompleteSupport. The tests of interest are in extensions/icu4j, for example AutoCompleteSupportTest. I'm not doing anything in particular with icu4j, but that's where the test is. Since this is the first project I've worked with that uses gradle, I'm at more of a loss than usual. Any hints or suggestions appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
"./gradlew build --scan" produced https://gradle.com/s/iwj7ksmm72wc2 with deprecation < 10000 div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="The configuration :extensions:compileClasspath was resolved without accessing the project in a safe manner.">This seems related to the type of problem I'm having, so I'll see what I can see. The deprecation warning suggested looking at |
Beta Was this translation helpful? Give feedback.
-
Sorry, I'm not familiar with Netbeans, I'm a Eclipse user. Usually there are IDE plugins for supporting build tools, like m2e for Maven support and Buildship for Gradle support in Eclipse. |
Beta Was this translation helpful? Give feedback.
-
|
@errael FYI: I've enabled the Discussions feature of Github for this project and moved your question to the Q&A section. |
Beta Was this translation helpful? Give feedback.
-
|
I'm using NetBeans support for gradle, but I'm guessing it's more restrictive. I'm trying to figure out how to get rid of the warning about the extensions classpath resolution. I'm hoping that fixing that will fix the NetBeans issue. Fortunately the tests I'm working on can be put together with minimal scaffolding, |
Beta Was this translation helpful? Give feedback.
-
|
The issue with NetBeans is solved. I run NB on jdk-15, so that's the default to run gradle. Gradle 5.3.1 (used by glazedlists) doesn't support newer jdks and that was the root of the problems I was having. Set some properties in NetBeans so that it uses jdk-11 to run gradle; no more error badges in the editor and I can use the IDE to edit and run tests, even "debug focused test method" is working. |
Beta Was this translation helpful? Give feedback.
-
|
I'm glad you could resolve this issue. Please keep in mind that Glazed Lists 1.12 will have a Java 8 baseline. |
Beta Was this translation helpful? Give feedback.
-
(gradle novice here) I've assumed that |
Beta Was this translation helpful? Give feedback.
-
I don't understand the implications. Does "develop" mean use? Is this about producing a compatible glazedlist artifact? |
Beta Was this translation helpful? Give feedback.
-
|
javaTargetVersion = 1.8 ensures that source and target is set to 1.8, indeed. But when you build against a JDK 11 (as you indicated above) it would still be possible to use a Java 11 API unnoticed. Concerning JavaFx: JavaFx is only needed for the Glazed Lists JavaFx extension. So, building all parts of Glazed Lists, the JavaFx APIs are required on the classpath. Oracle Java 8 JDK bundles JavaFx, so that should work out of the box. Building against a JDK 8 without bundled JavaFx (e.g. from AdoptOpenJDK) will not work out of the box. Things changed with newer JDK versions. Oracle has removed JavaFx from its JDK, so JavaFx is usually included as any other third-party dependency. Therefore, we use the org.openjfx.javafxplugin Gradle plugin for Java >= 11 to include JavaFx as dependency. Please see the build.gradle file of the JavaFx extension for details. So, to sum up: if you want to use and build against a Java 8 version, please use a Oracle JDK 8. |
Beta Was this translation helpful? Give feedback.
-
Very much so. Thanks. BTW, I do a command line build, with JAVA_HOME jdk1.8 oracle, as a final check. (Of course sh*t happens) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The project seems abandoned. (I'm going to look through the forks, but ...)
I'm going to work on a fix for #676. I'm wondering if the project might be active in some other location.
I'm basing my fix on 1.11.0. I was tempted to back up to 1.10.0 since I have no gradle experience. Could go with 1.12 snap, but I wonder about stability; it looks mostly like jdk1.8+ support.
Any insights appreciated.
Beta Was this translation helpful? Give feedback.
All reactions