Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » Files not being copied to output folder
Files not being copied to output folder [message #259083] Fri, 13 March 2009 20:16 Go to next message
Eclipse UserFriend
I have a wierd scenario where files are not being copied to the Java
build/output folder. In my project, the src folder is both the main source
folder and the default output folder. When I add another source folder
(test), my Java files get compiled and copied over to the output folder
just fine, but any other files (such as properties files) are ignored.
This is a problem.

This problem is easy to reproduce with a new eclipse project. Is there a
way to have multiple source folders, one of which is the output folder,
where ALL of the files in my source folders copy to the output folder?

(PS - As much as I hate having my src folder be the output folder, I can't
change it since we have various build scripts depending on that output
location.)
Re: Files not being copied to output folder [message #259128 is a reply to message #259083] Thu, 19 March 2009 11:06 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: eclipse-news.rizzoweb.com

On 3/13/2009 8:16 PM, Jonathan wrote:
> I have a wierd scenario where files are not being copied to the Java
> build/output folder. In my project, the src folder is both the main
> source folder and the default output folder. When I add another source
> folder (test), my Java files get compiled and copied over to the output
> folder just fine, but any other files (such as properties files) are
> ignored. This is a problem.
>
> This problem is easy to reproduce with a new eclipse project. Is there a
> way to have multiple source folders, one of which is the output folder,
> where ALL of the files in my source folders copy to the output folder?

Perhaps you're running into a conflict between the builder's desire to
clean the output location and its desire to put stuff there. I suggest
opening a bug about this scenario to see what kind of response that
garners. Be prepared that the answer might be "No going to support that."

> (PS - As much as I hate having my src folder be the output folder, I
> can't change it since we have various build scripts depending on that
> output location.)

Such scripts really aren't parameterized? Holy cow, how inept do you
have to be to write a script like that?!
Perhaps you can try some trickiness with linked folders in your Eclipse
project to work around that; make it think there are separate folders...

Hope this helps,
Eric
Re: Files not being copied to output folder [message #259166 is a reply to message #259128] Sat, 21 March 2009 00:22 Go to previous messageGo to next message
Eclipse UserFriend
Eric Rizzo wrote:

> Perhaps you're running into a conflict between the builder's desire to
> clean the output location and its desire to put stuff there.

Thanks for the response - I think you may be right.

> Such scripts really aren't parameterized?

Well they're not locked in stone (and they're not my scripts), but we have
a lot of code branches and developers utilizing these scripts, so making a
change would be a bit of a hassle.
Re: Files not being copied to output folder [message #259203 is a reply to message #259166] Mon, 23 March 2009 08:40 Go to previous message
Eclipse UserFriend
Originally posted by: eclipse-news.rizzoweb.com

On 3/21/2009 12:22 AM, Jonathan wrote:
> Eric Rizzo wrote:
>
>> Perhaps you're running into a conflict between the builder's desire to
>> clean the output location and its desire to put stuff there.
>
> Thanks for the response - I think you may be right.

Please do enter bug with as much detail as possible and post the bug
number/URL here. If you can, attach a small project that demonstrates
the problem to the bug report.


>> Such scripts really aren't parameterized?
>
> Well they're not locked in stone (and they're not my scripts), but we
> have a lot of code branches and developers utilizing these scripts, so
> making a change would be a bit of a hassle.

We all have to deal with "legacy" code (scripts are code, too) at some
point, I understand. It just sounded like what I'd consider a bug in the
script(s) if they are so rigid AND require a non-standard organization
in order to work. A bug that you, being an Eclipse user, are highly
motivated to fix. ;-)
Anyway, that point is unrelated to your issue with Eclipse, so...
Previous Topic:How to modify the field declaration with jdt
Next Topic:How to check if IType is abstract or not
Goto Forum:
  


Current Time: Mon Apr 21 01:49:22 EDT 2025

Powered by FUDForum. Page generated in 0.04376 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top