I've just tried to build on both Linux and Windows with Maven 2.2.1 and
they both on fail "Apache Sling Launchpad Testing". Is it still
necessary to use the "tweaks" described in
https://issues.apache.org/jira/browse/SLING-830 to build Sling ?
2009-12-21 15:37:06.901::INFO: Started SelectChannelConnector @
0.0.0.0:8888
[INFO] [beddedLocalContainer] Jetty 6.x Embedded started on port [8888]
[INFO] [surefire:test {execution: surefire-integration-test}]
[INFO] Surefire report directory:
/home/pontus/workspaces/sling/sling-builder/launchpad/testing/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtDeleteTest
Checking if the required Sling services are started...
(base
URLs=http://localhost:8888/org.apache.sling.launchpad.testing-6-SNAPSHOT
and http://localhost:8888/org.apache.sling.launchpad.testing-6-SNAPSHOT)
Server does not seem to be ready, after 60000 msec, got the following
118
Exceptions:org.apache.sling.commons.testing.integration.HttpStatusCodeException:
Expected status code 302 for POST, got 404,
URL=http://localhost:8888/org.apache.sling.launchpad.testing-6-SNAPSHOT/WaitForSlingStartup/1261406231043
org.apache.sling.commons.testing.integration.HttpStatusCodeException:
Expected status code 302 for POST, got 404,
URL=http://localhost:8888/org.apache.sling.launchpad.testing-6-SNAPSHOT/WaitForSlingStartup/1261406231923
org.apache.sling.commons.testing.integration.HttpStatusCodeException:
Expected status code 302 for POST, got 404,
URL=http://localhost:8888/org.apache.sling.launchpad.testing-6-SNAPSHOT/WaitForSlingStartup/1261406232438
...
/Pontus
Felix Meschberger (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SLING-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793052#action_12793052 ]
Felix Meschberger commented on SLING-1252:
------------------------------------------
you might also check if 2.0.10 or 2.0.11 (RC)
Good idea. Will do. Thanks.
add an enforcer
We currently have such a rule to require 2.0.7 ...
Reactor build using Maven 2.0.9 creates non-functional launchpad base artifact
------------------------------------------------------------------------------
Key: SLING-1252
URL: https://issues.apache.org/jira/browse/SLING-1252
Project: Sling
Issue Type: Bug
Components: Launchpad
Affects Versions: Launchpad Base 2.1.0
Reporter: Felix Meschberger
When running a full (reactor) build with Maven 2.0.9, the launcher JAR artifact
of the launchpad/app bundle is built incorrectly and is not functional. As a
result, Sling cannot be started and thus the integration tests fail.
When running the reactor build with Maven 2.2.1, everything builds fine and
tests succeed.
Should we try to fix this issue or require Maven 2.2.1 in the reactor ?
