[forge-dev] JBoss Stacks: Requirements

George Gastaldi gegastaldi at gmail.com
Wed Jul 11 12:21:35 EDT 2012


+1 !
way to go Rafael ! 

Em 11/07/2012, às 09:00, Rafael Benevides <benevides at redhat.com> escreveu:

> 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>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20120711/e3eb70f2/attachment.html 


More information about the forge-dev mailing list