Yeah, that cost me a fair bit of time when I tried starting using Sling
again last week. I patched launchpad/testing/pom.xml to clean some of
the files in that sling folder, but I suspect the right thing is to
delete the whole thing.
https://issues.apache.org/jira/browse/SLING-900
Jim
Carsten Ziegeler wrote:
Bertrand Delacretaz wrote:
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.
Don't know why we moved them - When running "mvn clean install" from the
root (multi project build) I even get a .sling folder in the root
directory which is totally confusing. So big +1 to get this sorted out
properly, which means create the folders in the modules they are created
from under "target".
Carsten
