You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/02/22 13:22:13 UTC
[jira] [Closed] (SLING-1364) Inside a Bundle Project it is not
possible to executed an embedded Test with LaunchPad, Cargo and Jetty
[ https://issues.apache.org/jira/browse/SLING-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1364.
-----------------------------------
> Inside a Bundle Project it is not possible to executed an embedded Test with LaunchPad, Cargo and Jetty
> -------------------------------------------------------------------------------------------------------
>
> Key: SLING-1364
> URL: https://issues.apache.org/jira/browse/SLING-1364
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
> Environment: Mac, Java 6, Apache Sling from SVN Trunk
> Reporter: Andreas Schaefer
> Assignee: Justin Edelson
> Labels: bundle, integration, test
> Fix For: Maven Launchpad Plugin 2.0.6
>
> Attachments: pom copy.xml
>
>
> Inside a bundle project I could not start an integration test. Even though I could create a launchpad bundles firing up the embedded Web container (Cargo / Jetty) or even just Jetty fails.
> Steps to reproduce it:
> 1) Create a Servlet
> 2) Create a Bundle that contains the Servlet
> 3) Take the POM from launchpad / /testing and move these maven plugins inside the integration test profile: launchpad and war
> 4) Make sure the launchpad plugin is called after the JAR file is created (pre-integration-test)
> Running that with 'mvn -P jcrinstall-tests integration-test' fails because Sling is never launched even though launchpad-bundles is created and the war files seems to be fine.
> Running the same without Cargo and plain Jetty fails because now Sling is deployed inside "${basedir}/sling/_" and also the System Console is not coming up even though the sling home page does.
> Cheers - Andy
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira