[Clirr-devel] maven plugin is working now
Status: Alpha
Brought to you by:
lkuehne
From: <lak...@t-...> - 2004-08-21 12:00:41
|
Hi guys, I finally had the time to dig into Vincent's ClassCastException, it was a problem in InterfaceSetCheck where we added Strings to a Set and then expected it to contain JavaClass objects. I have also made a small change in the plugin code to ensure that the baseline jar is downloaded only once, not every time the clirr goal is running. After adding <versions> to the POM I was able to run "maven clirr" without any problems on commons-collections. Vincent, could you please retest with Cactus? Open issues I see with the Maven plugin: * dependencies are not considered (<[new/old]ClassPath> subelements of the clirr Ant task), I don't know how things work out in the plugin if 3rd party classes appear in method signatures of the code clirr wants to check. * clirr:check calls jar:jar. In typical use cases (like adding clirr as a pregoal for jar:install) that will run jar:jar twice. Cheers, Lars |