Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[rt-pmc] jetty packaging at eclipse-rt: status and questions

Hi everyone,

Jesse told me that it was a good time to write a long email about what
we have been prototyping.
Here is what we have been working on to package an equinox based
distribution of jetty.

Status
----------

1- An update site with a few features and their associated source features:
http://www.intalio.org/public/maven2/org/intalio/osgi/updatesite-7.0.2.v20100331-03/

2- A standalone distribution of equinox, jetty and their source-bundles:
http://www.intalio.org/public/maven2/org/intalio/osgi/updatesite-7.0.2.V20100331-standalone/org.eclipse.jetty.dist-7.0.2-SNAPSHOT.tar.gz
The layout is biased towards jetty. In the context of eclipse-RT we
should definitly place all the jetty's related folders inside the
configuration area
(eclipse/configuration/org.eclipse.jetty.osgi.boot).
The layout supports the legacy webapps and other j2EE shared classes
folder: we could certainly choose to remove all this and use a jetty
config that supports only web-bundles.

Everything here was built with maven3-tycho pointing against the
eclipse-3.6 update site and the jetty jars released on maven
The source code to build these artifacts is here:
http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/eclipse/trunk/

I have placed inside the distribution the PDE files that make it easy
to use the distribution from PDE:
- the .project file will define a barebone jettyhome project in the workspace.
- the jetty.target is the target-platform definition and relies on
${workspace_loc:jettyhome} to locate the location of the bundles.
- the jetty.launch is an appropriate launch configuration

At eclipsecon Shaun Smith (EclipseLink) and I demoed this approach
during the "Getting Started with Eclipse RT" tutorial.
Shaun added the javax.persistence bundles and the 2 JSF bundles from
Sun to demo a JSF web-bundles with beans backed by JPA.

The idea of pointing the IDE directly on build to start debugging and
hacking is something that is very convincing from a developer and
management perspective.

Future improvements: managing installations and updates with P2
-----------------------------------------------------------------------------------------------
The current prototype is based on the old
org.eclipse.update.configurator plugin.

We would like to be able to manage this runtime with P2.

I have been looking at defining an eclipse application based on Scott
Lewis suggestion: https://bugs.eclipse.org/bugs/show_bug.cgi?id=245267
Here is the work in progress:
http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/eclipse/trunk/jetty-features/org.eclipse.jetty.product/

Although I am not sure I am heading in the right direction as PDE
would not let me export a product that does not define an application.
I have not convinced maven3-tycho to build this product either.

Let me know if we are heading in the right direction.
Cheers,
Hugues


Back to the top