Hi,

I was bitten by this one again, trying to run Sling tests failed due
to a stale "sling" work folder, or more precisely gave different
results when run in the launchpad/testing folder vs. top of the source
code tree.

In my opinion, "mvn clean test" should have predictable results,
without taking previous runs into account.

Why did we move the "sling" folders from target/sling (where mvn clean
kills them) to siblings of src folders?
Is that on purpose, or a side effect of other changes?

I'd move them back, if people agree - having non-repeatable "mvn clean
test" cycles can be a big waste of people's time.

-Bertrand

Reply via email to