On Sat, Aug 24, 2013 at 2:14 PM, Minh Nguyen <
minh.9...@gmail.com> wrote:
> Thanks for creating this project, it appears to be the easiest option for
> creating multithreaded testing scenarios. I have a couple of questions:
>
> Has there been any effort towards creating a Maven project of version 0.20?
> I imagine the project could gain a lot more visibility / adoption if it was
> easily accessible through Maven (a few lines to add to a pom.xml rather than
> the larger effort of adding it to an Ant script). If this seems worthwhile,
> I would like to volunteer to assist
Hi Minh,
Someone else had recently suggested this, and sent a sample pom.xml.
See
http://code.google.com/p/thread-weaver/issues/detail?id=8 .
There was some issue about whether or not objenesis was available as a
Maven jar - see the last comment. I'm afraid I know very little about
Maven, having used Ant or proprietary build systems in the past.
> I've been trying to have my mainThread and secondaryThread interweave using
> "Scripts" as described in the Wiki's example
> (
https://code.google.com/p/thread-weaver/wiki/UsersGuide) but encounter "no
> instrumented object" errors. I actually even copied the same example (with a
> minor typo edit) and experienced the same error. I plan to dive into the
> code a little bit but any guidance would be greatly appreciated.
Hmm. It should work. Do you have a traceback? And sample code that you're using?
You do still need to use the ThreadWeaver test annotations, rather
than direct test cases. The way ThreadWeaver works is that it reloads
the classes that you are testing using a custom classloader. (It has
to do this in order to instrument them, and add the breakpoints.) So
you can't call ThreadWeaver for a standard JUnit method - you need to
use ThreadWeaver's own annotations.
Please note that I will be on vacation tomorrow for a couple of weeks,
with limited email access, so I may be slow in reponding.
Alasdair