Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Jetty/Contributor/Update Site"
< Jetty | Contributor
m (capitalization) |
|||
| Line 7: | Line 7: | ||
==Generating the Update Site== | ==Generating the Update Site== | ||
| − | ; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-update-site/trunk : | + | ; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-update-site/trunk : Jetty update site trunk |
There are some requirements for getting this to work right as there is no nice and easy maven build for generating this as of yet. It is a woefully manual process that must be performed through the editor itself. I would _highly_ recommend using a clean installation of eclipse and keeping it around for the purposes of generating this update site. | There are some requirements for getting this to work right as there is no nice and easy maven build for generating this as of yet. It is a woefully manual process that must be performed through the editor itself. I would _highly_ recommend using a clean installation of eclipse and keeping it around for the purposes of generating this update site. | ||
| Line 15: | Line 15: | ||
* you should have the target artifacts in your local repository, if not then checkout the release tag and generate the documents from the top level, this should populate the local repo | * you should have the target artifacts in your local repository, if not then checkout the release tag and generate the documents from the top level, this should populate the local repo | ||
* locate and execute the gather.sh script which gathers up the maven artifacts, renames them to eclipse conventions and places them in the files directory in your current directory | * locate and execute the gather.sh script which gathers up the maven artifacts, renames them to eclipse conventions and places them in the files directory in your current directory | ||
| − | * copy the | + | * copy the Jetty files (now following the org.eclipse.jetty*_VERSION.jar naming convention) into the plugins directory of the clean eclipse installation |
* start the clean eclipse installation | * start the clean eclipse installation | ||
* import the project into a fresh eclipse workspace | * import the project into a fresh eclipse workspace | ||
| Line 36: | Line 36: | ||
===Servlet 2.5 Bundle=== | ===Servlet 2.5 Bundle=== | ||
| − | You should be able to obtain the bundle from ORBit or from the previous builds of the | + | You should be able to obtain the bundle from ORBit or from the previous builds of the Jetty update site. |
http://download.eclipse.org/jetty/7.0.0.M0/update/plugins/javax.servlet_2.5.0.v200806031605.jar | http://download.eclipse.org/jetty/7.0.0.M0/update/plugins/javax.servlet_2.5.0.v200806031605.jar | ||
Revision as of 05:53, 24 April 2009
Jetty Update Site
Jetty provides an eclipse p2 style update site for each of its builds that are stamped and released to the public for usage.
The URL for the update site follows the following naming convention: http://download.eclipse.org/jetty/<version>/update/
Generating the Update Site
- http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-update-site/trunk
- Jetty update site trunk
There are some requirements for getting this to work right as there is no nice and easy maven build for generating this as of yet. It is a woefully manual process that must be performed through the editor itself. I would _highly_ recommend using a clean installation of eclipse and keeping it around for the purposes of generating this update site.
- check out the source from the above scm URL
- obtain the servlet-api 2.5 bundle (see section below) and copy it into the plugins directory of the clean eclipse installation
- you should have the target artifacts in your local repository, if not then checkout the release tag and generate the documents from the top level, this should populate the local repo
- locate and execute the gather.sh script which gathers up the maven artifacts, renames them to eclipse conventions and places them in the files directory in your current directory
- copy the Jetty files (now following the org.eclipse.jetty*_VERSION.jar naming convention) into the plugins directory of the clean eclipse installation
- start the clean eclipse installation
- import the project into a fresh eclipse workspace
- Set the Target Platform
- mac: Eclipse->Preferences->Plugin Development->TargetPlatform
- chose 'Base RPC (Binary Only)' under Predefined Targets
- apply
- check the javax.servlet 2.5 bundle copied over in the second step above
- apply
- ok
- open the site.xml file of the org.eclipse.jetty.update.site project
- click Build All button
- if there are errors, good luck resolving them...they can be numerous and varied, or it just works, nuff said.
- zip up the resulting project (all of the org.eclipse.jetty.update.site project)
- scp the file to dev.eclipse.org:/home/www/jetty/<VERSION>
- unzip and rename directory to 'update'
- do a sanity check to make sure all the same jar files are on the plugins directory as the previous update sites
Servlet 2.5 Bundle
You should be able to obtain the bundle from ORBit or from the previous builds of the Jetty update site.
http://download.eclipse.org/jetty/7.0.0.M0/update/plugins/javax.servlet_2.5.0.v200806031605.jar