I have the classic integration testing structure under construction:
pre
test
post
My problem is that things can go wrong in pre. When they do, the build
fails, and then post doesn't run, and the early parts of pre that
succeed don't get cleaned up.
I could probably figure out to arrange for 'pre' never to fail the
build, but I don't want to run 'test' unless it succeeds.
I could make the junit tests in 'test' look for some cookie only
dropped if pre succeeds (in addition to forbidding pre from failing)
but that seems a crock.
What I wish is that the lifecycle was somehow wired to always run post
even if there's a failure in pre.
Could I make a custom lifecycle that has this characteristic?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
