recent changes

[Benson Margulies <bi...@gmail.com>]

While I was working on splitting the systests, I set out to clean up
some other test-related stuff, perhaps rashly.

There is some test-only code in rt-core. I moved it from src/main/java
to src/test/java, and changed the POM for rt-core to build a test jar.
Then I 'fixed' the dependencies to have a scope=test dependency on
rt-core with classifier 'tests'.

For this to work, I had to change the fastinstall profile to use
maven.test.skip.exec instead of plain maven.test.skip. Elsewise, the
tests don't get compiled, and the jar doesn't happen, and the
dependent project refuses to build.

To really do this cleanly, someone aught to split up rt-core so that
the stuff that the test classes depend on was in one slice and the
other stuff that depends on the test classes was in another, but I
think I've run out of courage for the moment.

Re: recent changes

[Daniel Kulp <dk...@apache.org>]

I'm going to revert this change, at least for now until things are fully 
settled and we get the major stuctural changes in systest pushed back through 
the fixes.   Then, we can probably revisit it on trunk only.

The major issue is that those classes are really there to help ANYONE that is 
using CXF to write unit/system tests for their own work.   I know Progress 
uses it all over the place.   Thus, to move it out of rt-core will cause major 
headaches and not something I want to do on the 2.1/2.2 branches.   For trunk, 
it may make sense, but I'd like to get the rest of the refactoring of the test 
done first and merged before adding to my misery.   :-)

Dan




On Sun August 30 2009 8:51:51 pm Benson Margulies wrote:
> While I was working on splitting the systests, I set out to clean up
> some other test-related stuff, perhaps rashly.
>
> There is some test-only code in rt-core. I moved it from src/main/java
> to src/test/java, and changed the POM for rt-core to build a test jar.
> Then I 'fixed' the dependencies to have a scope=test dependency on
> rt-core with classifier 'tests'.
>
> For this to work, I had to change the fastinstall profile to use
> maven.test.skip.exec instead of plain maven.test.skip. Elsewise, the
> tests don't get compiled, and the jar doesn't happen, and the
> dependent project refuses to build.
>
> To really do this cleanly, someone aught to split up rt-core so that
> the stuff that the test classes depend on was in one slice and the
> other stuff that depends on the test classes was in another, but I
> think I've run out of courage for the moment.

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog