Hi Brian, The main user of JUnit in production is WicketTester.
About ApacheLicenceTest - Jeremy tried to replace it with com.mycila.maven-license-plugin:maven-license-plugin in 1.4.x but didn't finish it. On Sun, Aug 14, 2011 at 6:04 AM, Brian Topping <[email protected]> wrote: > oic, there's a ApacheLicenseHeaderTest in every project. > > I'm in the process of isolating the junit.framework package to a test > dependency so JUnit is not a dependency in production code. If it were made > into a plugin, the instances of per-project ApacheLicenseHeader configuration > would need to come from the POM. That's kind of where it belongs (it's part > of the build, after all), but it could easily be made into a configuration > file that resides in each project to keep the POMs clean. > > Failing that, creating a separate module to contain o.a.w.util.license that > is a test scope dependency would be a last resort. > > I'm going to go ahead and create a plugin that reads a configuration file in > each project. Some of the configurations are lengthy > (org.apache.wicket.util.license.ApacheLicenceHeaderTest). That would be a > mess in the pom. > > > On Aug 13, 2011, at 10:09 PM, Brian Topping wrote: > >> Hi all, >> >> Does anyone know why org.apache.wicket.util.license is in wicket-util's >> production source directory? I'm guessing it has something to do with the >> desire to get the license plugin to fire every time a build is made, but if >> that's the case, it would be better handled as a Maven plugin. It's not a >> test and it's not a part of any public API. >> >> I'm happy to create a plugin if that's the case, please let me know. >> >> Cheers, Brian > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
