Home » Eclipse Projects » Eclipse Platform » Problem with builders not copying .xml files to bin directory
| Problem with builders not copying .xml files to bin directory [message #327763] |
Wed, 30 April 2008 22:50  |
Eclipse User |
|
|
|
Originally posted by: david_whiteman.us.ibm.com
Has anyone noticed in M5 or M6 a problem where if you have an .xml file
in the src directory of a Java project, it does not get copied to the
bin directory by the java builder? It seems any other file does get
copied except .xml files. I tried files named "foo", "foo.java",
"foo.xsd", "foo.xma", and "foo.xml", and the only one that was not
transferred to "bin" was foo.xml. Is this a known bug? If not, where
should I report it?
I am using the Eclipse IDE for Java Developers, Ganymede M6 build, on
Windows.
Thanks in advance,
David
|
|
|
| Re: Problem with builders not copying .xml files to bin directory [message #327770 is a reply to message #327763] |
Wed, 30 April 2008 23:12  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
David Whiteman wrote:
> Has anyone noticed in M5 or M6 a problem where if you have an .xml file
> in the src directory of a Java project, it does not get copied to the
> bin directory by the java builder? It seems any other file does get
> copied except .xml files. I tried files named "foo", "foo.java",
> "foo.xsd", "foo.xma", and "foo.xml", and the only one that was not
> transferred to "bin" was foo.xml. Is this a known bug? If not, where
> should I report it?
There is a preference for controlling what files NOT to copy to the
output directory during a build - maybe XML files are included there
somehow. You can check the Preference dialog - enter "filtered" (without
quotes) into the search field at the top of the dialog.
Report back if you find *.xml or something similar there, or not.
Eric
|
|
|
| Re: Problem with builders not copying .xml files to bin directory [message #327792 is a reply to message #327770] |
Thu, 01 May 2008 20:24 |
| Eclipse User |
|
|
|
Originally posted by: david_whiteman.us.ibm.com
Eric Rizzo wrote:
> David Whiteman wrote:
>> Has anyone noticed in M5 or M6 a problem where if you have an .xml
>> file in the src directory of a Java project, it does not get copied
>> to the bin directory by the java builder? It seems any other file
>> does get copied except .xml files. I tried files named "foo",
>> "foo.java", "foo.xsd", "foo.xma", and "foo.xml", and the only one that
>> was not transferred to "bin" was foo.xml. Is this a known bug? If
>> not, where should I report it?
>
> There is a preference for controlling what files NOT to copy to the
> output directory during a build - maybe XML files are included there
> somehow. You can check the Preference dialog - enter "filtered" (without
> quotes) into the search field at the top of the dialog.
> Report back if you find *.xml or something similar there, or not.
>
> Eric
That's exactly what it was. Thanks, Eric! I wasn't aware of that
change. Seems to be a pretty arbitrary list of file types that are
excluded. We have .xml files that are test resources in a JUnit
project, and they are accessed using the class loader, so that's why we
need them copied to the bin directory. Fortunately, you can configure
this preference on a per-project basis.
David
|
|
|
| Re: Problem with builders not copying .xml files to bin directory [message #327808 is a reply to message #327792] |
Fri, 02 May 2008 13:54 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
David Whiteman wrote:
> Eric Rizzo wrote:
>> David Whiteman wrote:
>>> Has anyone noticed in M5 or M6 a problem where if you have an .xml
>>> file in the src directory of a Java project, it does not get copied
>>> to the bin directory by the java builder? It seems any other file
>>> does get copied except .xml files. I tried files named "foo",
>>> "foo.java", "foo.xsd", "foo.xma", and "foo.xml", and the only one
>>> that was not transferred to "bin" was foo.xml. Is this a known bug?
>>> If not, where should I report it?
>>
>> There is a preference for controlling what files NOT to copy to the
>> output directory during a build - maybe XML files are included there
>> somehow. You can check the Preference dialog - enter "filtered"
>> (without quotes) into the search field at the top of the dialog.
>> Report back if you find *.xml or something similar there, or not.
>>
>> Eric
>
> That's exactly what it was. Thanks, Eric! I wasn't aware of that
> change. Seems to be a pretty arbitrary list of file types that are
> excluded. We have .xml files that are test resources in a JUnit
> project, and they are accessed using the class loader, so that's why we
> need them copied to the bin directory. Fortunately, you can configure
> this preference on a per-project basis.
It's not really arbitrary - I believe that plugins contribute to that
list files that they "know" should not generally be included in the
build output. For example, EMF adds *.ecore to the list so your model
source does not get copied.
Anyway, it is strange that XML files ended up in your list. I would
definitely consider that a bug, but the trick is finding out how it got
there. Is there any chance you accidentally did it or someone else did
it per-project and checked in their .settings files? If you're pretty
sure that's not the case, you should look at the plugins you have
installed and try to figure out which one might have done it.
I checked both my 3.3.x and my 3.4M6 installations and XML was not
included in the list (I have quite a few plugins installed, including
EMF, WTP, DTP, and much more), so it must be something else you have
installed.
Eric
|
|
|
| Re: Problem with builders not copying .xml files to bin directory [message #332201 is a reply to message #327808] |
Thu, 09 October 2008 23:12 |
 Brett Randall
Messages: 17
Registered: July 2009 |
Junior Member |
|
|
Eric Rizzo wrote:
> David Whiteman wrote:
>> Eric Rizzo wrote:
>>> David Whiteman wrote:
>>>> Has anyone noticed in M5 or M6 a problem where if you have an .xml
>>>> file in the src directory of a Java project, it does not get copied
>>>> to the bin directory by the java builder? It seems any other file
>>>> does get copied except .xml files. I tried files named "foo",
>>>> "foo.java", "foo.xsd", "foo.xma", and "foo.xml", and the only one
>>>> that was not transferred to "bin" was foo.xml. Is this a known
>>>> bug? If not, where should I report it?
>>>
>>> There is a preference for controlling what files NOT to copy to the
>>> output directory during a build - maybe XML files are included there
>>> somehow. You can check the Preference dialog - enter "filtered"
>>> (without quotes) into the search field at the top of the dialog.
>>> Report back if you find *.xml or something similar there, or not.
>>>
>>> Eric
>>
>> That's exactly what it was. Thanks, Eric! I wasn't aware of that
>> change. Seems to be a pretty arbitrary list of file types that are
>> excluded. We have .xml files that are test resources in a JUnit
>> project, and they are accessed using the class loader, so that's why
>> we need them copied to the bin directory. Fortunately, you can
>> configure this preference on a per-project basis.
>
> It's not really arbitrary - I believe that plugins contribute to that
> list files that they "know" should not generally be included in the
> build output. For example, EMF adds *.ecore to the list so your model
> source does not get copied.
> Anyway, it is strange that XML files ended up in your list. I would
> definitely consider that a bug, but the trick is finding out how it got
> there. Is there any chance you accidentally did it or someone else did
> it per-project and checked in their .settings files? If you're pretty
> sure that's not the case, you should look at the plugins you have
> installed and try to figure out which one might have done it.
> I checked both my 3.3.x and my 3.4M6 installations and XML was not
> included in the list (I have quite a few plugins installed, including
> EMF, WTP, DTP, and much more), so it must be something else you have
> installed.
>
> Eric
This exact problem has just happened to me, I suspect at the time that I
picked up the 3.4.1 M20080911-1700 and other updates, but I too have a
bunch of additional plugins on-top of the base Ganymede, so I don't know
which one to point the finger at.
Thanks for posting this and the solution.
Brett
|
|
|
| Re: Problem with builders not copying .xml files to bin directory [message #332205 is a reply to message #332201] |
Fri, 10 October 2008 13:27 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Note: copying this to the JDT newsgroup since this is a JDT feature
we're talking about.
JDT gurus: can you help us track down who is putting *.xml in the
"Filtered Resources" list for the JDT builder? I thought it would be an
extension point that we could look for, but I couldn't find any such
extension point. Looking at JavaBuildPreferencePage I tried to decipher
how that preference gets pre-populated by pulgins but I got lost.
Any hints?
Eric
Brett Randall wrote:
> Eric Rizzo wrote:
>> David Whiteman wrote:
>>> Eric Rizzo wrote:
>>>> David Whiteman wrote:
>>>>> Has anyone noticed in M5 or M6 a problem where if you have an .xml
>>>>> file in the src directory of a Java project, it does not get
>>>>> copied to the bin directory by the java builder? It seems any
>>>>> other file does get copied except .xml files. I tried files named
>>>>> "foo", "foo.java", "foo.xsd", "foo.xma", and "foo.xml", and the
>>>>> only one that was not transferred to "bin" was foo.xml. Is this a
>>>>> known bug? If not, where should I report it?
>>>>
>>>> There is a preference for controlling what files NOT to copy to the
>>>> output directory during a build - maybe XML files are included there
>>>> somehow. You can check the Preference dialog - enter "filtered"
>>>> (without quotes) into the search field at the top of the dialog.
>>>> Report back if you find *.xml or something similar there, or not.
>>>>
>>>> Eric
>>>
>>> That's exactly what it was. Thanks, Eric! I wasn't aware of that
>>> change. Seems to be a pretty arbitrary list of file types that are
>>> excluded. We have .xml files that are test resources in a JUnit
>>> project, and they are accessed using the class loader, so that's why
>>> we need them copied to the bin directory. Fortunately, you can
>>> configure this preference on a per-project basis.
>>
>> It's not really arbitrary - I believe that plugins contribute to that
>> list files that they "know" should not generally be included in the
>> build output. For example, EMF adds *.ecore to the list so your model
>> source does not get copied.
>> Anyway, it is strange that XML files ended up in your list. I would
>> definitely consider that a bug, but the trick is finding out how it
>> got there. Is there any chance you accidentally did it or someone else
>> did it per-project and checked in their .settings files? If you're
>> pretty sure that's not the case, you should look at the plugins you
>> have installed and try to figure out which one might have done it.
>> I checked both my 3.3.x and my 3.4M6 installations and XML was not
>> included in the list (I have quite a few plugins installed, including
>> EMF, WTP, DTP, and much more), so it must be something else you have
>> installed.
>>
>> Eric
>
> This exact problem has just happened to me, I suspect at the time that I
> picked up the 3.4.1 M20080911-1700 and other updates, but I too have a
> bunch of additional plugins on-top of the base Ganymede, so I don't know
> which one to point the finger at.
>
> Thanks for posting this and the solution.
>
> Brett
|
|
|
| Re: Problem with builders not copying .xml files to bin directory [message #332209 is a reply to message #332205] |
Fri, 10 October 2008 15:30 |
Jerome Lanneluc
Messages: 572
Registered: July 2009 |
Senior Member |
|
|
It might be TPTP. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=230050
Jerome
Eric Rizzo wrote:
> Note: copying this to the JDT newsgroup since this is a JDT feature
> we're talking about.
>
> JDT gurus: can you help us track down who is putting *.xml in the
> "Filtered Resources" list for the JDT builder? I thought it would be an
> extension point that we could look for, but I couldn't find any such
> extension point. Looking at JavaBuildPreferencePage I tried to decipher
> how that preference gets pre-populated by pulgins but I got lost.
> Any hints?
>
> Eric
>
>
> Brett Randall wrote:
>> Eric Rizzo wrote:
>>> David Whiteman wrote:
>>>> Eric Rizzo wrote:
>>>>> David Whiteman wrote:
>>>>>> Has anyone noticed in M5 or M6 a problem where if you have an .xml
>>>>>> file in the src directory of a Java project, it does not get
>>>>>> copied to the bin directory by the java builder? It seems any
>>>>>> other file does get copied except .xml files. I tried files named
>>>>>> "foo", "foo.java", "foo.xsd", "foo.xma", and "foo.xml", and the
>>>>>> only one that was not transferred to "bin" was foo.xml. Is this a
>>>>>> known bug? If not, where should I report it?
>>>>>
>>>>> There is a preference for controlling what files NOT to copy to the
>>>>> output directory during a build - maybe XML files are included
>>>>> there somehow. You can check the Preference dialog - enter
>>>>> "filtered" (without quotes) into the search field at the top of the
>>>>> dialog.
>>>>> Report back if you find *.xml or something similar there, or not.
>>>>>
>>>>> Eric
>>>>
>>>> That's exactly what it was. Thanks, Eric! I wasn't aware of that
>>>> change. Seems to be a pretty arbitrary list of file types that are
>>>> excluded. We have .xml files that are test resources in a JUnit
>>>> project, and they are accessed using the class loader, so that's why
>>>> we need them copied to the bin directory. Fortunately, you can
>>>> configure this preference on a per-project basis.
>>>
>>> It's not really arbitrary - I believe that plugins contribute to that
>>> list files that they "know" should not generally be included in the
>>> build output. For example, EMF adds *.ecore to the list so your model
>>> source does not get copied.
>>> Anyway, it is strange that XML files ended up in your list. I would
>>> definitely consider that a bug, but the trick is finding out how it
>>> got there. Is there any chance you accidentally did it or someone
>>> else did it per-project and checked in their .settings files? If
>>> you're pretty sure that's not the case, you should look at the
>>> plugins you have installed and try to figure out which one might have
>>> done it.
>>> I checked both my 3.3.x and my 3.4M6 installations and XML was not
>>> included in the list (I have quite a few plugins installed, including
>>> EMF, WTP, DTP, and much more), so it must be something else you have
>>> installed.
>>>
>>> Eric
>>
>> This exact problem has just happened to me, I suspect at the time that
>> I picked up the 3.4.1 M20080911-1700 and other updates, but I too have
>> a bunch of additional plugins on-top of the base Ganymede, so I don't
>> know which one to point the finger at.
>>
>> Thanks for posting this and the solution.
>>
>> Brett
|
|
|
| Re: Problem with builders not copying .xml files to bin directory [message #332243 is a reply to message #332205] |
Tue, 14 October 2008 10:29 |
| Eclipse User |
|
|
|
Originally posted by: mauro.molinari.cardinis.com
Eureka, someone having this problem at last!!!!
A co-worker of mine periodically encounters this problem and has to
rebuild his workspace from scratch, because we couldn't understand what
was the source of the problem until now. I made a search in Bugzilla
three or four times without success! :-(
Mauro.
|
|
|
Goto Forum:
Current Time: Thu Jun 27 19:40:02 GMT 2024
Powered by FUDForum. Page generated in 0.03508 seconds |
] 
Search
Help
Register
Login
Home
