[forge-dev] JBoss Stacks: Requirements
rruss at redhat.com
Mon Jul 30 19:18:19 EDT 2012
----- "Jonathan Fuerth" <jfuerth at redhat.com> wrote:
> Hi Rafael,
> This project sounds great! Anything that can help people sort through
> all the dependencies they need to get started with Errai will be a big
> Our Kitchen Sink archetype is org.jboss.errai.archetypes:
> jboss-errai-kitchensink-archetype: 2.0.2.Final. There will also soon
> be a 2.1.0-SNAPSHOT, but it's probably best to stick with the released
> version for JBoss Stacks.
> From: "Rafael Benevides" <benevides at redhat.com>
> To: "Pete Muir" <pmuir at redhat.com>
> Cc: jdf-dev at lists.jboss.org, "forge-dev List"
> <forge-dev at lists.jboss.org>, "James Perkins" <jperkins at redhat.com>,
> "Max Andersen" <manderse at redhat.com>, "Jay Balunas"
> <jbalunas at redhat.com>, "Jonathan Fuerth" <jfuerth at redhat.com>, "Brian
> Leathem" <bleathem at redhat.com>
> Sent: Monday, July 30, 2012 9:12:50 AM
> Subject: Re: JBoss Stacks: Requirements
> Hi Everybody,
> Jay, Jonathan, Brian
> We are cataloging the Archetypes on JDF (as you can see on Pete's
> email below).
> Part of the Job was done
> - Get the YAML file format -
> - YAML file Parser -
> Those informations (BOMs, Runtimes, Archetypes) will be presented on
> JDF site. A preview can be found here:
> So the main point is: Do you want the errai, html5 and richfaces
> archetypes included also ?
> Thank you
> Rafael Benevides | Senior Software Engineer
> Red Hat Brazil
> Better technology. Faster innovation. Powered by community
> See how it works at redhat.com
> Em 02-07-2012 19:33, Pete Muir escreveu:
> I chatted with Max at JBoss World about requirements for what I'm
> code-naming JBoss Stacks, which is a really an extension of the JBoss
> BOMs project.
> The JBoss Stacks project takes all the BOMs, all the archetypes, and
> all the runtimes, and identifies which work with which. This can then
> be used by tools (like JBDS, Forge, Maven plugins) to correctly
> configure users projects.
> The stacks project requires 3 different dictionaries:
> * available BOMs
> * available archetypes
> * available runtimes
> and the ability to see the intersection between these things (i.e. if
> I'm on runtime version 1.2.3.Final, what BOMs are possible, what BOM
> is recommended, what archetypes are available, what is recommended).
> The runtime should include a download URL, so that plugins such as
> James' AS plugin for forge can download it. It should also contain a
> some options. I'm not sure exactly what is needed here, but James can
> provide details and what makes most sense.
> The runtimes should include what type they are (e.g. JBoss AS, EAP) to
> allow categorisation, filtering, sorting
> The Yaml parser in use should be pluggable, to avoid introducing
> uncessary extra dependencies
> There should be a recommended runtime per major version and per minor
> version (so you can say "I want JBoss AS 7" and you get back AS
> 7.1.1.Final or you can say "I want JBoss AS 7.0" and you get back
> We're going to need to be careful about compat, eventually, so we need
> to get everything in there, and get it right. We'll have a long beta
> cycle ;-)
> There will be a client utility, written in Java. This should be a
> single source file, which projects can copy in. It must have no
> dependencies other than a Yaml parser.
> I think Rafael is going to take the lead on this. But we'll decide on
> Monday next week.
> forge-dev mailing list
> forge-dev at lists.jboss.org
More information about the forge-dev