Another trunk is good. If it sits there for too long, then off to the sandbox.
-David
On Jan 30, 2013, at 1:26 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
if nobody shouts before next week i'll move karafee over sandbox or another
trunk
any objection?
*Romain Manni-Bucau*
.
-dain
On Feb 11, 2013, at 7:12 PM, David Blevins david.blev...@gmail.com wrote:
We don't need to but we might want to do that where applicable on 1.6 (not
1.5.x).
-David
On Feb 10, 2013, at 3:14 AM, Romain Manni-Bucau rmannibu...@gmail.com
wrote:
Hi guys,
we are now tomee
Thank you so much. You can thank Karan Malhi for a good chunk of that. He did
an amazing job creating a framework for testing the validations and ensuring
each message key is used properly and supports all three levels we expect.
I agree, it's some of the better code I've seen.
-David
On
2 notes. There needs to be some communication on the list before starting a
release.
On 1.6.0 specifically, I'd like to finish getting the xml stuff switched over
before we release 1.6.0
Not the kind of thing I think we should be doing in a maintenance branch or we
would have done it in
I'd also like to get the raspberry pi support in better condition and make a
huge splash...
-David
On Mar 25, 2013, at 6:46 PM, David Blevins david.blev...@gmail.com wrote:
2 notes. There needs to be some communication on the list before starting a
release.
On 1.6.0 specifically, I'd
://www.oracle.com/technetwork/articles/java/raspberrypi-1704896.html
[2] http://ninjablocks.com/
Cheers
Daniel
On Mon, Mar 25, 2013 at 7:48 PM, David Blevins david.blev...@gmail.comwrote:
I'd also like to get the raspberry pi support in better condition and make
a huge splash...
-David
of things device,
where TomEE as well would make great sense.
[1]
http://www.oracle.com/technetwork/articles/java/raspberrypi-1704896.html
[2] http://ninjablocks.com/
Cheers
Daniel
On Mon, Mar 25, 2013 at 7:48 PM, David Blevins david.blev...@gmail.com
wrote:
I'd also like to get
Model B.
-David
On Mar 26, 2013, at 2:15 PM, dsh daniel.hais...@gmail.com wrote:
Which Raspberry Pi model do you use?
On Mon, Mar 25, 2013 at 11:30 PM, David Blevins
david.blev...@gmail.comwrote:
Right. It runs on a Raspberry PI now and runs significantly faster with
the xml
Our http implementation is fine for test, but should probably never be used in
any production server. Better to use Tomcat's or add Jetty -- we can handle
either.
-David
On Mar 27, 2013, at 11:24 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
Hi,
why our keep alive logic is in ejbd
A +1 from me of course. Vote passes with 10 +1 votes and no other votes.
+1s:
Alan Cabrera
Andy Gumbrecht
Daniel Haischt
David Blevins
Jean-Louis Monteiro
Jeff Genender
Jonathan Gallimore
Romain Manni-Bucau
Thiago Veronezi
Vishwanath Krishnamurthi
-David
On Mar 17, 2013, at 8:33 PM, David
Some release notes created, still more work needed there.
Binaries published:
https://dist.apache.org/repos/dist/release/tomee/tomee-1.5.2/
Should hit the mirrors soon.
-David
On Mar 31, 2013, at 7:18 PM, David Blevins david.blev...@gmail.com wrote:
Vote passes with 8 +1s and 1 +0.
+1s
still be accessible in Previous releases section?
Thanks,
Alex
On Sat, Apr 6, 2013 at 12:43 PM, David Blevins david.blev...@gmail.comwrote:
Some release notes created, still more work needed there.
Binaries published:
https://dist.apache.org/repos/dist/release/tomee/tomee-1.5.2
://rmannibucau.wordpress.com/
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/4/14 David Blevins (JIRA) j...@apache.org
[
https://issues.apache.org/jira/browse/TOMEE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
that someone else could stand in for you while you are
unavailable? I suppose your are some kind of a bottleneck if it gets to
sorting all these things out...
Cheers
Daniel
On Mon, Apr 8, 2013 at 10:36 AM, David Blevins david.blev...@gmail.com
wrote:
Hello from the Vienna airport!
Right
Spent some effort to get better pages together for snapshot builds. For
current branches:
- http://tomee.apache.org/download/tomee-1.6.0-snapshot.html
- http://tomee.apache.org/download/tomee-1.5.3-snapshot.html
Each page has a nice big disclaimer and full release notes (provided we file
Crafted up this post for announcing the 1.5.2 release:
- http://blogs.apache.org/preview/tomee/?previewEntry=apache_tomee_1_5_2
States that 1.5.2 is a maintenance release and gives a slight teaser for the
1.6.0 release.
Hope to publish it in the early afternoon Pacific time unless there are
FYI, that all this should be implemented now. The downloads.html links to an
index with all current and previous releases as well as snapshots.
-David
On Apr 6, 2013, at 11:12 PM, Alex The Rocker alex.m3...@gmail.com wrote:
Hello,
I often see in the users mailing list posts being replied
:
- what will learn with the example
- what is CODI
- maybe a couple key code snippets
Then I think it'd be awesome to tweet it to the 800+ TomEE followers and maybe
get it up on DZone.
-David
2013/4/25 David Blevins david.blev...@gmail.com
A very big thanks to Gerhard Petracek on his first
jboss behavior by.default. concretely: if getconnection fails
then try next db.
I added strategy for read only cases (rdbms have an issue with write case
by design)
Le 27 avr. 2013 02:02, David Blevins david.blev...@gmail.com a écrit :
Noticed the work going on with TOMEE-912 and wanted
://rmannibucau.wordpress.com/
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/4/27 David Blevins david.blev...@gmail.com
Had a quick look through the code and, definitely, it could only be used
for read-only cases where no JTA transaction or transaction of any
Seems like there's a simple solution, let's not use 'mvn:' as the prefix if we
aren't using the Maven coordinate system.
Any ideas on a better prefix? 'karaf:' or 'aether:'
As well, do you have any reference to Aether that shows this alternate
coordinates?
-David
On May 9, 2013, at 12:38
*
2013/5/9 David Blevins david.blev...@gmail.com
Seems like there's a simple solution, let's not use 'mvn:' as the prefix
if we aren't using the Maven coordinate system.
Any ideas on a better prefix? 'karaf:' or 'aether:'
As well, do you have any reference to Aether that shows this alternate
Looks to be a Karaf reference (OPS4j).
You mentioned Aether. Any info on that?
-David
On May 9, 2013, at 12:54 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
https://ops4j1.jira.com/wiki/display/paxurl/Mvn+Protocol
Le 9 mai 2013 21:38, David Blevins david.blev...@gmail.com a écrit
Fixed on the OWB side. Was a bug in the passivation checking.
-David
On May 9, 2013, at 10:25 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
Hi guys,
the currently failing test doesn't follow cdi spec (cdi-140), i can't
commit the patch ATM but here it is if anyone wants to do it (it
:
I already fixed it David...
Le 12 mai 2013 02:14, David Blevins david.blev...@gmail.com a écrit :
On May 3, 2013, at 7:18 AM, Thiago Veronezi thi...@veronezi.org wrote:
The pool ones are weird and i never have it locally :(
I have a theory: clock issues. It seems that the clock runs
/
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/5/13 David Blevins david.blev...@gmail.com
In a similar boat. I think #1 is a feature we need regardless, though
I
agree with JL that the default should be as it is now.
I have a small hope
Implemented an experimental feature in the spirit of the @Proxy concept where
an interface can be given along with an InvocationHandler implementation.
When the bean is created we'd create the InvocationHandler, create a proxy
using the interface, then use the proxy as the bean instance.
Took
On Sep 21, 2013, at 4:40 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
I think we already have it through cdi and decorators but it doesnt hurt to
get it this way ;).
Similar to decorators, yes. Just as the @Proxy+InvocationHandler concept is
similar to interceptors.
Big difference in
(with scope
handling for handler)
Le 21 sept. 2013 22:56, Romain Manni-Bucau rmannibu...@gmail.com a
écrit :
Works for me
Le 21 sept. 2013 22:51, David Blevins david.blev...@gmail.com a
écrit :
My phrasing might have been off -- I was agreeing with you on all points
:) I was just thinking about
I'd opt for simply going with TomEE 2.0 and OpenEJB 5.0.
We tried keeping OpenEJB locked to the EJB version number and it got very hard
and they eventually fell out of synch. There's only a new Java EE version
every 3.5 years and I suspect the next one will be more like 4.
I think we'll
Branched in hopes we can kick out some of the snapshot dependencies we have and
get a release candidate up mid week -- or at least something people can beat on.
In terms of OpenJPA specifically, what is the exact issue with using 2.2.2?
-David
On Oct 8, 2013, at 5:00 PM, David Blevins
: David Blevins david.blev...@gmail.com
To: dev@tomee.apache.org
Sent: Monday, 4 November 2013, 3:25
Subject: Re: Time to release TomEE 1.6.0
Branched in hopes we can kick out some of the snapshot dependencies we have
and get a release candidate up mid week -- or at least something people can
Heads up, making the branch for 1.6.0.
As sort of a crazy idea, I thought it might be interesting to branch for 1.6.1
now as well. Our intention would be to get this out *immediately* after 1.6.0
and I think it might help confidence that this will actually occur if we
effectively start that
On Nov 8, 2013, at 1:38 AM, Mark Struberg strub...@yahoo.de wrote:
The issue with openjpa-2.3.0 is a regression which only hits you seldom.
See OPENJPA-2335
I found it when I tried to use @OrderColumn.
It would be easy to fix this by rolling back Pinakis changes. But there might
have
Ignore. The upload failed.
On Nov 8, 2013, at 6:15 AM, dblev...@apache.org wrote:
[generated email]
SVN Tag:
https://svn.apache.org/repos/asf/tomee/tomee/tags/openejb-4.6.0/
Maven Repo:
https://repository.apache.org/content/repositories/orgapachetomee-092
Binaries Source:
the shaded
OpenJPA jar.
Cleaned that up and finally got it into nexus -- deploys continue to fail, so
determination is required.
Going to try and get some sleep. Jean-Louis staying on to get non-bloated zips
up.
-David
On Nov 8, 2013, at 3:15 AM, David Blevins david.blev...@gmail.com wrote
The release tools need work, but this build is good and running the TCK now.
Maven Repository:
- https://repository.apache.org/content/repositories/orgapachetomee-108/
Staged Binaries:
- https://dist.apache.org/repos/dist/dev/tomee/staging-108/tomee-1.6.0/
Source Branch:
-
Had 12 TCK failures in this build I think due to my OpenJPA build. Mark is now
publishing OpenJPA 2.3.0 binaries to Nexus for an vote. I'll try rerolling
with that version.
If that works and TCK is clear, I'll put the vote.
-David
On Nov 9, 2013, at 6:38 AM, David Blevins david.blev
Ok! All dependent projects are up for votes or completed voting.
I rolled a new set of binaries with Mark's proposed OpenJPA 2.3.0 binaries. I
ran these through the TCK and all is green. Looks like we're good to go.
Maven Repo:
-
Ok! All dependent projects are up for votes or completed voting.
I rolled a new set of binaries with Mark's proposed OpenJPA 2.3.0 binaries. I
ran these through the TCK and all is green. Looks like we're good to go.
Maven Repo:
-
updated my test suite - works fine
-Matthias
On Fri, Nov 15, 2013 at 9:39 AM, Mark Struberg strub...@yahoo.de
wrote:
+1
LieGrue,
strub
From: David Blevins david.blev...@gmail.com
To: dev@tomee.apache.org dev@tomee.apache.org
Sent
are up and TCK us running. If all looks good, I'll put them up for a
vote.
Thanks to everyone who took the time to review these binaries. We've never had
so many +1 votes from non-committers before. Really very awesome.
-David
On Nov 17, 2013, at 12:04 AM, David Blevins david.blev...@gmail.com
Ok, TCK clean so far.
Maven Repo:
- https://repository.apache.org/content/repositories/orgapachetomee-147/
Binaries:
- https://dist.apache.org/repos/dist/dev/tomee/staging-147/tomee-1.6.0/
Tag:
- https://svn.apache.org/repos/asf/tomee/tomee/tags/tomee-1.6.0/
The vote will go for 72 hours.
...@toolazydogs.com wrote:
There seems to be a number of license failures after I run
ant -f rat.xml scan
On Nov 17, 2013, at 2:16 AM, David Blevins david.blev...@gmail.com wrote:
Ok, TCK clean so far.
Maven Repo:
- https://repository.apache.org/content/repositories/orgapachetomee-147
Thanks for the note, Karl!
Adding to your point, I suspect it's a good time to start publishing JavaDoc as
well.
-David
On Nov 17, 2013, at 4:35 PM, Karl-Philipp Richter krichter...@aol.de wrote:
Hi together,
I'm new to mailing list and hope this is the right place to address to.
I
Ok, my +1
-David
On Nov 17, 2013, at 2:16 AM, David Blevins david.blev...@gmail.com wrote:
Ok, TCK clean so far.
Maven Repo:
- https://repository.apache.org/content/repositories/orgapachetomee-147/
Binaries:
- https://dist.apache.org/repos/dist/dev/tomee/staging-147/tomee-1.6.0
Ok, vote passes with 11 +1s and no other votes.
+1s:
Alex the Rocker
Bjorn Danielsson
Dain Sundstrom
Daniel S. Haischt
David Blevins
Jean-Louis Monteiro
Jeff Genender
Jonathan Gallimore
Matthias Wessendorf
Romain Manni-Bucau
Thiago Veronezi
Will push the binaries. It will take a few hours
My gut says we'd be wise to see 1.6.x through to stability before we start a
new major version.
Past evidence would suggest that absolutely no one would commit to the stable
branch if there was a more fun trunk to work on.
-David
On Nov 21, 2013, at 1:17 AM, Romain Manni-Bucau
More a note to Romain as I've not seen anyone else propose changing the version
number to match OpenEJB. To be honest, I'm not sure what this would give us.
It wouldn't make releases any easier or harder.
-David
On Nov 24, 2013, at 1:16 PM, Bjorn Danielsson
bjorn-apa...@lists.cuspycode.com
Pinging everyone who has shown interest in this online and offline.
Some time ago I proposed an initiative to collect all the various test in
Apache's Java EE related projects and convert and collect them here.
It would no doubt be a great contribution to TomEE, but to Java EE in general.
The
Lots of good feedback! Going to respond to just dev@tomee.apache.org as to not
bug people. Subscribe to the list or follow along via Nabble:
-
http://openejb.979440.n4.nabble.com/Arquillian-Java-EE-Test-Initiative-td4666503.html
-David
On Dec 2, 2013, at 7:47 PM, David Blevins david.blev
adding all these tests to
https://svn.apache.org/repos/asf/tomee/tomee/trunk/arquillian
or something else ?
If you could direct me or elaborate on a few next steps, I'll get started
with this right away :)
-Vishwa
On Tue, Dec 3, 2013 at 9:17 AM, David Blevins david.blev...@gmail.comwrote
Trying the shaded approach would certainly be interesting.
There's a lot of merit to it if we can work through the obvious issues and test
the heck out of it.
-David
On Dec 3, 2013, at 12:57 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
Ps: forgot another solutuon: shade quartz in
I suspect what Romain is pointing out is we already have things like
openejb-derby, openejb-hsql and openejb-cxf. No way at this point to use
openejb-cxf to imply a shaded or patched version of CXF without it
conflicting with the existing openejb-cxf module where the CXF integration code
Adding some notes as the person who made this mess :)
What we had there was very much the case of someday we can use this, but
someday never came till Andy finished it. We've historically told users the
exact server and client version needed to match.
Didn't say it at the time, but *huge*
On Dec 10, 2013, at 2:40 PM, David Blevins david.blev...@gmail.com wrote:
As far as where the shaded project lives, I'm cool with whatever as long as
it doesn't:
- break Intellij so we can still compile with a plain Intellij import and not
having to go through any magic to compile/run
Hi Jarek!
Really great you're interested in contributing and welcome aboard :)
If you want to submit a small test we can check in for OPENEJB-1358, I'll
commit it and then we can close that JIRA as Cannot Reproduce confident that
at least that bug will not show up in the future -- if it ever
Hi Chris!
Would love to see if we can fit that deb package into the build. As well an
openejb-maven-plugin sounds great.
Let's get started with the plugin. We can check that in next to the
tomee-maven-plugin. If you want to attach a zip of it to a new JIRA item,
that'd be a fantastic
Hi Martin!
You did everything great. Thanks for the documentation update! These little
tweeks go a long way when it comes to not wasting people's time. They're very
appreciated!
Committed it and it's now up on staging:
- http://tomee.staging.apache.org/tomee-mp-getting-started.html
Since our blog hasn't seen a ton of action and the twitter widget died months
and months ago, I switched up our front page so that it lists the downloads.
We can probably automate that or restore the news or any other options :) As
always, suggestions welcome.
-David
Wow. Absolutely, that looks like some *really* great advancements.
Looks like we'll have to buy the Infra guys/gals a round of beer at ApacheCon
this April. So fantastic.
Filed a JIRA to get us hooked up:
- https://issues.apache.org/jira/browse/INFRA-7315
Really great.
-David
On Feb 12,
://github.com/rmannibucau
2014-02-13 3:48 GMT+01:00 David Blevins david.blev...@gmail.com:
Wow. Absolutely, that looks like some *really* great advancements.
Looks like we'll have to buy the Infra guys/gals a round of beer at
ApacheCon this April. So fantastic.
Filed a JIRA to get us hooked
Synchronization issues rarely are :)
-David
On Feb 19, 2014, at 6:01 AM, agumbrecht agumbre...@tomitribe.com wrote:
OK, I'll dig in a bit later - And yes, it's not an 'always' thing?
Andy.
--
View this message in context:
So as I mentioned in the security reporting thread, although we do always use
the most recent versions of everything in our releases, we should probably
address our timing.
Over the lifetime of TomEE we average 4.14 months between releases. Also in
the lifetime of TomEE, there've been about
You've got the right idea.
Definitely make sure you use the WebSphere's InitialContextFactory instead of
TomEE's. Think of the `java.naming.factory.initial` like a JDBC driver.
Connecting to an Oracle DB requires an Oracle driver in TomEE, connecting to
WebSphere for EJB requires the
Tip to fellow list moderators, if you use the allow address instead of or in
addition to the accept address, the email address in question will not need
moderation again.
This unfortunately doesn't work if someone else responds first and just uses
accept.
We regularly have 100+ emails hit
FYI, definitely the wrong license header on that file :)
-David
On Mar 20, 2014, at 9:35 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
Hi
maybe last event should be AfterServiceCall(service, appInfo) for all
services or renamed to AfterRESTService
Side note: please don't add a
Some many releases ago, this started popping up in our logs. Eternal gratitude
to anyone who might have time to investigate and eliminate :)
INFO - Removing non-required WorkContextHandler with no context:
org.apache.geronimo.connector.work.TransactionContextHandler@8822a0
INFO - Removing
it?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-03-21 18:02 GMT+01:00 David Blevins david.blev...@gmail.com:
Some many releases ago, this started popping up
For Observers maybe we can find another way to achieve OPENEJB-2082 without
binding one observer directly to another:
public void observe(final @Observes(after = SimpleObserver.class)
SimpleEvent event)
I can see that creating just as much of a mess as having too many events.
Having to
is the index case.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-03-21 20:02 GMT+01:00 David Blevins david.blev...@gmail.com:
For Observers maybe we can find another
On Mar 22, 2014, at 4:15 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
removed after and replaced all the boilerplate we added with
AfterEventEvent.
Love it. Looks very elegant. Added a BeforeEvent to round it out.
Have some ideas to optimize. Ideally before/after could be zero
Was chatting with Gerhard at JavaLand and he mentioned moving examples to its
own section of the repository.
In our github mirror, we actually have quite a few people looking (110 forks,
34 stars)
- https://github.com/apache/tomee
If we move the examples out to their own repo and mirrored it
Very valid. In fact you reminded me of another topic of potentially moving the
examples out to their own repo.
Posted on that in another thread.
We were at around an hour and twenty minutes just a year ago, now we're up to 2
hours. Getting pretty heavy even for CI standards.
-David
On Mar
Romain had pinged me offline about the idea of upgrading our ASM dependencies
to v5 so we could support Java 8 (code compiled in Java 8 can't be read by ASM
v4 or earlier).
This combined with the Mojarra and EclipseLink / Plume distribution seem like
good features for a 1.7.0
We also have the
+1 for staging-1014
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
On Apr 15, 2014, at 11:15 AM, Andy Gumbrecht agumbre...@tomitribe.com wrote:
[generated email]
SVN Tag:
https://svn.apache.org/repos/asf/tomee/tomee/tags/tomee-1.6.0.1/
Maven Repo:
https
, David Blevins david.blev...@gmail.com
wrote:
This is probably not the full list of patches yet to be applied, but a
definite good start:
- https://github.com/apache/tomee/pulls
Andy or anyone else, possible to get some of these cleared out? The
ASF-Github integration now puts full details
on git it would be nice.
Le 20 avr. 2014 20:44, David Blevins david.blev...@gmail.com a écrit :
I think when you submitted your patch the asf hadn't yet improved the
github integration. Daniel Gruno (@Humbedooh) has put a lot of work into
and would probably do more if we had more ideas for him
Good to see the feedback and I'm a definite +1 for changing the default.
I don't see an advantage to actually removing the old approach. It's maybe 30
lines of code. We'd end up writing more than that in emails explaining that it
was removed and what to do instead.
--
David Blevins
http
.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
My +1.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
On May 6, 2014, at 2:29 PM, Andy Gumbrecht agumbre...@tomitribe.com wrote:
Hi Everyone,
I have rolled out the 1.6.0.2 security release for a vote.
The *only *difference to 1.6.0.1 is an upgrade to CXF 2.6.14
Release voting is the only abnormal voting. It requires a minimum vote: 3
+1s from PMC members to ensure legal oversight.
-David
On May 12, 2014, at 5:21 AM, agumbrecht agumbre...@tomitribe.com wrote:
Thanks Daniel,
Was kind of leaning on the 'Commit-Then-Review, Consensus Gauging through
: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-05-12 22:06 GMT+02:00 David Blevins david.blev...@gmail.com:
So if an administrator wanted to disable all users and did so by commenting
them out
Maybe someone can update this document.
Include the JIRA number and title (if there is a jira). I try never to say
Fixed FOO-2543 all by itself.
- http://tomee.apache.org/dev/tips-and-suggestions.html
This was already the proposed and agreed commit message format from some years
ago, but
I noticed trunk is still at 1.6.1-SNAPSHOT, we should probably switch that to
1.7.0-SNAPSHOT before branching.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
On May 20, 2014, at 5:14 AM, Jean-Louis Monteiro jlmonte...@tomitribe.com
wrote:
Time for 1.7.0
Let's do
track record is spotty on remembering to merge stuff from the
branch back to trunk :) (specifically version and pom changes are my most
frequent mistakes)
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
On May 20, 2014, at 2:23 PM, Romain Manni-Bucau rmannibu...@gmail.com
How did the talk go, Daniel?
Congratulations, btw
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
On Apr 11, 2014, at 3:04 PM, Daniel Cunha daniels...@gmail.com wrote:
Thiago,
Thank you. You helped me very much with my presentation.
On Fri, Apr 11, 2014
We have a Tomcat flavor of the javaee-api jar, we could yank el from that one.
(if we haven't already)
I know the servlet api is not in the Tomcat flavor of the javaee-api.jar
-David
On May 21, 2014, at 3:10 AM, Mark Struberg strub...@yahoo.de wrote:
btw, we should think about removing the
Side note, we should run the TCK on Java 8 to ensure all is well.
We added a config for 1.7 a while back, we'll need to do the same for 8. I'll
have to get it into our EC2 images, but meanwhile we can run a few tests on our
own machines.
--
David Blevins
http://twitter.com/dblevins
http
We should figure out how to make this jar optional so as to not affect any
tools that may be starting TomEE without using shell scripts.
If TomEE wasn't started with it and the person used the tomcat-juli.jar
instead, all should be ok.
-David
On May 19, 2014, at 1:59 PM, Romain Manni-Bucau
On May 28, 2014, at 4:58 PM, David Blevins david.blev...@gmail.com wrote:
We should figure out how to make this jar optional so as to not affect any
tools that may be starting TomEE without using shell scripts.
FYI, here's the result you get if updating the bin/ dir doesn't happen to be
part
months, that
perhaps is even better. Feedback is valuable.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
On Jun 4, 2014, at 7:38 AM, Hildeberto Mendonça m...@hildeberto.com wrote:
Hi,
just to give an update about this: Family is growing here, so I can't do
+1
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
On Jun 18, 2014, at 9:33 AM, Andy Gumbrecht agumbre...@tomitribe.com wrote:
Hi TomEE developers,
This mail is going out to both d...@openejb.apache.org and
dev@tomee.apache.org.
If you are still using d
+1
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
On Jun 18, 2014, at 2:10 PM, Andy Gumbrecht agumbre...@tomitribe.com wrote:
Hi TomEE developers,
This mail is going out to both d...@openejb.apache.org and
dev@tomee.apache.org.
If you are still using d
+1
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
On Jun 18, 2014, at 2:21 PM, Andy Gumbrecht agumbre...@tomitribe.com wrote:
Hi TomEE developers,
This mail is going out to both d...@openejb.apache.org and
dev@tomee.apache.org.
If you are still using d
is just a bear. Let's make sure we do that
one before we put up another vote as voting drastically decreases each time we
reroll.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
Looks like the legal report needs to be fixed -- attack of ASL header :)
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
On Jul 26, 2014, at 8:22 AM, Andy Gumbrecht agumbre...@tomitribe.com wrote:
Hi Everyone,
Anyone with some spare time is welcome to try out
On Jul 17, 2014, at 8:18 AM, David Blevins david.blev...@gmail.com wrote:
On the legal side, we still need:
- Library diff
- Review/adjust LICENSE and NOTICE files
We still need a report of the changed libraries from this release to the
previous. I guarantee there will be adjustments
Also looks as though we need to remove Gson from the NOTICE files as we no
longer ship it.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
On Aug 3, 2014, at 10:06 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
rmannibucau@asus:~/.m2/repository/org/apache/openejb
Getting a deadlock on AsynchronousInheritanceAnnotationFinder when the
interface a class implements is not in the jar being scanned.
main #1 prio=5 os_prio=31 tid=0x7f98ba812000 nid=0x1903 waiting on
condition [0x00010862c000]
java.lang.Thread.State: WAITING (parking)
at
1 - 100 of 857 matches
Mail list logo
