Hi,
These days I learning how Jetty support SPDY. I found that spdy-core and
spdy-jetty use the same package name. the SPDY modules and npn module has no
OSGi headers defined.
My question is:
will these modules support OSGi in the future, and if so, is there not any
issue for the split packag
There's a host of useful command lines for start.jar.
Try these ...
Show the list of OPTIONS available on your system.
$ java -jar start.jar --list-options
Show the start.config in use on your system.
$ java -jar start.jar --list-config
Show the classpath in use on your system (as defined in th
In reply to janb's "Re: [jetty-users] Jetty Maven Plugin: Which OPTION
jars are activated by default?"
Thanks Jan!
Jan, you said "If it helps your understanding, you can kind of think
of [mvn jetty:run starting up with options] as
OPTIONS=Server,jsp,jmx,resources,websocket,plus,annotations,jta,jd
Perfect! Thanks Jesse, this worked!
Below I provide my working pom.xml snippet. The relevant stuff is:
adding a section to the jetty-maven-plugin
section.
=== begin pom.xml ===
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schem
declare them as dependencies of the jetty plugin itself, they will
then be downloaded and added into the classpath of the plugin
execution
cheers,
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Mon, Sep 17, 2012 at 10:13 AM, Gerrit Hübbers
wrote:
> I need to have additional libraries/ja
I need to have additional libraries/jars available to the Jetty Maven
Plugin when starting it with "mvn jetty:run".
With the Jetty "start.jar" mechanism, I simply have to put the
required libraries into Jetty's directory "lib/ext" and they will be
added to Jetty automatically (as pointed out in
ht
