Hi guys,
After doing some analysis of this, I have some good news. First, for the
analysis!
(Base)WicketTester, it's usages and dependencies is an interesting problem.
WicketTester has dependencies on classes in wicket-core (Component, Page, etc),
but then it's used in the unit tests that validate the very same classes that
it depends on. Going a step further, it also has WicketTesterTest, which tests
that WicketTester is valid (presumably before testing the validity of the rest
of wicket-core).
Also, wicket-parent defines that a test-jar is built for all children, first
added in 2008 and attributed to WICKET-1641[1]. But it doesn't make sense if
other projects are not depending on each other's tests.
I tried a few different solutions, including [2] and various permutations of
includes/excludes on that theme. That would probably work, but the wicket-core
POM is included in the wicket metadata, which is incorrect since in the final
artifacts, wicket-core-test should have a dependency on wicket-core. (This is
really a bug in maven-jar-plugin, since every test-jar should have a dependency
on the code that it tests....)
What I would propose is to get rid of the test-jars being created across the
project, then create an artifact with WicketTester in it. If there is a desire
for the POM of this new jar to depend on common and have a different
${project.name}, I could easily create a plugin that will do that.
Thoughts?
[1] https://issues.apache.org/jira/browse/WICKET-1641
[2] http://maven.apache.org/guides/mini/guide-attached-tests.html
