Mailing-List: contact buildr-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: buildr-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of antoine.contal@gmail.com
 designates 209.85.200.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=W5bH57afXel621de80//kSM1LqWOOtpDdbS17Zfo33+HcQPQ3dZe+Kgp/YmNLLnvzJ
         nYNiJmVpOucN9Hnkwy0nQaXGJAOTA2hQxGE606qecnfR47jU7d+Zd6usUxg8EiEZJCfZ
         mcS9EZAI71Onhh7kpjpbNeS6HB6DAs6Je2FaA=
Message-ID: <fbb63c440808051645q5294199aq9a71a9a5a5f03352@mail.gmail.com>
Date: Wed, 6 Aug 2008 01:45:10 +0200
From: lacton <lacton@users.sourceforge.net>
Sender: antoine.contal@gmail.com
To: buildr-user@incubator.apache.org
Subject: Re: [buildr] resources under eclipse
In-Reply-To: <5582dd3b0808051604q3ec1a0eg3bd1eb62c1f9c68c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <fbb63c440808051041icdfef7elc963914719d07ccd@mail.gmail.com>
	 <3de5d7d20808051131ja064cd6o4ffb0e186086082a@mail.gmail.com>
	 <fbb63c440808051546j4d95c1e1kb06e0d02552175a2@mail.gmail.com>
	 <5582dd3b0808051604q3ec1a0eg3bd1eb62c1f9c68c@mail.gmail.com>

I created issue BUILDR-123.

https://issues.apache.org/jira/browse/BUILDR-123

On Wed, Aug 6, 2008 at 1:04 AM, Alex Boisvert <boisvert@intalio.com> wrote:
> This is clearer to me now.  I think we should treat this as a bug of the
> Eclipse task.
>
> alex
>
>
>
> On Tue, Aug 5, 2008 at 3:46 PM, lacton <lacton@users.sourceforge.net> wrote:
>
>> Assaf,
>>
>> I think there was a misunderstanding. From your answer, I guess you
>> think I'm questioning the reason for separating target/resources and
>> target/classes. I'm not and I fully support this separation.
>>
>> My question is exactly the opposite. I'm wondering why the eclipse
>> task is not doing the same separation as buildr does.
>>
>> Here's an example.
>>
>> = What the eclipse task generates now =
>> <classpath>
>>  <classpathentry kind="src" path="src/main/java"
>> excluding="**/.svn/|**/CVS/"/>
>>  <classpathentry kind="src" path="src/main/resources"
>> excluding="**/.svn/|**/CVS/"/>
>>  <classpathentry kind="src" path="src/test/java"
>> output="target/test/classes" excluding="**/.svn/|**/CVS/"/>
>>  <classpathentry kind="src" path="src/test/resources"
>> output="target/test/classes" excluding="**/.svn/|**/CVS/"/>
>>  <classpathentry kind="var"
>> path="M2_REPO/jmock/jmock/1.2.0/jmock-1.2.0.jar"/>
>>  <classpathentry kind="var" path="M2_REPO/junit/junit/4.4/junit-4.4.jar"/>
>>  <classpathentry kind="output" path="target/classes"/>
>>  <classpathentry kind="con"
>> path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>> </classpath>
>>
>> = What I think would be more consistent =
>> <classpath>
>>  <classpathentry kind="src" path="src/main/java"
>> excluding="**/.svn/|**/CVS/"/>
>>  <classpathentry kind="src" path="src/main/resources"
>> output="target/resources" excluding="**/.svn/|**/CVS/"/>
>>  <classpathentry kind="src" path="src/test/java"
>> output="target/test/classes" excluding="**/.svn/|**/CVS/"/>
>>  <classpathentry kind="src" path="src/test/resources"
>> output="target/test/resources" excluding="**/.svn/|**/CVS/"/>
>>  <classpathentry kind="var"
>> path="M2_REPO/jmock/jmock/1.2.0/jmock-1.2.0.jar"/>
>>  <classpathentry kind="var" path="M2_REPO/junit/junit/4.4/junit-4.4.jar"/>
>>  <classpathentry kind="output" path="target/classes"/>
>>  <classpathentry kind="con"
>> path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>> </classpath>
>>
>> What do you think of that?
>>
>> On Tue, Aug 5, 2008 at 8:31 PM, Assaf Arkin <arkin@intalio.com> wrote:
>> > On Tue, Aug 5, 2008 at 10:41 AM, lacton <lacton@users.sourceforge.net>
>> wrote:
>> >> When building with buildr, resources are copied to target/resources or
>> >> target/test/resources. Yet, when running the eclipse task, the same
>> >> resources go to target/classes or target/test/classes.
>> >>
>> >> What are the reasons for this difference?
>> >
>> > Putting resources inside src/main/java doesn't work too well, it's
>> > hard to tell whether an HTML page or image is part of the
>> > documentation (used by javadoc), or resource that should be copied.
>> > So package(:jar) collects files from both target/classes and
>> > target/resources.
>> >
>> > But resources are not tied to Java specifically, while target/classes
>> > is specific to the JDK compilers.  A project can contain nothing but
>> > resources, or combine resources with some other binary target (not
>> > target/classes).  That's the rational for separating target/resources
>> > from target/[binary], where [binary] depends on the language you're
>> > using.
>> >
>> > If we wanted to route resources to target/classes, it would help to
>> > rephrase that as "would it work better if everything gets generated
>> > and packaged from target/code".  I'm using target/code because it
>> > helps frame the problem independently of Java, which is just one
>> > language.  The alternative is to have multiple target directories,
>> > which is what we have right now.
>> >
>> > Assaf
>> >
>> >>
>> >> Would someone be dissatisfied if I submitted a patch that would make
>> >> buildr and eclipse more consistent about this?
>> >>
>> >> --
>> >> Lacton
>> >>
>> >
>>
>> --
>> Lacton
>>
>

-- 
Lacton