2008/9/16 Barrie Treloar <[EMAIL PROTECTED]> > On Tue, Sep 16, 2008 at 5:45 PM, Arnaud HERITIER <[EMAIL PROTECTED]> > wrote: > > I don't think we are using a mocking framework like easy mock but you can > > propose >
I had a look in InstallPluginsMojoTest and there seems to be some org.easymock.MockControl used there :-/. > > To be simplest you can create an integration test. > > You just have to create a maven project which reproduces the issue. > > I've been tinkering in the plugin lately, especially the test side of > things, so I thought I would have a look. > > InstallPluginsMojoTest was explicity excluded from the tests. > The code in there needed an overhaul to find a suitable jar and to > test it runs, so I've done that. > Now I can look at creating a unit test for this patch as well - > probably by using the jar that fails. > Hi Barrie, With the "jar that fails", the thing is I think it's proprietary(xdb.jar from the Oracle XDK).Though It's publicly downloadable (retrievable from oracle.com with a free account). So I guess it would be better to create a simple dumb jar with one or two classes, without any META-INF directory. Then this jar will be included in the project without any problem. I really think it's better. And obviously, I'll be happy to manually test the new version once the modification is applied. What do you think? Cheers. -- Baptiste <Batmat> MATHUS - http://batmat.net Save a tree, Eat a beaver!
