Bug 352512

Description Jesse McConnell 2011-07-19 17:28:40 EDT

We should track down where we have all our jetty archetypes and get them into a build that can be updated and released.  Also to incorporate recent comments on dev list.

-----

John Simone ✆ jsimone@salesforce.com via eclipse.org to jetty-dev
show details 16:16 (11 minutes ago)

I completely see your points. I don't want to introduce something that's already covered in documentation. I'll try my best to speak to the value that I see here.

The embeddability of Jetty is well explained and people are generally aware of it. What this does goes a little further than the examples. There are some steps between the simple embedding examples and running a full fledged application. The Maven plugin works so well because it explicitly adds project dependencies to the classpath before it launches. That avoids issues like taglib resolution and makes the embedded server work more like a general purpose application server rather than something tailored to a single application. I haven't seen an example of doing the same thing outside of that plugin and without building an intermediary war file.

I think that the flow of building an application with Maven, but then being able to launch it without Maven or anything else other than Java and project dependencies is nice and makes for a great dev/deploy flow. There were enough headaches, for me, in making this work that I want others to be able to skip the pain. This could be something that's just documented too, but since this still requires Maven it makes sense, to me, as an archetype.

An archetype like this could be used two ways. It could start a project the way the existing archetypes are likely used. It is also lightweight enough that it can be used to create a new project that existing code can be brought into. In both cases the archetype is a faster path to the goal than following a "how to" would be because of the nature of the project structure.