groovy

GroovyBuilder option to copy groovy source into bin dir instead compiling it

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.5.1
  • Component/s: None
  • Labels:
    None
  • Environment:
    Eclipse IDE
  • Number of attachments :
    0

Description

Actually the groovy eclipse plugin adds a builder for the project builders list and compile any groovy file into the bin dest dir.

Would be super if we could configure the Groovy builder to COPY the scripts into the bin dest dir because in many cases we are not interested on the compiled version because we are using scripts to extend our app on the fly.
(copying is important to allow during the debug to just use the classloader to load the script file as a resource)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Martin Novák added a comment -

I would like to see some option to disable groovy code generation per project basis as well. As I remember the previous version didn't compile files unless you really confirmed it in some dialog. The newest version asked me once, and compiles every groovy file in every project. And it really slows down eclipse compilation when my project has two/three groovy scripts, and 500 java files...

Show
Martin Novák added a comment - I would like to see some option to disable groovy code generation per project basis as well. As I remember the previous version didn't compile files unless you really confirmed it in some dialog. The newest version asked me once, and compiles every groovy file in every project. And it really slows down eclipse compilation when my project has two/three groovy scripts, and 500 java files...
Hide
Permalink
Thorsten Kamann added a comment -

For now you can disable the compilation per workspace and per project.

If this isn't the goal of this issue please feel free to reopen this issue.

Show
Thorsten Kamann added a comment - For now you can disable the compilation per workspace and per project. If this isn't the goal of this issue please feel free to reopen this issue.
Hide
Permalink
Paul King added a comment -

close off release 1.5.4

Show
Paul King added a comment - close off release 1.5.4
Hide
Permalink
Berno Langer added a comment -

I have a project, that needs the groovy files instead of the compiled class files.

Adding the source folders to the classpath isn't an option for me, because some external tools rely on the fact that the groovy files will be stored inside the bin directory - as it will be on the productive system later.

In other words, I would like to use the Groovy-Editor with autocompletion and all the useful stuff, but the result should be the unmodified groovy file in the bin directory.

I can't find any way to solve this problem. It doesn't matter whether the Groovy feature is turned on or off.

Show
Berno Langer added a comment - I have a project, that needs the groovy files instead of the compiled class files. Adding the source folders to the classpath isn't an option for me, because some external tools rely on the fact that the groovy files will be stored inside the bin directory - as it will be on the productive system later. In other words, I would like to use the Groovy-Editor with autocompletion and all the useful stuff, but the result should be the unmodified groovy file in the bin directory. I can't find any way to solve this problem. It doesn't matter whether the Groovy feature is turned on or off.
Hide
Permalink
blackdrag blackdrag added a comment -

Berno, I suggest you move this into a new issue. But I suggest even more to discuss this topic on the groovy user list first.

Show
blackdrag blackdrag added a comment - Berno, I suggest you move this into a new issue. But I suggest even more to discuss this topic on the groovy user list first.

People

  • Assignee:
    Scott Hickey
    Reporter:
    Samuel
Vote (2)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: