You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Andreas Pieber (JIRA)" <ji...@apache.org> on 2011/01/22 23:52:43 UTC
[jira] Updated: (KARAF-338) Upgrade Karaf to version 1.0.0
(-SNAPSHOT) of pax-web
[ https://issues.apache.org/jira/browse/KARAF-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Pieber updated KARAF-338:
---------------------------------
Summary: Upgrade Karaf to version 1.0.0 (-SNAPSHOT) of pax-web (was: Upgrade Karaf to version 0.8.2 of pax-web)
> Upgrade Karaf to version 1.0.0 (-SNAPSHOT) of pax-web
> -----------------------------------------------------
>
> Key: KARAF-338
> URL: https://issues.apache.org/jira/browse/KARAF-338
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 2.2.0
> Reporter: Charles Moulliard
> Assignee: Achim Nierbeck
> Fix For: 2.2.0
>
>
> Some nice features have been added in Ops4J Pax-Web project who offer now the possibility to customise the jetty server using the jetty.xml (http://issues.ops4j.org/browse/PAXWEB-193) not attached to a fragment bundle but deployed in /etc/ folder or in any other directory. Then you must create the file org.ops4j.pax.web.cfg in etc folder and add the following property --> org.ops4j.pax.web.config.file=./etc/jetty.xml
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.