Jetty has moved!
Jetty is a project at the Eclipse Foundation.
Homepage:http://www.eclipse.org/jetty
Downloads: http://download.eclipse.org/jetty/
Documentation:http://www.eclipse.org/jetty/documentation/current/
About:http://www.eclipse.org/jetty/about.php
Jetty Powered:http://www.eclipse.org/jetty/powered/
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
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Releasing the Jetty Website

The jetty website is a maven2 project hosted in the jetty scm at The Codehaus.

Required Background

The jetty website is setup like any other project, with its own trunk, tags and branches directory structure in scm. It operates off of a set of maven dependencies listed in the jetty-website artifacts pom.xml. Most of the content of the website is located in the scm for the project but there are key components that are pulled into the website generation process that are generated as a part of the jetty trunk and jetty 6.1.x branch builds. These components are generated by the maven-assembly-plugin and have the classifier of site-component and generally include things like aggregated javadocs, cross-references and some specific other key files.

Adjusting Jetty Versions

The website is generated for specific version of jetty by altering two properties defined in the top level pom.xml file.

$jetty7.version

7.0.0pre2 and up

$jetty6.version

6.1.12 and up

Releasing

The release process for the jetty website is very simple.

  • set the appropriate release versions for the jetty6 and jetty7 properties in the root pom and commit

Deploying the Website

If the site:deploy step does not work, then you can manually deploy the site from the target directory to davs://dav.codehaus.org/jetty/jetty.

Icon

If you have issues doing this with missing site-component resources then you might need to build the two jetty releases the site is being based off of. I am trying to iron this out so its not needed but it might take a little bit. Do let me know if you have issues!

– jesse

  • No labels
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