<div class="gmail_quote">On Tue, Apr 20, 2010 at 12:20 PM, Steven Boscarine <span dir="ltr"><<a href="mailto:steven.boscarine@childrens.harvard.edu">steven.boscarine@childrens.harvard.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 04/20/2010 06:14 AM, Pete Muir wrote:<br>
> It's not the same JAR, but it is the same API (subtly different ;-)<br>
><br>
<br>
</div>The contents are the same, correct? There is no JBoss-specific magic in<br>
an org.jboss.spec.javax.* jar, right? The classes and interfaces are<br>
otherwise identical, right?<br></blockquote><div><br></div><div>Yes, identical. This is similar in spirit to what Geronimo has been doing for years.</div><div><br></div><div><a href="http://repo2.maven.org/maven2/org/apache/geronimo/specs/">http://repo2.maven.org/maven2/org/apache/geronimo/specs/</a></div>
<div><br></div><div>In fact, just about all of my past corporate projects referenced the geronimo specs for the very reason we are discussing in this thread...many were absent from central. Central got better for a while, now it's out of date again :(</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
><br>
>> On one hand, I prefer the javax.* because it is more conventional and in my opinion, more polished looking, especially for people who choose to run weld or Java EE outside of a JBoss container.<br>
>><br>
> Agreed. However even if we decided to maintain a BOM for this, we couldn't have it 100% using javax. as some specs in EE6 are missing published Maven artifacts. So, the question becomes whether it is worth doing a split one?<br>
><br>
<br>
</div>Fully understood. Sun/Oracle hasn't been good about pushing their APIs<br>
to maven central. It's been frustrating me and every other maven user<br>
for many years now.<br></blockquote><div><br></div><div>There are two problems here.</div><div><br></div><div>1. The spec APIs are not consistently pushed to the central repository (if at all)</div><div>2. The JARs contain stripped classes, which blow up test suites, as we have observed</div>
<div><br></div><div>Sonatype has been working on merging the <a href="http://java.net">java.net</a> Maven repository into central. Here's the story as I know it. They have put a lot of effort into it and they haven't gotten much support. So this is a one-time important and won't address future publication needs. So while it gives us the JARs we need in the short term, we still need a long term strategy. </div>
<div><br></div><div>Uh, and to think all of this over just needing to compile and app to use the platform. Frustrating for sure.</div><div><br></div><div>-Dan</div><div><br></div></div>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>