Rafael Benevides | Senior JBoss Consultant
Red Hat Brazil
+55-61-9269-6576

Better technology. Faster innovation. Powered by community collaboration. 
See how it works at redhat.com

Only comment is that we should have a labels: property, that allows arbitrary metadata to be attached  to each top level item (bom, archetype, runtime), which will provide an extensible way for tools to interact with the data format.

On 11 Jul 2012, at 13:00, Rafael Benevides 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!