History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: GRVY-1729
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Dmitry Krasilschikov
Reporter: Michael K. Werle
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Groovy

Exclude Compiler Output from Grails run/debug configurations

Created: 29 Aug 08 01:06   Updated: 13 Nov 08 16:37
Component/s: Grails other, Run & Debug
Affects Version/s: jetgroovy 1.6
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: IDEa 7.0.4 and JetGroovy 1.6.18808


 Description  « Hide
When developing in Grails, it is not necessary (or advisable) to use an IDE for compilation. The grails "run-app" command handles compilation and can reload most classes. When it cannot reload a class, it normally reloads the application completely w/o restarting the Java VM.

However, it seems that there's no way to prevent IDEA from inserting the project's output directory into the launch classpath.

If a developer accidentally builds the project with the Make button, then makes changes and then starts the app with the run/debug configuration, the old classes get picked up earlier in the classpath instead of the current classes.

This creates a very frustrating in which the application works as expected when run from the command line, but not when run through IDEA. The only way to detect that idea has inserted the project output diretory is in the class path is to look several thousand characters through the launch command line and find it.

To avoid these problems, there should be a checkbox in the run/debug configuration for "Include module output directory in classpath."



 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.