Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
n/a
Description
Within a web application, you can store compliled java classes not only in jars in a lib directory, but also in a classes directory. I am proposing that groovy support the same structure, essentially sourcing (including in the classpath) anything in and under ~/.groovy/classes/*.groovy. Users would still have to import properly.
This would help encourage good programming practice w/in groovy - i.e., getting people to make lots of small classes instead of gigantic functional scripts. JARing, while cool, doesn't really fit with a scripting language approach of just cranking text files. You can't just pop into a jar and edit it.