| Summary: | groovy ebuild should provide 'startGroovy' script | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | corey <corey_s> |
| Component: | [OLD] Java | Assignee: | Java team <java> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 2007.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
corey
2007-08-28 20:02:11 UTC
The following simple patch seems to do the trick:
--- groovy-1.0-r1.ebuild.orig 2007-08-29 04:56:11.000000000 -0700
+++ groovy-1.0-r1.ebuild 2007-08-29 04:55:58.000000000 -0700
@@ -115,4 +115,5 @@
java-pkg_dolauncher "groovy" --main groovy.ui.GroovyMain
java-pkg_dolauncher "groovysh" --main groovy.ui.InteractiveShell
java-pkg_dolauncher "groovyConsole" --main groovy.ui.Console
+ dobin ${S}/src/bin/startGroovy
}
What does startGroovy do? Is it still necessary in recent (1.6.x) Groovy? My understanding is that the groovy launcher does everything that is needed, so this bug can probably be closed. (In reply to comment #2) > What does startGroovy do? Is it still necessary in recent (1.6.x) Groovy? My > understanding is that the groovy launcher does everything that is needed, so > this bug can probably be closed. > gant seems to use it. the following is a snippet of gant-starter. it seems gant uses groovy to load itself. this becomes harder to replicate using our launcher. *********** # Load user specific libraries that are Ant specific. load !{user.home}/.ant/lib/*.jar # Load user specific libraries that are for Groovy. load !{user.home}/.groovy/lib/*.jar # Load required libraries load !{gant.home}/lib/*.jar ************* I guess it very much depends on what the groovyStarter actually is, could it itself be another gentoo launcher? Closing bug as unsure whether this loader is still needed. Reopen with a detailed use case if you think this issue is still a problem. |
