Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Jakarta EE 9 Milestone release?
Hi,

Things are going reasonably well, but there are still a number of blockers. Latest one is Fighter Fish (the OSGi interop), which is itself large enough to take some time to Jakarta-ize, but it also depends on OSGi enterprise, which uses javax types:

<groupId>org.osgi</groupId>
<artifactId>osgi.enterprise</artifactId>
<version>7.0.0</version>

package org.osgi.service.http;

import java.io.IOException;
import java.net.URL;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

/**
 * Context for HTTP Requests.
 * 
 * <p>
 * This service defines methods that the Http Service may call to get
 * information for a request.
 */
public interface HttpContext {}

Not sure how to handle these things. Negotiate with the OSGi alliance to have them release a new spec? That will very unlikely happen within a month.

Kind regards,
Arjan Tijms





On Fri, May 8, 2020 at 6:44 PM Kevin Sutter <sutter@xxxxxxxxxx> wrote:
Hi,
Based on Steve's recent update on Glassfish, we're making some fantastic progress towards Jakarta EE 9!  Although this is promising news from a CI viewpoint and we're also making progress on the TCKs, it's looking less and less likely that we will be able to produce a final release of Jakarta EE 9 by June (our original goal).  FYI, a final release of Jakarta EE 9 would require the final Specifications, final APIs, final TCKs, and final Compatible Implementations (CI), along with the results of the TCKs running against the CIs.  So, even though we are making great progress, that is a lot of work to be done by June...

To that end, we've been thinking about producing an M1 (Milestone) release for Jakarta EE 9 in the June timeframe.  We have already produced an RC1 for the Jakarta EE 9 APIs.  But, this Jakarta EE 9-M1 would include the current state of all the Specs, APIs, TCKs, and CIs.  Before we could actually produce this M1, we would need a functional, running Glassfish 6.0.0-M1 along with a running Platform TCK 9.0.0-M1.  Not sure if we want to set a bar for the TCK success rate, or just advertise where we are at with running the TCK.  For example, do we want to wait until we get to 75% successful before claiming an M1 release?  Or, do we use a date cutoff and when we announce the M1 release, we also announce our current TCK success rate (whatever that happens to be)?

This would need to be a coordinated effort across all of the Jakarta EE projects, so I'm looking for input and buy-in before we start down this path.  Producing an M1 release for Jakarta EE 9 would show all of our positive progress.  And, it would give our potential stack products (IDEs, frameworks, etc) a useable release to start experimenting with the new jakarta namespace.  Comments and suggestions welcome.  Thanks!

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

Back to the top