<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I want to give all the "BOM heads" an FYI that the Fedora Java SIG
is currently selecting artifacts to use to create the RPMs that
correspond to the "official implementation" of each Java EE API [1].
Much like the JBoss specs, these RPM packages will become the
official "headers" for any Java packages that rely on Java EE APIs.
Here's an example: <a class="moz-txt-link-freetext" href="https://apps.fedoraproject.org/packages/cdi-api">https://apps.fedoraproject.org/packages/cdi-api</a><br>
<br>
The JBoss community, several members in particular (Shelly, Pete,
Karel, etc), have put in a lot of effort to groom and curate a set
of Java EE API JARs. I'd hate to see that effort passed up in
Fedora. Take note of the criteria that Stanislav mentions below to
determine which artifact to use to create the API package for each
spec (# of dependencies is a primary concern). If you'd like to
participate in this decision, feel free to submit feedback in the
#fedora-java IRC channel or the <a class="moz-txt-link-abbreviated" href="mailto:fedora-devel@lists.fedoraproject.org">fedora-devel@lists.fedoraproject.org</a>
list (or contact your local representative, i.e., Marek or Carlo,
hehehe).<br>
<br>
If you need some motivation as to why you want to get involved,
here's a preview of some of the artifacts that have been selected.
Note that few are from the JBoss specs:<br>
<ul>
<li>...<br>
</li>
<li>javax.el - tomcat-el-2.2-api
</li>
<li> javax.enterprise.inject - cdi-api
</li>
<li> javax.inject - atinject
</li>
<li>..</li>
<li>javax.persistence - geronimo-jpa
</li>
<li> javax.security.auth.message - geronimo-jaspic-spec </li>
<li> javax.servlet - tomcat-servlet-3.0-api </li>
<li> javax.servlet.jsp - glassfish-jsp/glassfish-jsp-api
</li>
<li> javax.servlet.jsp.jstl - jakarta-taglibs-standard
</li>
</ul>
Now is the time to have this conversation. It's a "speak now or hold
your peace" sort of thing.<br>
<br>
-Dan<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://admin.fedoraproject.org/mailman/private/java-devel/2012-June/004443.html">https://admin.fedoraproject.org/mailman/private/java-devel/2012-June/004443.html</a><br>
<div class="moz-forward-container"><br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
</th>
<td>[fedora-java] Chosing implementations for EE APIs and
finalizing guidelines</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
<td>Thu, 28 Jun 2012 15:16:57 +0200</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
<td>Stanislav Ochotnicky <a class="moz-txt-link-rfc2396E" href="mailto:sochotnicky@redhat.com"><sochotnicky@redhat.com></a></td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
<td>Fedora Java Development
<a class="moz-txt-link-rfc2396E" href="mailto:java-devel@lists.fedoraproject.org"><java-devel@lists.fedoraproject.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>With new additions to packaging guidelines for EE APIs, we have to pick
1 implementation for each API.
I have made initial proposal for these APIs into the draft[1]. My
criterias:
1. if JDK provides it, we are done. Packages should remove this
dependency from pom.xml files
2. Prefer packages with smaller and simpler BR/R chains. Good example
being javax.servlet.jsp where I preferred glassfish-jsp over tomcat
or other implementations.
3. Exception for 2nd point: if the project is proven to be difficult in
the past, override. Example being geronimo projects which were
overriden few times.
Even when we finalize this list, I don't expect it to be set in stone. I
want it in the guidelines, but if situation arises where quick change is
needed we can still do it. Longer-term, I'd like to package more simple
independent implementations such as glassfish-jsp so we don't have
dependency for example on tomcat in very basic dependency chain.
Now, I'd like to give everyone time to look at my picks and poke holes
in them. If you don't like them...speak up. If you don't, you will not
have my sympathies later. So I'll wait a week for comments. I plan to
finalize new guidelines by the end of next week. Then call SIG meeting
(finally) and vote on it before presenting it to the FPC.
[1] <a class="moz-txt-link-freetext" href="https://fedoraproject.org/wiki/User:Akurtakov/JavaPackagingDraftUpdate#EE_API_List">https://fedoraproject.org/wiki/User:Akurtakov/JavaPackagingDraftUpdate#EE_API_List</a>
--
Stanislav Ochotnicky <a class="moz-txt-link-rfc2396E" href="mailto:sochotnicky@redhat.com"><sochotnicky@redhat.com></a>
Software Engineer - Base Operating Systems Brno
PGP: 7B087241
Red Hat Inc. <a class="moz-txt-link-freetext" href="http://cz.redhat.com">http://cz.redhat.com</a>
</pre>
<br>
</div>
<br>
</body>
</html>