[ https://issues.apache.org/jira/browse/SLING-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468794#comment-16468794 ]
Bertrand Delacretaz commented on SLING-7659: -------------------------------------------- {quote}Would it be acceptable to exit the integration test with an error if the folder already exists? {quote} Why not, but cleaning up is more developer friendly... > Test using o.a.s.testing.paxexam block if run without "mvn clean" > ----------------------------------------------------------------- > > Key: SLING-7659 > URL: https://issues.apache.org/jira/browse/SLING-7659 > Project: Sling > Issue Type: Bug > Components: Testing > Affects Versions: Testing PaxExam 2.0.0 > Reporter: Bertrand Delacretaz > Priority: Minor > Attachments: testing.log > > > This happens for (at least) the following modules: > * sling-org-apache-sling-commons-html which uses o.a.s.testing.paxexam 2.0.0 > * sling-org-apache-sling-resource-presence which uses o.a.s.testing.paxexam > 0.0.4 > The integration tests work fine with {{mvn clean install}} but running {{mvn > install}} right after that causes the tests to hang and time out (after > approximately 6 minutes). > Deleting {{target/paxexam}} folder before running {{mvn install}} fixes the > issue, so it's linked to existing OSGi state apparently. > I'll attach a {{testing.log}}, I don't see any obvious clues in it but the > tests block after this line: > {code:java} > 2018-05-09 11:59:56,003 DEBUG [BundleWatcher: 1] o.o.p.e.r.e.i.Probe > [Parser.java : 64] Registering Service: org.ops4j.pax.exam.ProbeInvoker > with Probe-Signature="PaxExam-d4e46627-3b02-462a-aa46-883ce54e3f9f" > and expression= > "org.apache.sling.commons.html.it.TagsoupHtmlParserIT;testFeaturesConfiguration" > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)