On Oct 6, 2008, at 11:57 AM, Levi Hoogenberg wrote:
<snip>
Defining src/main/resources as a source folder would solve the
problem? I guess you don't like this for performance reasons as you
have mentioned below? Another solution would be to change the
classpath order of the classpath folders.
Using src/main/resources as source folder would solve the issue,
but I don't like that (not just for performance reasons, but in
Eclipse a class folder is just conceptually the better option,
IMO). Changing the order helps as well (thought I tried that):
classpath entries that are defined last have the highest priority.
I'll add this to the JIRA issue I created.
I definitely see your point. I would like to hear what other Eclipse
users think about this. The Maven plugin for creating Eclipse files
creates source folders for resources folders. I don't have a clear
opinion yet. Basically the same discussion is valid for IntelliJ
(Unfortunately we don't have an IntelliJ plugin yet).
<snip>
I don't run manual builds that often, but do most things [testing,
running Jetty, usw ;)] from within Eclipse. So it would be great if
that could work with just a 'gradle eclipse' command.
Regards,
Levi
Just to be sure. As I understand it 'gradle eclipse' works in your
case, but you don't want resources to be a src folder, right?
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
