[forge-dev] JBoss Stacks: Requirements

Rafael Benevides benevides at redhat.com
Wed Jul 11 08:00:35 EDT 2012


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!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20120711/c565dcd1/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Class Diagram.png
Type: image/png
Size: 138263 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/forge-dev/attachments/20120711/c565dcd1/attachment-0001.png 


More information about the forge-dev mailing list