Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » TPTP and java compiler's "filtered resources"
TPTP and java compiler's "filtered resources" [message #130044] Wed, 14 May 2008 04:37
Vadim Dmitriev is currently offline Vadim Dmitriev
Messages: 74
Registered: July 2009
Member
Hi!

A little background first: project, I'am currently working on, tend to
keep configuration XML files on the build path (/src/).
Eventually I decided to run profiling on that project. Some time after
that I began running into issues with configs not being updated in the
/bin/ folder (it seemed that time that these configs were not parsed
correctly). After hours of debugging I invoked "clean" on the project and
on the next run I got (surprise!) exception that configs cannot be found.
It were a good news after all since there were no problems with our code.
I looked here and there in the settings and found that TPTP silently added
multiple exclusions to the java compiler's "output folder"->"filtered
resources". Aside from TPTP-specific (as I get it) extensions like
*.testsuite, *.deploy, *.location, *.execution, *.datapool there were some
more common *.html and *.svg and even more common *.xml. Last one filter
actually prevented our configs from being updated in the /bin/ folder on
the incremental build in the first place.

Maybe it worth mentioning somewhere that TPTP will modify workspace-wide
java compiler preferences on first profiling attempt? Or maybe it will be
better to make exclusions more precise (for example, replace "*.xml" with
"prefix*suffix.xml") since TPTP constantly updates filtered resources with
*.xml pattern.

Thanks :)
Previous Topic:Agent Controller fails to start on linux
Next Topic:Exec time profiling using CPU samples?
Goto Forum:
  


Current Time: Sat Aug 23 09:27:32 EDT 2014

Powered by FUDForum. Page generated in 0.01573 seconds