may I create an issue in JIRA for this problem ?
it actually blocks me, I cannot upgrade apps on production environment
without refactoring file system layouts
thank you
Enrico
Il 28/12/2012 15:53, Enrico Olivelli - Diennea ha scritto:
Hi all,
I can deploy a webapp as ROOT context putting
Hi
Im a bit lost with your versions, can you check tomee 1.5.1? ( and maybe
trunk)
Le 30 déc. 2012 08:27, Enrico Olivelli eolive...@gmail.com a écrit :
may I create an issue in JIRA for this problem ?
it actually blocks me, I cannot upgrade apps on production environment
without refactoring
Hi,
I need at least 3 fixes (todo) pretty quickly
Hope to get it mid january so end of january would be fine
Would be a 1.6 IMO
Will try to explain more next year ;)
Le 29 déc. 2012 23:44, Alex The Rocker alex.m3...@gmail.com a écrit :
Jean-Louis:
This is a very serious topic for my
Hi Alex,
You are all welcome to share your needs and what you expect (and also to
help if you can ;-)).
IMO, TomEE 1.x.y is only Java EE 6 dedicated.
The work on Java EE 7 will start Q2 2013 I guess or a bit after and it
should produce the 2.x.y of TomEE.
Java EE 8, dunno for the moment, maybe
Id like to break rest default config so 1.6 is better imo
Le 30 déc. 2012 21:34, Jean-Louis MONTEIRO jeano...@gmail.com a écrit :
Hi Alex,
You are all welcome to share your needs and what you expect (and also to
help if you can ;-)).
IMO, TomEE 1.x.y is only Java EE 6 dedicated.
The work
Jean-Louis:
I wasn't very clear, sorry for that, but I think you got the idea :)
If I understand well your proposal of TomEE versioning, it would be x.y.z,
with x=1 for Java EE 6 ; and y moving when there are new features and z
moving for fixes.
Why not, but this is a little bit different from
That sounds pretty similar to Tomcat.
If we can adapt a bit to make things even clearer I'm all for it.
Whatever the next version will be, yes we can create a page and push our
versioning thoughts and Java EE mapping.
Would you like to start pushing your understanding as you proposed
previously
Note: why should we follow tomcat? Tomcat is pretty simple and doesnt
depend of anything else compared to us so it is natural if our versioning
is a bit less straight fwd even if we try to keep it as simple as possible
Moreover we are tied to openejb too which doesnt depend on tomcat
Le 30 déc.
Okay, now time for a stupid question : I'm asked to enter an Apache ID, how
can I register one? (the ID which I use for JIRA doesn't work here)
On Sun, Dec 30, 2012 at 11:01 PM, Jean-Louis MONTEIRO jeano...@gmail.comwrote:
That sounds pretty similar to Tomcat.
If we can adapt a bit to make
No stupid question, only stupid answers.
Apache ID = apache committer ID
You can just say No and enter in an anonymous mode.
As soon as you validate it, we receive a patch to commit for you.
@Romain, no need to follow Tomcat, was just to clarify things in my opinion
and check their versioning
When I click 'No', I'm redirected to this location:
https://cms.apache.org/openejb/wc/browse/anonymous-sFLdJE/trunk/
and I don't see where I could edit the page about TomEE versions :(
Am I missing something?
On Sun, Dec 30, 2012 at 11:17 PM, Jean-Louis MONTEIRO jeano...@gmail.comwrote:
No
11 matches
Mail list logo
