August 2012 - jdf-dev - Jboss List Archives

[JBoss JIRA] (JDF-31) helloworld-osgi quickstart needs a -with-osgi BOM

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JDF-31?page=com.atlassian.jira.plugin.sys... ] Work on JDF-31 started by Rafael Benevides. > helloworld-osgi quickstart needs a -with-osgi BOM > -------------------------------------------------- > > Key: JDF-31 > URL: https://issues.jboss.org/browse/JDF-31 > Project: JBoss Developer Framework > Issue Type: Bug > Components: stacks > Reporter: Sande Gilda > Assignee: Rafael Benevides > Fix For: 2.0.0.Final > > > See https://issues.jboss.org/browse/JBPAPP-9063?focusedCommentId=12694344#com... > From Pete Muir: > example: helloworld-osgi > artifact: org.osgi/org.osgi.core > using vesion: 4.2.0 > EAP bom version: 4.2.0-redhat-1 > We're going to need a with-osgi BOM for this -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JDF-30) hibernate3 quickstart needs a -with-hibernate3 BOM

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JDF-30?page=com.atlassian.jira.plugin.sys... ] Work on JDF-30 started by Rafael Benevides. > hibernate3 quickstart needs a -with-hibernate3 BOM > --------------------------------------------------- > > Key: JDF-30 > URL: https://issues.jboss.org/browse/JDF-30 > Project: JBoss Developer Framework > Issue Type: Bug > Components: stacks > Reporter: Sande Gilda > Assignee: Rafael Benevides > Fix For: 2.0.0.Final > > > See https://issues.jboss.org/browse/JBPAPP-9063?focusedCommentId=12694344#com... > The hibernate3 example has related artifacts with 3.6.8 version. In EAP bom we have 3.6.5 version. > From Pete Muir: > We're going to need a -with-hibernate3 BOM for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JDF-29) Need a -with-logging BOM for the following quickstarts: logging-tools, log4j

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JDF-29?page=com.atlassian.jira.plugin.sys... ] Work on JDF-29 started by Rafael Benevides. > Need a -with-logging BOM for the following quickstarts: logging-tools, log4j > ---------------------------------------------------------------------------- > > Key: JDF-29 > URL: https://issues.jboss.org/browse/JDF-29 > Project: JBoss Developer Framework > Issue Type: Bug > Components: stacks > Reporter: Sande Gilda > Assignee: Rafael Benevides > Fix For: 2.0.0.Final > > > From Pete Muir: > example: logging-tools > artifact: org.jboss.logging/jboss-logging-processor > using vesion: 1.0.1.Final > EAP bom version: 1.0.2.Final-redhat-1 > example: logging-tools > artifact: org.jboss.logging/jboss-logging-processor > using vesion: 3.1.0.GA > EAP bom version: 3.1.1.Final-redhat-1 > example: log4j > artifact: log4j/log4j > using vesion: 1.2.16 > EAP bom version: 1.2.16-redhat-1 > We're going to need a -with-logging BOM for this. Can you file a http://issues.jboss.org/browse/JDF issue to ask for one? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

Re: [jdf-dev] JBoss Stacks: Requirements

by Pete Muir

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(a)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> >

11 years, 9 months

2
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

jdf-dev August 2012