Re: [windup-dev] JBoss BOM

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(a)redhat.com | c: 980.226.7865 | http://www.redhat.com ----- Original Message ----- From: "Marek Novotny" <mnovotny(a)redhat.com&gt; To: windup-dev(a)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-sup... 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(a)redhat.com | c: 980.226.7865 | http://www.redhat.com > > _______________________________________________ > windup-dev mailing list > windup-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/windup-dev >