|
|
| Re: Probes: invalid unicode [message #57883 is a reply to message #57789] |
Mon, 13 March 2006 19:00   |
Eclipse User |
|
|
|
Originally posted by: Navid_Mehregani_nmehrega.ca.ibm.com
This is a multipart message in MIME format.
--=_alternative 0068409C85257130_=
Content-Type: text/plain; charset="US-ASCII"
It's strange that you're getting compilation errors on Java comments.
Multiple source folders in a project is supported for probekit. I tried
creating probes in a project with three source files and it works fine.
The path you pasted looks a bit strange. I have the following path for my
probes:
/* probekit \<project_name>\src\myprobe.probe
*/
I'm glad you were able to resolve it.
Navid Mehregani
--=_alternative 0068409C85257130_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">It's strange that you're getting compilation
errors on Java comments. Multiple source folders in a project is
supported for probekit. I tried creating probes in a project with
three source files and it works fine. The path you pasted looks a
bit strange. I have the following path for my probes:</font>
<br>
<br><font size=2 face="sans-serif">/* probekit \<project_name>\src\myprobe.probe</font>
<br><font size=2 face="sans-serif">*/</font>
<br>
<br><font size=2 face="sans-serif">I'm glad you were able to resolve it.</font>
<br>
<br><font size=2 face="sans-serif">Navid Mehregani</font>
--=_alternative 0068409C85257130_=--
|
|
|
|
| Re: Probes: invalid unicode [message #58247 is a reply to message #57906] |
Tue, 14 March 2006 22:03 |
| Eclipse User |
|
|
|
Originally posted by: Navid_Mehregani_nmehrega.ca.ibm.com
This is a multipart message in MIME format.
--=_alternative 0078ED0185257131_=
Content-Type: text/plain; charset="US-ASCII"
>The strange path is due to the fact that our colleagues in development
maintain their SW split into "modules" in their favorite versioning system
and they also keep the actual code seperate from the corresponding unit
>test cases. The plugin we use to connect to that versioning system maps
these modules to multiple source directories in the form
This explains it. Probekit requires the user to define their probes in a
source folder that is a direct child of the project. This is a limitation
of probekit that will hopefully be removed in the future. Note that your
probes don't have to be defined in the same project that you want to
instrument your classes in. So here's what I would suggest:
Create a new project -> create a source folder in you project -> create
your probe(s) in the source folder and try instrumenting your classes with
the probe again.
Navid Mehregani
--=_alternative 0078ED0185257131_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="Arial">>The strange path is due to the fact that
our colleagues in development maintain their SW split into "modules"
in their favorite versioning system and they also keep the actual code
seperate from the corresponding unit >test cases. The plugin we use
to connect to that versioning system maps these modules to multiple source
directories in the form</font>
<br>
<br>
<br><font size=2 face="sans-serif">This explains it. Probekit requires
the user to define their probes in a source folder that is a direct child
of the project. This is a limitation of probekit that will hopefully
be removed in the future. Note that your probes don't have to be
defined in the same project that you want to instrument your classes in.
So here's what I would suggest:</font>
<br>
<br><font size=2 face="sans-serif">Create a new project -> create a
source folder in you project -> create your probe(s) in the source folder
and try instrumenting your classes with the probe again.<br>
<br>
Navid Mehregani</font>
<br>
<br>
--=_alternative 0078ED0185257131_=--
|
|
|
|
| Re: Probes: invalid unicode [message #58516 is a reply to message #58326] |
Wed, 15 March 2006 15:47 |
| Eclipse User |
|
|
|
Originally posted by: Navid_Mehregani_nmehrega.ca.ibm.com
This is a multipart message in MIME format.
--=_alternative 005679DF85257132_=
Content-Type: text/plain; charset="US-ASCII"
> I moved the probe file into that folder and that seems to have done the
trick: no more complaints re. unicode...
Yes, this'll have the same exact effect I suggested.
> Now - the next wish would of course be that one doesn't always have to
re-instrument (i.e. to reselect the corresponding classes) over and over
again after doing some changes in the app's source.
You should look forward to Dynamic Probekit in TPTP4.2. With dynamic
probekit, everything is done on-the-fly. The instrumentation is done in
memory so none of the files on disk need to be modified. You can simply
apply your probes in profile mode and let the framework do all the hard
work. There is no clean-up required at the end and you don't have to
instrument your classes manually every time. TPTP 4.2 is scheduled to be
released in June 2006, but you'll most likely be able to take advantage of
dynamic probekit by grabbing one of our stable 4.2 builds in mid to end of
April.
Navid Mehregani
--=_alternative 005679DF85257132_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="Arial">> I moved the probe file into that folder
and that seems to have done the trick: no more complaints re. unicode...</font>
<br>
<br><font size=2 face="Arial">Yes, this'll have the same exact effect I
suggested.</font>
<br>
<br><font size=2 face="Arial">> Now - the next wish would of course
be that one doesn't always have to re-instrument (i.e. to reselect the
corresponding classes) over and over again after doing some changes in
the app's source.</font>
<br>
<br><font size=2 face="Arial">You should look forward to Dynamic Probekit
in TPTP4.2. With dynamic probekit, everything is done on-the-fly.
The instrumentation is done in memory so none of the files on disk
need to be modified. You can simply apply your probes in profile
mode and let the framework do all the hard work. There is no clean-up
required at the end and you don't have to instrument your classes manually
every time. TPTP 4.2 is scheduled to be released in June 2006, but
you'll most likely be able to take advantage of dynamic probekit by grabbing
one of our stable 4.2 builds in mid to end of April.</font>
<br>
<br><font size=2 face="Arial">Navid Mehregani</font>
--=_alternative 005679DF85257132_=--
|
|
|
Powered by
FUDForum. Page generated in 0.06333 seconds
] 
Search
Help
Register
Login
Home
