On Oct 6, 2008, at 1:16 PM, Levi Hoogenberg wrote:
On Mon, Oct 6, 2008 at 12:28 PM, Hans Dockter <[EMAIL PROTECTED]>
wrote:
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).
I'm interested in what others think as well - if I'm the only one
who likes the class folder functionality, maybe I'm the one who
should change his process.
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?
That's right (see http://jira.codehaus.org/browse/GRADLE-253).
Although what you said about modified resources got me thinking -
how do you (or other Eclipse users who might read this) handle the
filtering case you described when you're running tests inside Eclipse?
In our special case we have the following situation. We automatically
generate a properties file as part of the build and put it in the
build/classes folder. This is used by the production code. We have a
dummy version of this property file in the src/test/resources folder.
Therefore when the unit tests are running this resource exists and we
can check against defined values. When we run Gradle or the
integration tests from our IDE the dummy version is also used. In our
case this is fine (as it contains only versioning information). In
other more complicated cases I guess you have to customize the
Eclipse builder. But I never had to deal with such a situation.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
