Re: Handling Non-Public runtime packages

2011-12-04 Thread Stephen Coy
For JEE 6 applications you can use this pom fragment: org.jboss.spec jboss-javaee6-specs-bom 2.0.0.Final pom import in your dependencyManagement. Unfortunately, this does not exist for JBoss

Re: Handling Non-Public runtime packages

2011-12-03 Thread Stephen Connolly
Ahhh well you should be able to use the pom's they have as templates for EAP 5.0 poms On 3 December 2011 01:10, Steve Cohen wrote: > Sorry, it's our company who will not bless use of EAP 6.0 at all, but will > bless it EAP 7.0 soon. Hopefully there will be Maven for that. I didn't > mean to im

Re: Handling Non-Public runtime packages

2011-12-02 Thread Steve Cohen
Sorry, it's our company who will not bless use of EAP 6.0 at all, but will bless it EAP 7.0 soon. Hopefully there will be Maven for that. I didn't mean to imply anything about JBoss's plans. There is a Maven repo for jboss.org 5.1.0.GA. I was groaning about having to go backwards from that.

Re: Handling Non-Public runtime packages

2011-12-02 Thread Anders Hammar
Who decided they're not going to support EAP6.0? Your company or JBoss/Red Hat? I don't think the jboss community version fully support Maven, at least not for jboss.org 5.0 and earlier (which EAP 5 is based on). The thing is that it is hard to do magic when the individual components don't use Mav

Re: Handling Non-Public runtime packages

2011-12-02 Thread Steve Cohen
On 12/02/2011 01:47 AM, Anders Hammar wrote: I recognize your situation and here's what I've done for JBoss EAP (4.3 and 5.0): For all the runtime artifacts of the platform, I've created a tool that analyzes the dependencies between those artifacts. Based on this information I've created poms fo

Re: Handling Non-Public runtime packages

2011-12-01 Thread Anders Hammar
I recognize your situation and here's what I've done for JBoss EAP (4.3 and 5.0): For all the runtime artifacts of the platform, I've created a tool that analyzes the dependencies between those artifacts. Based on this information I've created poms for all the artifact with this dependency info. T

Handling Non-Public runtime packages

2011-12-01 Thread Steve Cohen
I am perplexed by the following situation: I work for a very large corporation with strict bureaucratic rules about what you can use. Nonetheless, they have a maven repository administered by very helpful people. However the maven repository people don't talk so much to the technical standar

Handling Non-Public runtime packages

2011-12-01 Thread Steve Cohen
I am perplexed by the following situation: I work for a very large corporation with strict bureaucratic rules about what you can use. Nonetheless, they have a maven repository administered by very helpful people. However the maven repository people don't talk so much to the technical standar