Re: OpenEJB-4.6.0-SNAPSHOT Spring dependencies

Hi Mark I thought i excluded it yesterday Le 26 mars 2013 07:12, "Mark Struberg" a écrit : > Hi folks! > > > I'm using OpenEJB-4.6.0-SNAPSHOT embedded for testing my app and by > accident I discovered that quite a few Spring dependencies seems to have > slipt in. > Are those really necessary for

OpenEJB-4.6.0-SNAPSHOT Spring dependencies

Hi folks! I'm using OpenEJB-4.6.0-SNAPSHOT embedded for testing my app and by accident I discovered that quite a few Spring dependencies seems to have slipt in. Are those really necessary for activemq? If no, can we exclude them? LieGrue, strub [INFO] |  \- org.apache.openejb:openejb-core:jar

Re: 1.6.0

Not this week. Speaking on TomEE at DevoxxUK tomorrow, at DevoxxFR Thursday and ConFess in Vienna next week. -David On Mar 25, 2013, at 10:29 PM, Romain Manni-Bucau wrote: > @David: any idea when you'll do the xml stuff? basically i can wait the end > of the week but no more (> 3 months, a b

Re: 1.6.0

Great David, thks. So do we plan the 1.6.0.Final next month with next tomcat? Le 26 mars 2013 00:46, "David Blevins" a écrit : > I think calling beta as we've done for other releases is fine. That > should give more time for community discussion on a final and still get you > the release you se

Re: 1.6.0

I think calling beta as we've done for other releases is fine. That should give more time for community discussion on a final and still get you the release you seem to need. In the future know that starting a release and then consulting the list is not the right order. We'll chalk this up as

Re: 1.6.0

Right. It runs on a Raspberry PI now and runs significantly faster with the xml changes. I'd like to get it through a full TCK run and actually announce "TomEE certified on a Raspberry PI". I have gotten it pretty close to complete, but several chunks of tests timeout as that platform is a li

Re: 1.6.0

@David: any idea when you'll do the xml stuff? basically i can wait the end of the week but no more (> 3 months, a bunch of rewrite about classloaders, serialization etc, nothing we can put in 1.5.x but absolutely mandatory for a bunch of use cases). *Romain Manni-Bucau* *Twitter: @rmannibucau

Re: [VOTE] TomEE 1.5.2/OpenEJB 4.5.2 (staging-008)

+1 Jeff On Mar 25, 2013, at 3:32 PM, Alan Cabrera wrote: > +1 looks good > > > Regards, > Alan > > On Mar 20, 2013, at 9:17 PM, dblev...@apache.org wrote: > >> [generated email] >> >> SVN Tag: >> >> https://svn.apache.org/repos/asf/tomee/tomee/tags/tomee-1.5.2/ >> >> Maven Repo: >> >>

Re: [VOTE] TomEE 1.5.2/OpenEJB 4.5.2 (staging-008)

+1 looks good Regards, Alan On Mar 20, 2013, at 9:17 PM, dblev...@apache.org wrote: > [generated email] > > SVN Tag: > > https://svn.apache.org/repos/asf/tomee/tomee/tags/tomee-1.5.2/ > > Maven Repo: > > https://repository.apache.org/content/repositories/orgapachetomee-008 > > Binaries & S

Re: Validator ConcurrencyManagement

Hi Romain Thanks a lot for the answer. I will look at this class. -Ralf On 25.03.13 21:31 Romain Manni-Bucau wrote: all are here http://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/main/java/org/apache/openejb/config/rules/ some checks are elsewhere in the code beca

Re: Validator ConcurrencyManagement

all are here http://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/main/java/org/apache/openejb/config/rules/ some checks are elsewhere in the code because it is easier or not possible otherwise, your validation is done in http://svn.apache.org/repos/asf/tomee/tomee/trunk/co

Validator ConcurrencyManagement

Hello I worked a little bit and tried to get and learn the internals and have therefore a couple of questions related to this sub task 48 Validation ConcurrencyManagement. Here are my (beginner) questions: 1) What to validate? I think it is just: @ConcurrencyManagement (concurrency-management

CMS diff: Source Code

Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://tomee.apache.org/dev%2Fsource-code.mdtext David Salter Index: trunk/content/dev/source-code.mdtext === --- trunk/content/dev/source-cod

Re: 1.6.0

I actually ran GlassFish v2.1 on a Nokia N900 phone a couple of years ago, on OpenJDK for ARM. It was horribly slow, TomEE would be a breeze in comparison :) -- Bjorn Danielsson Cuspy Code AB dsh wrote: > I suppose Raspberry Pi support relates to getting TomEE to work on the > Oracle Java SE e

Re: 1.6.0

Hi David, was waiting tck setup to be fixed to send a mail with some info. honestly we have no choices, the 1.6.0 brings new changes needed for a bunch of apps (we should have them for at least 2 months!) waiting one more week is not an option (or we need to backport almost the whole release not

Re: 1.6.0

I suppose Raspberry Pi support relates to getting TomEE to work on the Oracle Java SE embedded for ARM platforms [1]? If so I am interested, but would like to see the task to be extended to ARM platform support for TomEE including the Raspberry Pi. Frankly, I am not a big fan of all the hype around

Re: 1.6.0

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 wrote: > 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

1.6.0

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 1.5.2

Re: Hi - I'd like to help out.

There is an online edit (blue pen on doc) which should be easier Le 25 mars 2013 19:06, "David Salter" a écrit : > Yes, I can help with docs also. > > For adjusting docs, is it the same procedure as for code, i.e. > > Raise JIRA issue > Add a patch > Ask the list to review the issue > > Thanks. >

Re: Hi - I'd like to help out.

Yes, I can help with docs also. For adjusting docs, is it the same procedure as for code, i.e. Raise JIRA issue Add a patch Ask the list to review the issue Thanks. Dave. On 25 Mar 2013, at 17:57, Romain Manni-Bucau wrote: > well about your issue tomee:deploy was originally created to depl

Re: Hi - I'd like to help out.

well about your issue tomee:deploy was originally created to deploy in the current tomee not another one (even if possible). That's pby why it was ambiguous you can help adjusting the doc too ;) *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannib

Re: Hi - I'd like to help out.

Hi, I've seen that post so I'll look even more in depth and see what issues I can help with. With the deploy issue, I was assuming that the relative path was to the mvn tomee:deploy command. If this isn't the case, then I don't need to raise an issue as its working as expected :) I thought i

Re: Hi - I'd like to help out.

Hi maybe read http://openejb.979440.n4.nabble.com/Hello-all-together-td4661567.html about your issue here the full idea: the path is a param sent to the remote tomee so basically it should be accessible from it. IIRC you can give a path (absolute or relative to the remote tomee), a http url, a m

Hi - I'd like to help out.

Hi, I'm interested in helping out with TomEE / OpenEJB and was hoping I could be of help to the project. I've been developing in Java EE for about 10 years, so hopefully I can help out. I've had a problem deploying a war file which got solved over in the User Forum (http://openejb.979440.n4.n

Re: [VOTE] TomEE 1.5.2/OpenEJB 4.5.2 (staging-008)

+1 Jean-Louis 2013/3/24 Romain Manni-Bucau > +-0 > > tomee seems to have gotten some fixes but arquillian got some regressions > (-1 for ports etc...) > > basically for prod it works and for test you can still use the old version > > *Romain Manni-Bucau* > *Twitter: @rmannibucau