om example indeed ;).
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibu
CATALINA_OPTS=-Dquviondb.url=
it allows to use the same config in dev (local) and docker since setting
system props will work in all env and with any tooling (compared to env
vars which are less reliable by experience - some tools dont support them)
Romain Manni-Bucau
@rmannibucau <https://twitter.
89f
>
> I added @ApplicationScoped to the resource, removed the monotonic and added
> beans.xml but still, the issue arises
>
>
> El lun., 15 oct. 2018 a las 16:21, Romain Manni-Bucau (<
> rmannibu...@gmail.com>) escribió:
>
> > Hey César,
> >
> > not sure
+1 (non-binding) if we clearly state it is not usable in production (the
bval security issue the fork didnt fix), -1 (still not binding) otherwise
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Ol
try to make the endpoint not failing this way on
geronimo-metrics side.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibuc
the others types of metrics.
>
>
> El dom., 14 oct. 2018 a las 23:01, Romain Manni-Bucau (<
> rmannibu...@gmail.com>) escribió:
>
>> Hi César,
>>
>> the actual error is in the cause - available in logs.
>>
>> Romain Manni-Bucau
>> @rman
Hi César,
the actual error is in the cause - available in logs.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibuc
advantage is you can dev with the custom distro without having to
predownload it which is a game changer in the EE habits.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com&g
What about using tomee maven plugin to build your own distro? Build goal
was designed for it and this use case. We cant match all potential flavors
or we would deliver like 150 distro ;)
Le dim. 14 oct. 2018 14:02, j4fm a écrit :
> Hi, I'm taking a look at the TomEE 8 release preview for the MP
to - does - enforce its job/$$ choices into the spec and forget about
the overall platform consistency but IMHO TomEE must stay as clean as
possible to not just provide an unusable and misleading distribution to end
users. At least that's how we built it @geronimo.
Romain Manni-Bucau
@rmannibucau
It is really optional functionally and throught as such.
It is used to support yaml only - and undertested to be honest - so
normally not used at all in MP apps which are about JSON first (core) and
json is there OOTB.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |
wdym?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> |
PS: this code didn't change since 2 years so we can likely exclude it. Also
opened https://github.com/apache/activemq/pull/308 but not sure it will be
that welcomed in current way.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.ne
t;
>
> On Sat, Oct 13, 2018 at 1:57 PM Romain Manni-Bucau
> wrote:
>
> > this property is ignored by the MP layer, you have to use a cxf
> > interceptor:
> >
> > @OutInterceptors(classes = MyInterceptor.class)
> > @Path("foo")
> > public
super(Phase.PRE_LOGICAL);
}
public void handleMessage(final Message message) throws Fault {
message.put(FaultListener.class.getName(), new NoOpFaultListener());
}
public void handleFault(final Message message) {
// no-op
}
}
Romain Manni-Bucau
@rmannibu
Hi Ivan
you can either configure the log level or set a FaultListener to handle
that and bypass the default log.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com&g
this is an optional part so we can workaround it and we should open an
issue to ask AMQ to use jsonb. They are preparing a release these days so
hopefully it can make it.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Ol
Hello Roberto
Any reason to not exclude it as usual?
-- Forwarded message -
From:
Date: ven. 12 oct. 2018 23:36
Subject: [2/5] tomee git commit: Added Jackson notice to plus and plume.
To:
Added Jackson notice to plus and plume.
Project:
ok, means the TCCL can have changed and be wrong here due to a change in
the eager boot code which can capture apploader or maven classloader
instead of the mojo classloader.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/>
hmm the loader is the parent loader (container one) and it must work, are
you in a plain tomee or another flavor like tomee-embedded or other?
Class.forName uses the caller classloader which should be the same here in
the best case
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibu
Le ven. 12 oct. 2018 11:10, Thomas Andraschko
a écrit :
> Hi,
>
> found a bug, which is related to a slow startup as discussed in the other
> thread.
>
> See: https://issues.apache.org/jira/browse/TOMEE-2258
> the lookup: loader.loadClass("org.apache.openejb.bval.BValCdiFilter")
> fails with a
91f
> >
>
> Cheers,
> Roberto
>
> > On 9 Oct 2018, at 05:20, Romain Manni-Bucau
> wrote:
> >
> > Le mar. 9 oct. 2018 01:56, Roberto Cortez
> a
> > écrit :
> >
> >> Romain, you mean here:
> >>
> >>
> https://github.co
's a chance of getting a
> release this week.
> >
> > Assuming that's possible, is there anything standing in our way for
> putting up a release vote ourselves this week?
> >
> >
> > -David
> >
> >> On Oct 8, 2018, at 8:28 AM, Romain Mann
one option can be to start only one webapp here instead of all and hope
there is a single one or others are skipped ;)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com&g
e a better look and try to come up with some test scenarios.
> >
> >> On 4 Oct 2018, at 10:47, Romain Manni-Bucau
> wrote:
> >>
> >> Le jeu. 4 oct. 2018 à 11:42, Roberto Cortez <mailto:radcor...@yahoo.com.invalid>> a
> >> écrit :
> &g
the end the two issues are mentionned are not covered:
1. a regression will silently come back
2. for ears we can leak the servlet context if we end up here (and then the
app will wrongly behave)
My point is not to revert what you did but more to ensure it fixes the
issue in our buil
+1 looks good
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> |
the same pitfall so it can need to be reworked to ensure we don't hit
it for ears to not leak context between webapp which would be another nasty
bug).
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Ol
ase we can push snapshots with a particular version like
8.0.0-SNAPSHOT- to mark them even more.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://git
that is what I had in mind, throught it was already the case to be honest
through the transaction registry - excess of enthusiasm probably ;)
Side note: dropped G for now, if we find something impacting g-txmgr we'll
add it back
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibu
g-validation will be released (vote sent) likely next week - likely without
javadoc love for this iteration until somebody finds time in the week-end.
Then bval 2.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Ol
no?
side note: reference queue is supposed thread safe yes.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <ht
t. We probably need
> to check first about the existence of a JWT Principal and then fallback to
> the Tomcat one. I think I know how to do it, I was just trying to broaden
> up the conversation about general integration with EE security.
>
> Cheers,
> Roberto
>
> > On
OWB enable to do it - we did it in geronimo impl to pass tck of jwt auth
spec.
Le mer. 26 sept. 2018 03:28, Roberto Cortez a
écrit :
> Hi,
>
> I’ve done some work to push our MP JWT implementation from 1.0 to 1.1.
>
> You can check it here:
> https://github.com/apache/tomee/pull/173 <
>
custom provider programmatically through an extension
mecanism if you prefer
4. you can ignore johnzon configuring it as ignored
This is why I'm not really following you and I don't understand what you
are trying to achieve
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |
No, you always can override it as showed in this thread, test it if you
doubt.
Le dim. 23 sept. 2018 23:24, exabrial12 a écrit :
> So we're in agreement? Whether it's a specification note or not, the user
> cannot replace Johnzon because it is annotated */* and necessitates an
> option to
Hi Jonathan,
What is important is to use LocalMBeanServer to allow to disable that. Then
using a dynamicmbean - through our wrapper if you prefer the api - is nice
because you can put description easily versus a standard mbean where it is
less natural. For the name building, using the
Le dim. 23 sept. 2018 21:25, exabrial12 a écrit :
> Sorry, posting from my phone, it's not annontated *exclusively* */*, but
> that's my point.
Yes, but both must be used to sort providers properly and it is spec
behavior.
If I never want Johnzon to handle anything, you simply
> can't change
Ok so to clarify:
1. no "bug" in the stack for your case except that you app uses jaxb to
model json objects which is not clearly specified as required (think you
created a jira on that already)
2. you can use moxy if you follow the rules i mentionned - maybe the not
obvious part is cxf compares
Le sam. 22 sept. 2018 20:28, exabrial12 a écrit :
> Johnzon is buggy :) And the JSON produced by several popular REST APIs in
> the
> real world are also buggy. This patch provides a clean way to deal with
> said
> bugs when the "correct" way fails.
>
> Also, as mentioned, Johnzon cannot be
Hi Jonathan,
I dont understand this need since johnzon is always lower priority than
user providers so it is needed only for buggy providers which can be
wrapped in user code to avoid to configure it on the instance which is not
always possible.
Le ven. 21 sept. 2018 19:00, exabrial12 a écrit
Hi Alex
Le ven. 21 sept. 2018 à 09:56, Alex The Rocker a
écrit :
> Hello TomEE developpers,
>
> We are running our web apps with TomEE+ 7.0.5 and we are trying to
> upgrade our Apache struts based app to latest version (Struts 2.5.17).
>
> However it turns out that Structs 2.5.17 depends on
Hi Thiago
The block was fine to handle jwt errors and convert them in 4xx but it was
missing a final "else" to rethrow the original exception.
Side note: since other mp spec are Geronimo ones, maybe this one should be
migrated too to G impl?
Le jeu. 20 sept. 2018 00:22, Thiago Veronezi a écrit
FYI https://issues.apache.org/jira/browse/TOMEE-2233
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn &
You can generate swagger.json at byild time, no need to bring jackson and
friznd in the runrime just for that ;). Also cxf has a custom integ.
Le ven. 31 août 2018 21:08, Thiago Veronezi a écrit :
> I did not vote minus one because of that. I don't think we inject
> Application very often, but
http://repository.apache.org/snapshots/
Le sam. 25 août 2018 15:55, Matthew Broadhead
a écrit :
> where do the snapshots end up?
>
> On 24/08/18 22:49, Roberto Cortez wrote:
> > Thank you!
> >
> >> On 24 Aug 2018, at 19:42, Mark Struberg
> wrote:
> >>
> >> Sure, just started it. Should be
since the 16th we pass tck - both tomee and openejb - but maybe snapshots
are not up to date (bval and [weaver]
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github &
to Cortez >
> >>>> wrote:
> >>>>>
> >>>>> Apparently the issue with TomEE 7.1 is because of this:
> >>>>>
> >>>>
> https://github.com/apache/tomee/commit/76c9698a27ccbc4bb5970382846b570dc5f36793
> >>
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8
https://ci.apache.org/builders/tomee-7.1.x-ubuntu-jvm8
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github &
looks good
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> |
tps://github.com/apache/tomee/pull/142 <
https://github.com/apache/tomee/pull/142>
Cheers,
Roberto
> On 8 Aug 2018, at 21:49, Romain Manni-Bucau wrote:
>
> MP doesnt require it yet - will in 2.0 pby.
>
> Issue we have is to know you use jsonb. That said, thinking out loud
@Gurkan: there is no need to do a vote for java 11 support, we have to
support it anyway or it means the server is dead and we move it to attic.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Ol
Ok, let's be concrete, who will implement the specs on tomee 7 and under
which deadline? I think it is the main point to recenter on tomee 8 where
all the work is already done and investment is very low.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
Le jeu. 9 août 2018 à 07:53, Gurkan Erdogdu a écrit :
> >
> > We can definitely vote, but would be great if we can way a day or two to
> > discuss what we'd be voting and what our status is and how to best
> address
> > our concerns.
> >
> +1
>
>
> > We all universally agree we want MP in TomEE
Le mer. 8 août 2018 22:45, Jonathan Gallimore
a écrit :
> On Wed, Aug 8, 2018 at 9:32 PM, Gurkan Erdogdu
> wrote:
>
> > Hi all,
> > Can you please summarize the current state of MP in TomEE versions? I
> > really lost and confused that different people is working on some
> > (different) part of
aEE8 TCK is available and we pass it.
> >
> > B.) Go 8.0.0-M1, M2, etc. And do a 8.0.0 once we pass the JakartaEE8
> TCK. Note that this will mean that we will see a good year without any
> proper non-M release. And this might hurt adoption.
> >
> > LieGrue,
> >
Hi Gurkan,
>From what I know tomee hosts a not finished mp jwt auth impl and that is
it. It was however made cdi "in container" friendly which means we can
import all geronimo impl as it (even through tomee:build goal of our mojo
which is good for end users cause doing an pp distro is easily
Hi Jon,
wss4j needs it.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in
would work, A then
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in
switches between old / new.
> Something like openejb.jaxrs.legacy.providers = true / false.
> On Thursday, August 2, 2018, 4:42:13 PM GMT+1, Romain Manni-Bucau <
> rmannibu...@gmail.com> wrote:
>
> Sure, the target is quite clear I think, but we should mitigate the side
> eff
serialization will not change, only API is different if it was set
explicitly (@JsonbProperty or so).
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rm
Yep, or we just do it OOTB for the MP distro in a first step.
I don't have any strong opinion since in all cases we'll break some users
:(.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibuca
documented on the jaxrs mapper
page.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in
+ the related packaging. JCA got some work on that area to have some
command oriented pattern but it stays very heavy compared to the more
widespread CDI based solution.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Ol
the
exercise technically :)
Le mer. 1 août 2018 02:00, ChrisOwens a écrit :
> Romain Manni-Bucau wrote
> > If your goal is really to interact with kafka - and you dont care of rar
> > by
> > themselves - i would recommand to use a cdi extension,
> > you can find severa
Le mar. 31 juil. 2018 à 17:21, ChrisOwens a écrit :
> Romain Manni-Bucau wrote
> > 1. self contained and not used in another modules (ejb or web) -> you
> > register it in tomee.xml (in
> >
> > + config if needed) and that's it
>
> What does "+ config i
Le mar. 31 juil. 2018 à 17:22, ChrisOwens a écrit :
> Romain Manni-Bucau wrote
> > Are you able to push a reproducer on github with the tomee-maven-plugin
> > configured?
>
> I'm working on that now. I don't usually use the tomee-maven-plugin, so I
> thought I would
ejb are started (for the @Startup ones) after the
connector resources are created too so it should be fine. Are you able to
push a reproducer on github with the tomee-maven-plugin configured?
In terms of logs, you should see that some resources related to the rar are
created.
Romain Manni-Bucau
@rm
=HEAD
There are plans @geronimo to create a 1.4/2.0 pom (Yann said he will have a
look after his holidays) too which can be a better fit for tomee since some
of the specs you mentionned are not in MP 1.4/2.0 (BTW tomee 8 will be 2.0
since it has cdi 2.0).
Romain Manni-Bucau
@rmannibucau <ht
a
écrit :
> I was actually thinking of putting the entire classes jar from inside the
> rar into the ear lib module, not exploding the rar. There weren’t any
> annotations in the last rar spec I worked with…
>
> David Jencks
>
> > On Jul 30, 2018, at 12:33 PM, Romain Manni-Bu
Hi
The api part of the rar should be shared so put it in tomee/lib (or the ear
lib module). Worse case, David's trick of exploding the rar in the ear can
work if it uses annotations (just put it in any scanned module).
Le lun. 30 juil. 2018 21:09, David Jencks a
écrit :
> Hopefully someone who
Gurkan
>
> On Sun, Jul 29, 2018 at 6:32 PM, Romain Manni-Bucau >
> wrote:
>
> > Le dim. 29 juil. 2018 à 17:30, Gurkan Erdogdu a
> > écrit :
> >
> > > At a minimum, if some users (move from 7.0.x to 8.0.x) are successfully
> > > used it in product
the project members want to
> go this way, you can absolutely do.
> Regards.
> Gurkan
>
> On Sun, Jul 29, 2018 at 6:16 PM, Romain Manni-Bucau >
> wrote:
>
> > This is actually what we did since the beginning of TomEE.
> > Also keep in mind milestone, alpha, beta
- at least that's what we saw here. Therefore the fact to
directly go live is probably saner and doesn't prevent to fix issues
quickly.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibuca
the
milestone workaround we used for the 1.x to ensure 1.0.0 was certificed. So
yes, 8.0.0 directly is really ok :).
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github &
e make 7.1 directly a branch and we release it at the same time than
8.0.0
wdyt?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com
Ok so means we drop tomee 7.0 support with next release?
Le jeu. 26 juil. 2018 12:20, Jonathan Gallimore <
jonathan.gallim...@gmail.com> a écrit :
> On Thu, Jul 26, 2018 at 11:18 AM, Mark Struberg >
> wrote:
>
> > Yes, the following steps are now up to get done:
> >
> > 1.) Move the current
Hmm, did we get anything new compared to the thread "TomEE 7.1.x with
Microprofile" to justify a 7.1 compared to directly jump to 8.0?
Does it mean 7.0 is no more supported if we stick to only supportting 2
main branches?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannib
for a
new user to pick one not randomly.
Wdyt? Anyone interested in working on that or some aspects?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://g
You can set > in the tomee-maven-plugin
and upgrade the plugin version for the embedded flavor
(don't forget the repository and pluginRespotory pointing on the staging)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/
used.
>
> []s,
> Thiago.
>
>
>
> On Mon, Jul 16, 2018 at 12:30 PM, Romain Manni-Bucau <
> rmannibu...@gmail.com>
> wrote:
>
> > guess the contexts.find in cxf-rs module?
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.co
guess the contexts.find in cxf-rs module?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.
Hi Thiago,
you can surely start from
https://github.com/apache/tomee/blob/master/server/openejb-cxf-rs/src/test/java/org/apache/openejb/server/cxf/rs/JSonStreamingOutputTest.java
and adapt the endpoint to match you use case?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibu
l in few weeks from now.
>
> Second option would allow for incorporating additional user feedback along
> side with the Tomcat upgrade.
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Wed, Jul 11, 2018 at 9:4
They try to release each ~month/6weeks.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin
the name is configured in the tck, in properties, we used "jdbc" leading to
this openejb:Resource stuff. We should be able to use java:openejb/Resource
to workaround it pby but we can also ask tomcat to enable a whitelist of
namespace in the server to avoid to break our users.
Romain M
Just for reference on the saml issue:
http://tomee-openejb.979440.n4.nabble.com/Missing-Guava-in-TomEE-7-0-4-Plus-td4684068.html
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpres
+1, good catch!
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in
I trust you Jon that it was broken in 7.0.4, but it is not OK to keep it.
This particular dep can just be drop (so easy fix).
The java-support issue is more impacting and was completely missed in last
release cycles (guess we dont test saml?)
Romain Manni-Bucau
@rmannibucau <https://twitter.
:s, IMHO we must fix it - or do you see the legal requirements anywhere?
also we have that java-support issue (which beaks cxf/saml support in 7.0.4
since we dont provide guava), do we want to re-release a broken distro
since it has been broken in 7.0.4?
Romain Manni-Bucau
@rmannibucau <ht
Hi,
It seems we bundle javax.xml.soap-api-1.3.5.jar now in plus flavor (guess
it is a "leak" due to some dep upgrade), its license is CDDL+GPL1.1. I
didn't see the notice/license work done. Was it intended or as I'm thinking
a silent transitive issue?
Romain Manni-Bucau
@rmannibu
Hmm tests are key and even for arquillian module to run all-adapters
profile.
Id rather fix tests than excluding them and introduce potential regressions
easily.
On mac main issue is network interface selection. Should be easy to fix, no?
Le jeu. 5 juil. 2018 10:26, Gurkan Erdogdu a écrit :
>
Mark never run
-Pall-adapters which means you have ~1/3 of the actual coverage for several
modules. We did a fastbuild profile to solve that local build time issue a
long time ago. Maybe just invest in making it better?
>
> LieGrue,
> strub
>
>
> > Am 27.06.2018 um 11:35 schrieb
we can test against new and
> old containers.
> Plus an EE7 examples and EE8 examples project which can run against newer
> containers.
>
We align our examples on the branch so not a big advantage from my window.
>
> But we certainly have to think about how to do the final set
Hi Mark,
think we already discuss it somewhere else but wrote again the points
inline if it has been missed
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github &
. arquillian modules for "integration tests" (understand run in
a real tomee)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau&g
Hmm, bval and cdi tck right? This is almost nothing of ee tck coverage
sadly.
Le jeu. 21 juin 2018 08:22, Gurkan Erdogdu a écrit :
> Aha 3 h is ok, assumed 13 h :) Actually I was running the TCK in my laptop
> less than 3h
>
> On Thu, Jun 21, 2018 at 9:20 AM, Romain Manni-Buca
the full infra. So if you want to check some
coverage it easily takes that much or more yes.
Le jeu. 21 juin 2018 07:30, Gurkan Erdogdu a écrit :
> Romain, do you mean that each release running with TCK takes 13h?
>
> On Wed, Jun 20, 2018 at 9:33 AM, Romain Manni-Bucau >
> wrote:
&
> that's it.
>
> Everything else is not really user friendly and will make it harder for
> any new committer to get on board.
> I get the argument test coverage. But some of these examples still use the
> javaee6 apis, etc...
>
> LieGrue,
> strub
>
> > Am 20.06.2018
For the story it was not done cause not deployed and not linked to the
projzct for most of them.
Also, as you noticed in another mail, the reactor (and build) was not
designed to use the plugin so maybz dont fight too much that way ;)
Le mar. 19 juin 2018 22:55, a écrit :
> move samples to the
101 - 200 of 1698 matches
Mail list logo
