ClassGraph thinks the application jars are JRE_LIB_OR_EXT_JARS

[emaayan]

hi.. when working from the IDE classGraph works fine, how in runtime my applicaiton is order like so
. -> root folder
jre -> jre folder
lib -> folder for all my jars

scripts for runnig the app.

so when running the scripts the code in SystemJarFinder the code sees the folder jre and assume my root folder is the jdk,
even though it's not, so it takes all jars in lib folder as system jars ..

 if (javaHome != null && !javaHome.isEmpty()) {
            final File javaHomeFile = new File(javaHome);
            addJREPath(javaHomeFile);
            if (javaHomeFile.getName().equals("jre")) {
                // Try adding "{java.home}/.." as a JDK root when java.home is a JRE path
                final File jreParent = javaHomeFile.getParentFile();
                addJREPath(jreParent);
                **addJREPath(new File(jreParent, "lib"));**
                addJREPath(new File(jreParent, "lib/ext"));
         
        }

perhaps you could add a setting like don't assume jdk folder above jre

[lukehutch]

Thanks for the report.

In every JDK release I have seen, the jre folder is within the JDK folder, if you have a JDK installed. I wonder how to do this in a more robust way...

What is your runtime environment?

[emaayan]

you're assuming the existence if a jdk and not just a jre, what if for example you have just a custom built jre folder?

[lukehutch]

Can you please suggest a robust way to detect the system lib and ext directories then?

[emaayan]

just give the user an option to override the default behaviour, by supplying their own javahome
a lib folder for application jars can be a very common structure for most java apps.

[lukehutch]

Is there likely to be some reliable way to tell between a JRE and a JDK?

I would want to check these variables across numerous releases, on all 3 major Java platforms, and for local install vs. system install:

https://docs.oracle.com/javase/tutorial/essential/environment/sysprop.html

If there's a way to reliably detect JRE (maybe the string "Runtime Environment" in one of the variables?), then I can avoid assuming JRE is always contained within a JDK dir.