Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » "The resource is a duplicate ... and was not copied to the output folder"
"The resource is a duplicate ... and was not copied to the output folder" [message #759630] Tue, 29 November 2011 12:06 Go to next message
Jesper Eskilson is currently offline Jesper Eskilson
Messages: 131
Registered: July 2009
Senior Member
We're getting a bunch of these warnings when building headlessly in
Buckminster:

> The resource is a duplicate of src/com/iar/common/projectimport/ui/.svn/format and was not copied to the output folder

The warnings appears in projects which has multiple source folders. I
can work around the warnings by explicitly excluding the .svn folders
from the classpath in the project's .classpath file.

I tried to install the subclipse component in my headless Buckminster,
but that did not have any effect on this problem.

Shouldn't Buckminster (at least with subclipse support enabled) be aware
of .svn folders and automatically exclude them from build?

--
/Jesper
Re: "The resource is a duplicate ... and was not copied to the output folder" [message #759651 is a reply to message #759630] Tue, 29 November 2011 13:49 Go to previous message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-11-29 13:06, Jesper Eskilson wrote:
> We're getting a bunch of these warnings when building headlessly in Buckminster:
>
>> The resource is a duplicate of src/com/iar/common/projectimport/ui/.svn/format and was not copied to the output folder
>
> The warnings appears in projects which has multiple source folders. I can work around the warnings by explicitly
> excluding the .svn folders from the classpath in the project's .classpath file.
>
> I tried to install the subclipse component in my headless Buckminster, but that did not have any effect on this problem.
>
> Shouldn't Buckminster (at least with subclipse support enabled) be aware of .svn folders and automatically exclude them
> from build?
>
It should indeed. Not sure why it doesn't. A bugzilla with an example that reproduces this would be very much appreciated.

Regards,
Thomas Hallgren
Previous Topic:Exclude test classes from jar file
Next Topic:headless Buckminster build fails with "Unbound classpath container" on OSX Lion
Goto Forum:
  


Current Time: Mon Oct 20 11:25:10 GMT 2014

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

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