Hide Forgot
Description of problem: I have small groovy script to check mail mailCheck.groovy For windows environment it run from cmd file like: groovy.bat --classpath commons-net-2.0.jar mailCheck.groovy Jar file commons-net-2.0.jar placed in the same directory. I've try to do the same on Linux. $ groovy --help usage: groovy [options] [args] options: .... -classpath <path> Specify where to find the class files - must be first argument -cp,--classpath <path> Aliases for '-classpath' but this give me error: $ groovy --classpath /home/pasha/temp/groovy-test/commons-net-2.0.jar mailCheck.groovy org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: /home/pasha/temp/groovy-test/mailCheck.groovy: 5: unable to resolve class org.apache.commons.net.pop3.POP3Client @ line 5, column 1. import org.apache.commons.net.pop3.POP3Client ^ 1 error I have tried also variants like: groovy --classpath ./commons-net-2.0.jar mailCheck.groovy groovy --classpath /home/pasha/temp/groovy-test/commons-net-2.0.jar mailCheck.groovy groovy -cp /home/pasha/temp/groovy-test/commons-net-2.0.jar mailCheck.groovy groovy -cp commons-net-2.0.jar mailCheck.groovy groovy -cp ./commons-net-2.0.jar mailCheck.groovy Also with no success. Version-Release number of selected component (if applicable): $ rpm -q groovy groovy-1.8.6-3.fc16.noarch How reproducible: Always
Why not use the provided jar file by apache-commons-net? Does this work?
Its just example off course. I want use with my own jars. Additionally there may bee needed bundle its too. Finally it is documented, so this must works.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
On groovy-2.0.4-1.fc17.noarch reproduced also.
groovy-1.8.7-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/groovy-1.8.7-4.fc18
groovy-1.8.8-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/groovy-1.8.8-4.fc19
Package groovy-1.8.8-4.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing groovy-1.8.8-4.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5541/groovy-1.8.8-4.fc19 then log in and leave karma (feedback).
I had tested in on 2.0 version. For what 1.8.8 also pushed in Fedora 19??
groovy-1.8.8-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
groovy-1.8.9-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/groovy-1.8.9-1.fc18
(In reply to Pavel Alexeev (aka Pahan-Hubbitus) from comment #10) > I had tested in on 2.0 version. For what 1.8.8 also pushed in Fedora 19?? Hi Pavel. We don't have groovy 2.x in Fedora 19 yet. I've just pushed another build yesterday for groovy 1.8.9. I plan to check into Groovy 2.x soon to see if we have the dependencies in place to make that happen.
Package groovy-1.8.9-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing groovy-1.8.9-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-8955/groovy-1.8.9-1.fc18 then log in and leave karma (feedback).
groovy-1.8.9-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.