<div dir="ltr"><div>For the longest time java ee related spec apis ware not officially available in any maven repository.</div><div><br></div><div>Only lately with latest version of Java/Jakarta EE spec apis are starting to appear properly in maven central.</div><div><br></div><div>Another reason is as Petr said, some service loader configs (w)are different and in some cases even some impl classes (w)are added.</div><div><br></div><div>--</div><div>tomaz<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 29, 2019 at 4:08 PM Matej Novotny <<a href="mailto:manovotn@redhat.com">manovotn@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
This is probably stupid question but I was recently wondering, what's the actual reason why WFLY (and other RH technologies) use jboss versions of all the specs?<br>
For instance <a href="https://github.com/jboss/jboss-annotations-api_spec" rel="noreferrer" target="_blank">https://github.com/jboss/jboss-annotations-api_spec</a> instead of just picking up the javax.annotation artifact.<br>
<br>
The contents are pretty much the same, so I think I have to be missing something trivial and obvious..<br>
Is it historical reasons? Or perhaps a matter of licenses and productization?<br>
<br>
Matej<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote></div>