Community
Participate
Working Groups
As suggested by Dmytro, such a fragment would be attached to org.eclipse.jetty.osgi.boot It would contain the jetty configuration file etc/jetty.xml and is a nice way to let users define their custom configurations without having to define the system property "jetty.home" on the command line. It is similar to what spring-dm does for its own integration of jetty: http://static.springsource.org/osgi/docs/1.2.1/reference/html/web.html#web:osgi-artifacts:containers:jetty Inside org.eclipse.jetty.osgi.boot jettyhome/etc/jetty.xml will be renamed jettyhome/etc/default-jetty.xml The code that loads this file will first search for etc/jetty.xml then default to jettyhome/etc/jetty.xml
Committed the support for such a fragment. At the moment it works if and only if the fragment is actually exploded. Is this a reasonable assumption or do we need to put in some more work to make it work when it is a jar?
(In reply to comment #1) > Committed the support for such a fragment. > At the moment it works if and only if the fragment is actually exploded. > > Is this a reasonable assumption or do we need to put in some more work to make > it work when it is a jar? Hello, It would be nice to have this way to extend osgi.boot bundle. Current implementation supports only Eclipse (support of unzipped bundles). Regards, Dmytro
Resolved for 7.1.5 at the same time than bug 298703 and bug 309250.