Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To build just the jetty core project all that needs to be run is 'mvn install' but since the jetty-contrib project is brought in via svn:externals declaration and as mentioned above it ideally a separate entity a profile needs to be activated to factor in the contrib modules. Running 'mvn -Pall-modules install' will trigger these contrib modules to also be built in the reactor.

No Format

(just jetty core artifacts)
> mvn install
(contrib artifacts as well)
> mvn -Pall-modules install

h3. Jetty Contrib Trunk

...



The jetty contrib trunk is pulled into the normal jetty build into the 'modules/contrib' directory but can be worked with outside of the jetty trunk.

...

  

The svn location for this project is:
No Format

>

...

svn

...

co

...

http://svn.codehaus.org/jetty-contrib/trunk

...

jetty-contrib

...

No Format

By default the jetty-contrib-parent does not declare the projects within as modules as ideally in the future the individual jetty contrib modules will be separately releasable on their own timelines as opposed to being lockstep with jetty releases. Whether this happens or not remains to be seen, but to build all registered artifacts in jetty-contrib simply execute maven with the all-modules profile activated. Not all modules in jetty-contrib build directly with maven so they may or may not be activated with this profile but within the jetty-contrib project, all committers have access to adding or removing modules from the all-modules profile.

...

Contact the core Jetty developers at www.webtide.com
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery