Versions Compared

Key

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

...

  • flat project structure, all artifacts lined up under jetty project, no project nesting planned initially
  • will retain the jetty-parent artifact which will be referenced as parent for jetty-contrib
  • jetty-contrib will remain at codehaus
  • potentially dropping jetty assembly at eclipse and instead managing that as a jetty distribution at codehaus as is done now, or roll that and hightide together into a more encompassing offering

SVN

  • jetty/jetty-parent-pom/trunk,tags,branches - o.e.jetty:jetty-parent used as parent for all jetty endeavors and linkage to jetty-contrib trunk development @ codehaus
  • jetty/jetty/trunk,tags,branches - jetty 7 trunk
  • jetty/jetty-sandbox/trunk,tags,branches - jetty sandbox - components can be developed here outside of the mainline jetty trunk and be voted/moved over into the jetty-trunk so that jetty-trunk remains specifically for active maintained jetty componentry
  • jetty/jetty-site/trunk,tags,branches - jetty website (we going to manage from eclipse?)

Under the jetty/trunk the module layout will look this:

  • pom.xml - o.e.jetty:jetty-project - contains <modules> linkage to all subprojects
  • jetty-server - o.e.jetty:jetty-server
  • jetty-util - o.e.jetty:jetty-util
  • ... for all artifacts mentioned below in per-artifact guidelines
  • jetty-assembly - o.e.jetty:jetty-assembly - produces .zip, .bz2, .tgz artifacts for traditional jetty usage (see Jetty Assembly Section below)

Eclipse Packaging Plan

The following is the intending packaging restructure of jetty7 into the proposed eclipse project move.

...

New Package

Previous Package

Previous Artifact

org.eclipse.jetty.plus.webapp

org.mortbay.jetty.plus.webapp

plus/jetty-plus

org.eclipse.jetty.plus.servlet

org.mortbay.jetty.plus.servlet

plus/jetty-plus

org.eclipse.jetty.plus.security

org.mortbay.jetty.plus.security

plus/jetty-plus

org.eclipse.jetty.plus.naming

org.mortbay.jetty.plus.naming

plus/jetty-plus

org.eclipse.jetty.annotation

org.mortbay.jetty.plus.annotation

plus/jetty-plus

org.eclipse.jetty:jetty-annotations - jetty/jetty-annotations

New Package

Previous Package

Previous Artifact

org.eclipse.jetty.annotation

org.mortbay.jetty.plus.annotation

plus/jetty-plus

org.eclipse.jetty.annotations

org.mortbay.jetty.annotations

plus/jetty-annotations

...

New Package

Previous Package

Previous Artifact

org.eclipse.jetty.handler.rewrite

org.mortbay.jetty.handler.rewrite

extra/jetty-rewrite

Jetty Assembly Plan

Jetty will be built entirely in self contained components with no contextual antrun scripting to move files around. In order for jetty to build the assembly correctly each component may be wired to generate an 'install-component' classified artifact that can be pulled down with the jetty-assembly build that will allow us to generate an install bundle very much akin to our existing jetty download bundle.

We can leverage the maven-dependency-plugin and the maven-assembly-plugin to build out this jetty-assembly artifact similar to the mechanic in place for the current jetty-site.

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