[jira] [Updated] (SLING-2657) Unable to set context path with launchpad jar

2013-02-16 Thread Robert Munteanu (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2657:
---

Remaining Estimate: 0h
 Original Estimate: 0h

> Unable to set context path with launchpad jar
> -
>
> Key: SLING-2657
> URL: https://issues.apache.org/jira/browse/SLING-2657
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Affects Versions: Launchpad Base 2.4.0
>Reporter: Robert Munteanu
> Attachments: contextpath.zip
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> When building a launchpad jar and configuring it to use the http jetty bundle 
> as of revision 1407407 the -r parameter does not cause the context path to be 
> set.
> When launching the launchpad jar with 
> java -jar target/contextpath-0.0.SNAPSHOT.jar -r /ctx
> I get the following log output
> 11.11.2012 15:04:45.265 *INFO * [main] Setting sling.home=sling (default)
> 11.11.2012 15:04:45.266 *INFO * [main] Starting Apache Sling in 
> /mnt/md/robert/workspace/contextpath/sling
> 11.11.2012 15:04:45.276 *INFO * [main] Checking launcher JAR in folder 
> /mnt/md/robert/workspace/contextpath/sling
> 11.11.2012 15:04:45.289 *INFO * [main] Existing launcher is up to date, using 
> it: 2.4.0 (org.apache.sling.launchpad.base.jar)
> 11.11.2012 15:04:45.291 *INFO * [main] Loading launcher class 
> org.apache.sling.launchpad.base.app.MainDelegate from 
> org.apache.sling.launchpad.base.jar
> 11.11.2012 15:04:45.307 *INFO * [main] Setting 
> sling.launchpad=/mnt/md/robert/workspace/contextpath/sling
> 11.11.2012 15:04:45.307 *INFO * [main] Setting 
> org.apache.felix.http.context_path=/ctx
> 11.11.2012 15:04:45.307 *INFO * [main] Starting launcher ...
> 11.11.2012 15:04:45.309 *INFO * [main] HTTP server port: 8080
> SLF4J: The following loggers will not work becasue they were created
> SLF4J: during the default configuration phase of the underlying logging 
> system.
> SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger
> SLF4J: org.apache.sling.commons.log.internal.LogServiceFactory
> 2012-11-11 15:04:46.079:INFO:oejs.Server:jetty-7.x.y-SNAPSHOT
> 2012-11-11 15:04:46.131:INFO:oejsh.ContextHandler:started 
> o.e.j.s.ServletContextHandler{/,null}
> 2012-11-11 15:04:46.368:INFO:oejs.AbstractConnector:Started 
> SelectChannelConnector@0.0.0.0:8080
> 2012-11-11 15:04:46.467:INFO:oejsh.ContextHandler:stopped 
> o.e.j.s.ServletContextHandler{/,null}
> 2012-11-11 15:04:46.520:INFO:oejs.Server:jetty-7.x.y-SNAPSHOT
> 2012-11-11 15:04:46.520:INFO:oejsh.ContextHandler:started 
> o.e.j.s.ServletContextHandler{/,null}
> 2012-11-11 15:04:46.560:INFO:oejs.AbstractConnector:Started 
> SelectChannelConnector@0.0.0.0:8080
> 11.11.2012 15:04:53.357 *INFO * [main] Startup completed

--
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


[jira] [Updated] (SLING-2657) Unable to set context path with launchpad jar

2012-11-11 Thread Robert Munteanu (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2657:
---

Attachment: contextpath.zip

To reproduce the problem with the attached contextpath.zip:

* unzip the archive
* run mvn package
* run java -jar target/contextpath-0.0.1-SNAPSHOT.jar 


> Unable to set context path with launchpad jar
> -
>
> Key: SLING-2657
> URL: https://issues.apache.org/jira/browse/SLING-2657
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Affects Versions: Launchpad Base 2.4.0
>Reporter: Robert Munteanu
> Attachments: contextpath.zip
>
>
> When building a launchpad jar and configuring it to use the http jetty bundle 
> as of revision 1407407 the -r parameter does not cause the context path to be 
> set.
> When launching the launchpad jar with 
> java -jar target/contextpath-0.0.SNAPSHOT.jar -r /ctx
> I get the following log output
> 11.11.2012 15:04:45.265 *INFO * [main] Setting sling.home=sling (default)
> 11.11.2012 15:04:45.266 *INFO * [main] Starting Apache Sling in 
> /mnt/md/robert/workspace/contextpath/sling
> 11.11.2012 15:04:45.276 *INFO * [main] Checking launcher JAR in folder 
> /mnt/md/robert/workspace/contextpath/sling
> 11.11.2012 15:04:45.289 *INFO * [main] Existing launcher is up to date, using 
> it: 2.4.0 (org.apache.sling.launchpad.base.jar)
> 11.11.2012 15:04:45.291 *INFO * [main] Loading launcher class 
> org.apache.sling.launchpad.base.app.MainDelegate from 
> org.apache.sling.launchpad.base.jar
> 11.11.2012 15:04:45.307 *INFO * [main] Setting 
> sling.launchpad=/mnt/md/robert/workspace/contextpath/sling
> 11.11.2012 15:04:45.307 *INFO * [main] Setting 
> org.apache.felix.http.context_path=/ctx
> 11.11.2012 15:04:45.307 *INFO * [main] Starting launcher ...
> 11.11.2012 15:04:45.309 *INFO * [main] HTTP server port: 8080
> SLF4J: The following loggers will not work becasue they were created
> SLF4J: during the default configuration phase of the underlying logging 
> system.
> SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger
> SLF4J: org.apache.sling.commons.log.internal.LogServiceFactory
> 2012-11-11 15:04:46.079:INFO:oejs.Server:jetty-7.x.y-SNAPSHOT
> 2012-11-11 15:04:46.131:INFO:oejsh.ContextHandler:started 
> o.e.j.s.ServletContextHandler{/,null}
> 2012-11-11 15:04:46.368:INFO:oejs.AbstractConnector:Started 
> SelectChannelConnector@0.0.0.0:8080
> 2012-11-11 15:04:46.467:INFO:oejsh.ContextHandler:stopped 
> o.e.j.s.ServletContextHandler{/,null}
> 2012-11-11 15:04:46.520:INFO:oejs.Server:jetty-7.x.y-SNAPSHOT
> 2012-11-11 15:04:46.520:INFO:oejsh.ContextHandler:started 
> o.e.j.s.ServletContextHandler{/,null}
> 2012-11-11 15:04:46.560:INFO:oejs.AbstractConnector:Started 
> SelectChannelConnector@0.0.0.0:8080
> 11.11.2012 15:04:53.357 *INFO * [main] Startup completed

--
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