[
https://issues.apache.org/jira/browse/SLING-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253162#comment-14253162
]
Bertrand Delacretaz commented on SLING-4259:
--------------------------------------------
This is totally mysterious so far, that test works fine on my mac with java
version "1.7.0_45" and also at https://builds.apache.org/view/S-Z/view/Sling/
The core problem seems to be the org.apache.sling.junit.core bundle missing or
not active, so org.apache.sling.junit.scriptable cannot start.
I don't have a windows box, will ask on list of someone can try with a similar
environment as yours.
On your side you might try the following to verify that the set of bundles that
you get when building is valid:
* Start a standalone Sling instance from launchpad/builder - remove the sling
folder first and java -jar
target/org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar
* Mount http://localhost:8080 via WebDAV
* Create a folder named apps/test/install on that WebDAV mount and copy the
contents of testing/samples/integration-tests/target/sling/additional-bundles
in there
* At this point http://localhost:8080/apps/test/install.tidy.2.json should list
those bundles
* Check via http://localhost:8080/system/console/bundles that the
org.apache.sling.junit.scriptable bundle is active
In my build I get the following under target/sling/additional-bundles:
{code}
bndlib-1.50.0.jar
commons-io-1.4.jar
httpclient-osgi-4.1.2.jar
httpcore-osgi-4.1.2.jar
junit-4.11.jar
org.apache.felix.scr.annotations-1.9.8.jar
org.apache.sling.commons.json-2.0.6.jar
org.apache.sling.junit.core-1.0.10.jar
org.apache.sling.junit.performance-1.0.0-SNAPSHOT.jar
org.apache.sling.junit.remote-1.0.10.jar
org.apache.sling.junit.scriptable-1.0.8.jar
org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar
org.apache.sling.servlets.post-2.3.4.jar
org.apache.sling.testing.samples.failingtests-1.0.7-SNAPSHOT.jar
org.apache.sling.testing.samples.sampletests-1.0.7-SNAPSHOT.jar
slf4j-api-1.5.11.jar
slf4j-simple-1.5.11.jar
{code}
> Cannot run integration tests using the default configuration
> ------------------------------------------------------------
>
> Key: SLING-4259
> URL: https://issues.apache.org/jira/browse/SLING-4259
> Project: Sling
> Issue Type: Bug
> Affects Versions: Launchpad Builder 8
> Environment: Windows 7 64 bit, apache sling latest trunk version
> (8-SNAPSHOT), java 1.7 64-bit, maven 3.2.3
> Reporter: Andrei Zafiu
> Priority: Minor
> Attachments: error.log
>
>
> After a SVN checkout from the main trunk, all the tests from
> testing/samples/integration-tests will fail when using the "mvn clean
> install" command.
> The main error seems to be that the bundles are not properly installed:
> org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start
> (org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.sling.junit.scriptable [107]: Unable to resolve 107.0: missing
> requirement [107.0] osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.sling.junit)(version>=1.0.0)(!(version>=2.0.0))))
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.sling.junit.scriptable [107]: Unable to resolve 107.0: missing
> requirement [107.0] osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.sling.junit)(version>=1.0.0)(!(version>=2.0.0)))
> I have attached the error.log file from sling/default/logs after 2 runs, one
> with the "mvn clean install command" and one with the "mvn clean verify
> -DkeepJarRunning=true -Dhttp.port=8999" command.
> Additional information: If I start the sling launchpad from the sling trunk
> and set the properties in the pom.xml of the integration-test folder to use
> the launched instance instead of the bundled one then the test will pass.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
