Security and annotations are up for vote.
I have JavaMail 1.6 created and almost ready for VOTE.
We don't have standalone TCK to run for those, but when they are released,
I'll get them all integrated and I'll push a TCK build on TomEE so we have
a view on what we need to fix.
--
Jean-Louis Monte
See this note on our activation thread. Long story short, our version 1.1 is
legitimate and the exact version expected for Java EE 8 on Java 8.
-
https://lists.apache.org/thread.html/89f81b0584dffca7d979a4fdedc6fe7b4f3c547848b0159b1702857e@
On JavaMail, my recommendation would be to update as
Trying to pull this message up in the list.
If we want to release Apache TomEE 8.0.0 before CodeOne, we need JavaMail,
Activation and some others.
For the others, I think I managed to get them up for vote and ready.
For Activation and JavaMail it's also an implementation so there is more
work inv
> On Aug 14, 2019, at 2:05 AM, Alex The Rocker wrote:
>
> Okay; for EDL I see it's compatible with Apache licensing, but
> strangely, JAXB license does not look like an EDL:
> https://github.com/eclipse-ee4j/jaxb-api/blob/2.3.2/LICENSE.md
>
> Am I mistaking or this is actually "cheesy" ?
I pull
Okay; for EDL I see it's compatible with Apache licensing, but
strangely, JAXB license does not look like an EDL:
https://github.com/eclipse-ee4j/jaxb-api/blob/2.3.2/LICENSE.md
Am I mistaking or this is actually "cheesy" ?
Kind regads,
Alexandre
Le mer. 14 août 2019 à 10:37, David Blevins a écr
> On Aug 14, 2019, at 1:23 AM, Alex The Rocker wrote:
>
> Hello,
>
> How about JAXB which is not EPL but EDL 1.0 ?
> (see https://github.com/eclipse-ee4j/jaxb-api/tree/2.3.2)
EDL is an approved license. Here's the complete naughty and nice list as it
where :)
- https://apache.org/legal/reso
Hello,
How about JAXB which is not EPL but EDL 1.0 ?
(see https://github.com/eclipse-ee4j/jaxb-api/tree/2.3.2)
Kind regards,
Alexandre
Le mer. 14 août 2019 à 10:16, David Blevins a écrit :
>
> This is really the better thread to talk about how to handle the gaps in our
> Java EE 8 APIs and sup
This is really the better thread to talk about how to handle the gaps in our
Java EE 8 APIs and support.
As noted, there is not license victory to be won. We have had EPL and CDDL
dependencies since v1.0 in 2011.
From a Geronimo perspective, we typed in the APIs and created all those spec
jar
David,
May I ask where you got all the versions please?
I was looking at this page and I see some mismatches.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Aug 13, 2019 at 9:10 AM David Blevins
wrote:
> I did a small gap-analysis of where we're sti
See comments below
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Aug 13, 2019 at 9:10 AM David Blevins
wrote:
> I did a small gap-analysis of where we're still short on Java EE 8 APIs
> from the perspective of our javaee-api jar:
>
> - https://issues
Thanks David.
Fantastic job with the review and summary. I am currently working on
Jakarta EE 8 compliancy. I have noticed some gaps and attempted to fix some
of them.
I'm happy to give it a try with them but the 3 last until we can move on.
--
Jean-Louis Monteiro
http://twitter.com/jlouismontei
I did a small gap-analysis of where we're still short on Java EE 8 APIs from
the perspective of our javaee-api jar:
- https://issues.apache.org/jira/browse/TOMEE-2620
Specific callouts are these APIs are also implementations, so switching to the
equivalent Jakarta version also gains a complian
12 matches
Mail list logo
