<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 30, 2012, at 9:51 AM, Rafael Benevides wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div text="#000000" bgcolor="#FFFFFF">
We only want to know if you approve that. And will be helpful if you
send the groupid:artifactId of the archetypes you want to include
also :D<br></div></blockquote><div><br></div><div>Awesome!! I think this will be a good listing to get people started.</div><div><br></div><div>The AeroGear HTML5/Mobile archetype used in JBoss Central is located at:</div><div><br></div><div>Group: org.jboss.aerogear.archetypes</div><div>Artifact: jboss-html5-mobile-archetype</div><div>Version: 1.0.0.M4b</div><div><br></div><div>This corresponds to the same html5/mobile kitchensink quickstart that is in JDF. </div><br><blockquote type="cite"><div text="#000000" bgcolor="#FFFFFF">
<br>
I'll do the rest.<br>
<pre class="moz-signature" cols="72">Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at <a href="http://redhat.com">redhat.com</a>
</pre>
<br>
Em 30-07-2012 10:36, Jay Balunas escreveu:
<blockquote cite="mid:FF841F48-BEDC-4BF1-B638-53B2E952CEDD@redhat.com" type="cite"><br>
<div>
<div>On Jul 30, 2012, at 9:12 AM, Rafael Benevides wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div text="#000000" bgcolor="#FFFFFF"> Hi Everybody,<br>
<br>
Jay, Jonathan, Brian<br>
<br>
We are cataloging the Archetypes on JDF (as you can see on
Pete's email below).<br>
<br>
Part of the Job was done<br>
<br>
- Get the YAML file format -
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true" href="https://github.com/jboss-jdf/jdf-stack/blob/master/stacks.yaml">https://github.com/jboss-jdf/jdf-stack/blob/master/stacks.yaml</a><br>
- YAML file Parser -
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true" href="https://github.com/jboss-jdf/jdf-stack/blob/master/Parser.java">https://github.com/jboss-jdf/jdf-stack/blob/master/Parser.java</a><br>
<br>
Those informations (BOMs, Runtimes, Archetypes) will be
presented on JDF site. A preview can be found here:
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true" href="http://site-jdf.rhcloud.com/stack/stacks/">http://site-jdf.rhcloud.com/stack/stacks/</a><br>
<br>
So the main point is: Do you want the errai, html5 and
richfaces archetypes included also ?<br>
</div>
</blockquote>
<div><br>
</div>
<div>What would be needed to get them there? Depending on
this, I think it would be good to include these archetypes in
the list. </div>
<br>
<blockquote type="cite">
<div text="#000000" bgcolor="#FFFFFF"> <br>
Thank you<br>
<pre class="moz-signature" cols="72">Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at <a moz-do-not-send="true" href="http://redhat.com/">redhat.com</a>
</pre>
<br>
Em 02-07-2012 19:33, Pete Muir escreveu:
<blockquote cite="mid:0BD80EE5-EDC3-4CB3-941A-B755A33A8D3A@redhat.com" type="cite">
<pre wrap="">All,
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 7.0.2.Final).
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.
Pete</pre>
</blockquote>
</div>
</blockquote>
</div>
<br>
</blockquote>
</div>
_______________________________________________<br>jdf-dev mailing list<br><a href="mailto:jdf-dev@lists.jboss.org">jdf-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/jdf-dev<br></blockquote></div><br></body></html>