[windup-dev] JBoss BOM

[Jess Sightler]

On 08/26/2015 12:15 AM, Brad Davis wrote:
> I think you need the one under the eap folder. The others don't map 
> versions correctly.
>
>> jboss-javaee-6.0-with-all 
>> <http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/jboss-javaee-6.0-with-all/> 
>
>
> That one only has version 1.0.4.
>
> http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/eap/jboss-javaee-6.0-with-transactions/
>
> That seems to have the right versions mapping to releases but not the 
> same  number of options (such as -all).
>

Oh, that's right. I don't think there is a single bom that is 
comprehensive. Perhaps we could pull in more than one?


> Brad
>
> Sent from my iPhone
>
> On Aug 25, 2015, at 10:58 PM, Jess Sightler <jsightle at redhat.com 
> <mailto:jsightle at redhat.com>> wrote:
>
>> Hmm, maybe we could use the jboss-javaee-6.0-with-all/ 
>> <http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/jboss-javaee-6.0-with-all/> 
>> one. I didn't remember that being an option before.
>>
>> On 08/25/2015 10:13 PM, Brad Davis wrote:
>>> I think they have the various versions here:
>>> http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/
>>>
>>> We would need the engineering teams to tell us which one... there are lots of boms in there with various options.
>>>
>>> Brad Davis
>>> Senior Manager, Red Hat Consulting
>>> Email:bdavis at redhat.com  | c: 980.226.7865 |http://www.redhat.com  
>>>
>>>
>>> ----- Original Message -----
>>> From: "Jess Sightler"<jsightle at redhat.com>
>>> To:windup-dev at lists.jboss.org
>>> Sent: Tuesday, August 25, 2015 9:45:13 PM
>>> Subject: Re: [windup-dev] JBoss BOM
>>>
>>> I agree... this is the best way to do it if it is feasible. Does such a
>>> single bom like this exist for EAP?
>>>
>>> On 08/24/2015 09:27 AM, Brad Davis wrote:
>>>> Right; the idea being that when EAP or BRMS or one of the other platforms go GA, they could have a BOM they provide to us that has the relevant dependencies they are exposing, and we could then turn that into the Target Technology in Windup.  It would make handoff easier, I think.
>>>>
>>>> Brad Davis
>>>> Senior Manager, Red Hat Consulting
>>>> Email:bdavis at redhat.com  | c: 980.226.7865 |http://www.redhat.com
>>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Marek Novotny"<mnovotny at redhat.com>
>>>> To:windup-dev at lists.jboss.org
>>>> Sent: Monday, August 24, 2015 4:06:12 AM
>>>> Subject: Re: [windup-dev] JBoss BOM
>>>>
>>>> Brad,
>>>>
>>>>    just to clarify more what you are writing about JBoss (developer) EAP
>>>> BOMs include just Java EE APIs artifacts + some JBoss implementations.
>>>> (those are described here
>>>> http://www.jboss.org/developer-materials/#!sys_type=jbossdeveloper_bom)
>>>>
>>>> But if you need a stack then you might mean EAP 6 supported BOM ?
>>>> https://repository.jboss.org/nexus/index.html#nexus-search;quick~eap6-supported-artifacts
>>>>
>>>>
>>>> On 10.8.2015 00:40, Brad Davis wrote:
>>>>> Jess,
>>>>> I wanted to see whether there would be a way to take a Maven BOM or dependencies and generate the packaging needed for the classloader stuff?  That way, when a platform is released, we could have a reusable way to generate the JBoss Windup target stuff that is needed for your classloading?
>>>>>
>>>>> I know for example that we have a JBoss EAP BOM that I would guess would have all of the dependencies for Java EE and the base JBoss EAP modules for a given JBoss version. Could be a custom plugin to create your XML + the assembly or dependency plugin probably.  Just wanted to throw the idea out there.
>>>>>
>>>>> Is there a sample out & sample docs you can link me to?
>>>>>
>>>>> Thanks,
>>>>> Brad Davis
>>>>> Senior Manager, Red Hat Consulting
>>>>> Email:bdavis at redhat.com  | c: 980.226.7865 |http://www.redhat.com
>>>>>
>>>>> _______________________________________________
>>>>> windup-dev mailing list
>>>>> windup-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150826/6237b5b5/attachment.html