Max, your best source is https://github.com/jboss-jdf/jdf-stack/blob/Beta2/stacks.yaml which I think is most up to date.
There are three roots: BOMs, archetypes and runtimes. Runtimes is what ties it all together though.
On 31 Jul 2012, at 14:01, Max Rydahl Andersen wrote:
Sorry for getting in late (3 weeks PTO) - so if this is answered somewhere else please let me know :)
Looking at the diagram i'm reading it as the runtime defines/contains the BOM/Archetypes since the runtime is the root or
am I misreading this ?
i.e. IMO an archetype has to be able to work with multiple versions, otherwise we need to release every archetype at every minor update of the runtime.
Thus I assume i'm wrong in reading that, but just wanted to be sure "root of YAML file" is not the runtime.
/max
On 11 Jul 2012, at 14:00, Rafael Benevides <benevides@redhat.com> wrote:
Yesterday I started to work on this new yaml format and I tried to capture all requirements that was discussed in this Thread. The result was the following attached uml diagram.
I think that's the better way to try comprehending what is needed and what will be covered. Today (or maybe tomorrow) I'll convert this idea to an example yaml file that is the representation of the diagram.
The closest of the idea is something like similar to:
bom: &jboss-with-x
name: JBoss With X
description: lorem ipsum
otherProperties: otherValues
availableVersions:
- 1.0.0.Final
- 1.0.1.CR1
bom: &jboss-with-y
name: JBoss With Y
description: lorem ipsum
otherProperties: otherValues
availableVersions:
- 1.0.0.Final
- 1.0.1.CR1
runtime: &jbosseap6
version: 6.0
type: EAP
boms:
- *jboss-with-x
- *jboss-with-y
recommendedBOM: *jboss-with-x
Em 03-07-2012 13:01, Rafael Benevides escreveu:
Em 03-07-2012 12:53, James Perkins escreveu:
We could do that as well.
7.0.1.Final:
properties:
arguments: -logmodule
cli: not-available
I like this approach.
I like this approach either!
<Class Diagram.png>