Bug 347842 – dev-java/groovy-2.4.5: groovy ignores --classpath

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Alexey Vladykin 2010-12-05 21:52:27 UTC]

groovy ignores --classpath given on command line.

Reproducible: Always

Steps to Reproduce:
# echo 'class A {}' > A.groovy
# groovy --classpath . -e 'new A()'

Actual Results:  
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
script_from_command_line: 1: unable to resolve class A 
 @ line 1, column 1.
   new A()
   ^

1 error


Expected Results:  
no error

This one work correctly:
# CLASSPATH=. groovy -e 'new A()'

[Comment 1 Ralph Sennhauser (RETIRED) 2013-01-21 15:37:52 UTC]

*** Bug 453210 has been marked as a duplicate of this bug. ***

[Comment 2 Patrice Clement (RETIRED) 2015-11-01 17:31:30 UTC]

This is a bug caused by the way we create our launchers to execute Java programs. The -cp/-classpath option is already set in stone within the launcher and as far as I can see, specifying it again doesn't override the launcher classpath nor it updates it. Basically, as if you were trying to run: java -cp /some/java/program.jar:. -cp /some/other.jar:. org.gentoo.java.Main. java picks the values specified in the 1st -cp option and ignores the ones passed to the 2nd -cp option. We should look into this issue.

[Comment 3 Michał Górny 2019-09-14 15:38:13 UTC]

Package removed.