to your comments.
Regards
Violeta Georgieva
2012/9/11 Mark Thomas ma...@apache.org
Violeta Georgieva miles...@gmail.com wrote:
It would be very useful if I can provide this as part of the build
infrastructure for example.
If you can give me a hint from where to start I may try to provide
Hi Mark,
OK. First question. How did you create your git repo? I am trying to add
your repo as a remote repo to my own but there are no common ancestors.
I think I can hack around this but I'd like to understand how it
happened in the first place.
I'm using git svn.
The last rebase that I
From which git repository? I couldn't find that commit ID in the ASF git
repo for Tomcat trunk nor the GitHub mirror.
Ok I understood where the missunderstanding is.
That repo (in my github profile) is my own git-to-svn repo and is not a
fork from the one available in github.
Having my own
Thanks
2013/1/3 Mark Thomas ma...@apache.org
On 03/01/2013 14:30, Violeta Georgieva wrote:
I think that when the filter name is NULL the proper behaviour is to
return
IllegalArgumentException.
From other point of view the method's javadoc specifies only
IllegalStateException
Hi,
2013/1/20 Williams, Nick
So, will Tomcat 8 be targeted for EE 7, or will it wait until JSP-next
comes out, even if that takes a good deal longer than EE 7?
Also, I know that a lot depends on the timeline of EE 7, but now that that
date is approaching, do we have a GENERAL timeframe for
2013/2/5 Konstantin Kolinko
Could you test on some other XP.
I've tested 7.0.36 on Win7/x64 and XPSP3/x86 and everything works fine
Tried to restart dozen times at different stages and everything work
fine.
I also tested it onWin7/x64 and Win Server 2003/x64 and everything works
fine.
Hi,
I would like to work on this enhancement request [1].
What do you think? Is it Ok to provide implementation for it in Tomcat 7?
Thanks
Violeta
[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=51526
-
To unsubscribe,
2013/2/13 Mark Thomas :
The proposed Apache Tomcat 7.0.37 release is now available for voting.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.37/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-227/
The svn
2013/3/8 Mark Thomas wrote:
The proposed Apache Tomcat 7.0.38 release is now available for voting.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.38/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-002/
The
I found another problem. It appears when running a web application
from an archive (unpackWARs=false)
Mar 14, 2013 12:01:10 AM org.apache.catalina.startup.ContextConfig
processAnnotationsJndi
SEVERE: Unable to process resource element
2013/3/13 Mark Thomas wrote:
On 13/03/2013 18:10, violet...@apache.org wrote:
Author: violetagg
Date: Wed Mar 13 18:10:45 2013
New Revision: 1456068
URL: http://svn.apache.org/r1456068
Log:
Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=54684
Added 'javax.naming.spi' to the header
2013/3/14 Mark Thomas wrote:
Given the issues reported with the 7.0.38 tag I'm leaning towards
cancelling the 7.0.38 vote, fixing the known issues and rolling 7.0.39.
In addition to the issues in Bugzilla the only other issue was the
UEncoder problem Violeta found. (Any chance of a test case
2013/3/20 Ognjen Blagojevic wrote:
Hi,
http://tomcat.apache.org/tomcat-7.0-doc/config/http.html
restrictedUserAgents - The value is a regular expression (using
java.util.regex) *matching matching* ...
Thank you for the report.
The fixed documentation will be available with the next release
Hi,
I have a question for the loader that is used in
o.a.t.util.scan.StandardJarScanner.scan(ServletContext, ClassLoader,
JarScannerCallback, SetString) (7.0.x trunk).
Why don't we use the loader that is provided as a method parameter,
but instead of this we are using the thread context class
2013/3/20 Mark Thomas wrote:
On 20/03/2013 13:55, Violeta Georgieva wrote:
Hi,
I have a question for the loader that is used in
o.a.t.util.scan.StandardJarScanner.scan(ServletContext, ClassLoader,
JarScannerCallback, SetString) (7.0.x trunk).
Why don't we use the loader that is provided
Hi,
Test org.apache.catalina.connector.TestMaxConnections FAILED
I cannot reproduce this failure neither on Windows nor on MAC.
Can somebody help me to understand what's happening with this test?
Thanks
Violeta
2013/3/21 build...@apache.org:
The Buildbot has detected a new failure on
2013/3/21 Mark Thomas wrote:
On 21/03/2013 13:28, Violeta Georgieva wrote:
Hi,
Test org.apache.catalina.connector.TestMaxConnections FAILED
I cannot reproduce this failure neither on Windows nor on MAC.
Can somebody help me to understand what's happening with this test?
The machine
2013/3/22 Mark Thomas wrote:
The proposed Apache Tomcat 7.0.39 release is now available for voting.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.39/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-015/
The
2013/4/10 Ralph Plawetzki wrote:
I am looking for the Tomcat 8 sources and can't find them. I searched
the SVN and googled. The only thing I could find was the doc web page
for Tomcat 8.
Are the sources for Tomcat 8 already publicly available?
http://tomcat.apache.org/svn.html
/trunk/ -
Hi Rainer,
2013/4/16 Rainer Jung rainer.j...@kippdata.de
Hi Violeta,
On 16.04.2013 22:15, violet...@apache.org wrote:
Author: violetagg
Date: Tue Apr 16 20:15:28 2013
New Revision: 1468594
URL: http://svn.apache.org/r1468594
Log:
Fix
2013/4/19 Mark Thomas wrote:
On 19/04/2013 15:49, Mark Thomas wrote:
Should the changes described in [1] be applied to the Tomcat wiki?
[X] +1 Make it so
[ ] 0 No opinion
[ ] -1 I object to this proposed change because...
+1
2013/5/5 Mark Thomas ma...@apache.org
The proposed Apache Tomcat 7.0.40 release is now available for voting.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.40/
The Maven staging repo is:
2013/5/25 Mark Thomas wrote:
On 24/05/2013 21:58, violet...@apache.org wrote:
Author: violetagg
Date: Fri May 24 20:58:10 2013
New Revision: 1486217
URL: http://svn.apache.org/r1486217
Log:
Temporary disable the test check.
Why?
Because it was passing successful on my Windows
2013/5/25 Mark Thomas wrote:
On 25/05/2013 08:04, Violeta Georgieva wrote:
2013/5/25 Mark Thomas wrote:
On 24/05/2013 21:58, violet...@apache.org wrote:
Author: violetagg
Date: Fri May 24 20:58:10 2013
New Revision: 1486217
URL: http://svn.apache.org/r1486217
Log:
Temporary
Hi,
In the AsyncContext.dispatch(path) javadoc we have:
There can be at most one asynchronous dispatch operation per asynchronous
cycle, which is started by a call to one of the
2013/5/28 Konstantin Kolinko wrote:
I think that your patch is wrong.
Looking at how ActionCode.ASYNC_DISPATCH is handled in different
connector implementations in Tomcat 7, the code is like the following:
if (asyncStateMachine.asyncDispatch()) {
2013/5/29 Violeta Georgieva wrote:
2013/5/28 Konstantin Kolinko wrote:
I think that your patch is wrong.
Looking at how ActionCode.ASYNC_DISPATCH is handled in different
connector implementations in Tomcat 7, the code is like the following
2013/5/31 Violeta Georgieva wrote:
2013/5/29 Violeta Georgieva wrote:
2013/5/28 Konstantin Kolinko wrote:
I think that your patch is wrong.
Looking at how ActionCode.ASYNC_DISPATCH is handled in different
connector implementations in Tomcat 7, the code is like the following
2013/6/6 Mark Thomas wrote:
The proposed Apache Tomcat 7.0.41 release is now available for voting.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.41/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-073/
The
2013/6/11 ma...@apache.org
Author: markt
Date: Tue Jun 11 20:18:10 2013
New Revision: 1491940
URL: http://svn.apache.org/r1491940
Log:
Servlet 3.1 requires an ISE if getRequest() or getResponse() are called
after complete() or dispatch()
Modified:
2013/6/12 ma...@apache.org
Author: markt
Date: Wed Jun 12 18:31:30 2013
New Revision: 1492331
URL: http://svn.apache.org/r1492331
Log:
With clarification from the EG for Servlet 3.1 section 4.4 finally makes
sense. Implement the necessary restriction and add a test case.
I think that we
2013/6/14 Mark Thomas wrote:
On 14/06/2013 07:00, Violeta Georgieva wrote:
Is that mean that if I have AsyncListener that does some work in
onComplete() then I will not be able to use the request and response
objects?
Yes and no. You can't call getRequest() or getResponse
Hi,
According to Servlet Spec 3.1 final javadoc:
javax.servlet.http.HttpServletRequest.upgrade(Class) throws IOException,
ServletException
javax.servlet.http.HttpServletRequestWrapper.upgrade(Class) throws
IOException, ServletException
In our Servlet APIs these methods throw only IOException.
2013/6/20 ma...@apache.org
Author: markt
Date: Thu Jun 20 10:38:49 2013
New Revision: 1494915
URL: http://svn.apache.org/r1494915
Log:
Servlet 3.1 Implement the new deny-uncovered-http-methods element in
server.xml
That's for the xml but what about annotations?
We are processing them
Hi Mark,
2013/6/11 Mark Thomas wrote:
On 11/06/2013 21:29, Nick Williams wrote:
I was looking through EE 7 and the changes to trunk in the last six
months or so and realized that no work had yet been done to implement
EL 3.0. Does anyone know what the anticipated timeline is for
beginning
2013/7/2 Mark Thomas wrote:
The proposed Apache Tomcat 7.0.42 release is now available for voting.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.42/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-098/
The
2013/7/8 Mark Thomas wrote:
On 08/07/2013 06:38, Jeremy Boynes wrote:
On Jun 25, 2013, at 10:44 PM, Jeremy Boynes jboy...@apache.org
wrote:
Jasper's descriptor parser (used for web.xml and TLDs) can only
validate DTD-based documents. I opened 55212 about adding it. Such a
fix could
2013/7/9 Konstantin Kolinko wrote:
2013/7/9 build...@apache.org:
The Buildbot has detected a new failure on builder tomcat-trunk while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/tomcat-trunk/builds/4625
Buildbot URL: http://ci.apache.org/
2013/7/10 Mark Thomas wrote:
On 10/07/2013 12:11, violet...@apache.org wrote:
Author: violetagg
Date: Wed Jul 10 11:11:23 2013
New Revision: 1501719
URL: http://svn.apache.org/r1501719
Log:
javax.el.ResourceBundleELResolver:
According to javadoc:
1. When creating
2013/7/10 Mark Thomas wrote:
No. Firstly because if is not exclusive. Secondly because the
remainder of the returns definition states that the return value is
undefined if propertyResolved is false.
Another way of looking at it is that there is no language that requires
a return value of
Hi,
In the javadoc it is not described that the method throws IAE when the
property cannot be coerced into an integer. Moreover it is specified that
the property will be ignored by the resolver:
property - The index of the element in the list to return the acceptable
type for. Will be coerced
2013/7/10 Konstantin Kolinko wrote:
2013/7/10 Violeta Georgieva miles...@gmail.com:
Hi,
In the javadoc it is not described that the method throws IAE when the
property cannot be coerced into an integer. Moreover it is specified
that
the property will be ignored by the resolver
Hi,
I have the following question about:
1. Method setValue
There is some mismatch in the javadoc. In the method description there is
the following statement:
If the property exists but does not have a setter, then a
PropertyNotFoundException is thrown.
But the throws clause states:
2013/7/11 Konstantin Kolinko wrote:
2013/7/11 Violeta Georgieva miles...@gmail.com:
Hi,
I have the following question about:
1. Method setValue
There is some mismatch in the javadoc. In the method description there
is
the following statement:
If the property exists but does
2013/7/11 Mark Thomas wrote:
On 11/07/2013 13:49, Violeta Georgieva wrote:
Hi,
I have the following question about:
1. Method setValue
There is some mismatch in the javadoc. In the method description there
is
the following statement:
If the property exists but does not have
2013/7/15 ma...@apache.org
Author: markt
Date: Sun Jul 14 21:07:26 2013
New Revision: 1503056
URL: http://svn.apache.org/r1503056
Log:
Start to implement the lambda expression syntax. Very basic expressions
work. I expect further changes to be required for more complex expressions.
2013/7/16 Mark Thomas wrote:
On 16/07/2013 09:02, Violeta Georgieva wrote:
2013/7/15 ma...@apache.org
snip/
+public class AstLambdaExpressionOrInvocation extends SimpleNode {
+
+public AstLambdaExpressionOrInvocation(int id) {
+super(id
2013/7/16 ma...@apache.org
Author: markt
Date: Tue Jul 16 20:01:47 2013
New Revision: 1503857
URL: http://svn.apache.org/r1503857
Log:
Fix handling of nested lambda expressions with method parameters.
Removed:
tomcat/trunk/java/org/apache/el/parser/AstLambdaExpressionOrInvocation.java
2013/7/17 Mark Thomas wrote:
On 17/07/2013 12:43, Mark Thomas wrote:
Violeta Georgieva miles...@gmail.com wrote:
Having the example from the test:
(x-y-x-y)(2)(1)
We may transform it like this:
(()-y-2-y)()(1)
So instead of returning right way when formalParameters.isEmpty
Hi,
Let's have a lambda expression:
x-y-x-y
Let's now assign it and invoke it indirectly:
f = x-y-x-y; f(2)(1)
From the spec we have:
If the result of evaluating the function name is a LambdaExpression, the
LambdaExpression is invoked with the supplied arguments. If the result of
evaluating
2013/7/18 Mark Thomas wrote:
On 18/07/2013 08:00, Violeta Georgieva wrote:
Hi,
Let's have a lambda expression:
x-y-x-y
Let's now assign it and invoke it indirectly:
f = x-y-x-y; f(2)(1)
Several problems here.
1. The grammar didn't support functions having multiple sets
Hi,
While I was playing with collections I decided to change a bit one of our
tests (o.a.el.stream.TestCollectionOperations.testMaxLambda01()) and
instead of
beans.stream().max((x,y)-x.name.compareTo(y.name))
I made it like this:
comparison = v-(x,y)-v(x).compareTo(v(y))
Hi,
I tried to test the different o.a.el.stream.Optional methods.
Again I used one of our tests and modify
it: (o.a.el.stream.TestCollectionOperations.testAverage03())
[].stream().average().orElseGet(()-64)
I received:
javax.el.ELException: Cannot convert 64 of type class java.lang.Long to
2013/7/18 Mark Thomas wrote:
I think we are at the point where we could do a 8.0.0-alpha release. The
specs (Servlet 3.1, JSP 2.3, EL 3.0, WebSocket 1.0) are all implemented.
There is still work to do to review the EG disucssions that covered
various edge cases / things not in the spec to
2013/8/1 Mark Thomas wrote:
The proposed Apache Tomcat 8.0.0 release candidate 1 is now available
for voting.
Given this is a release candidate I am working on the basis that it is
equivalent to an alpha. That said:
- Servlet 3.1 is complete
- JSP 2.3 is complete
- EL 3.0 is complete
-
2013/8/1 Mark Thomas wrote:
All,
Continuing the roughly monthly release cycle for 7.0.x, it is the start
of a new month and time for another release.
The open 7.0.x bugs have been fixed so 7.0.x/trunk should be in a
suitable state for tagging.
I'd like to free up some more time for
2013/8/14 Mark Thomas wrote:
Summarising the response to this thread so far:
There is a preference for not strictly enforcing whatever limit is
selected. Rules need exceptions and committers can exercise judgement.
It does create a grey area but the majority is OK with that.
There is a mix
2013/8/7 Mark Thomas wrote:
On 07/08/2013 06:19, Konstantin Kolinko wrote:
2013/8/6 Mark Thomas ma...@apache.org:
Feel free to make as much or as little use of this:
http://wiki.apache.org/tomcat/ReleaseProcess
If anything isn't clear, let me know.
The following is missing:
1.
2013/8/20 Nick Williams wrote:
I'm working on implementing bugzilla 55317. It's a pretty important
change (weaving) to a pretty import class (WebappClassLoader), so it
obviously needs some unit tests. However, I need some guidance:
1) I've never gotten all the existing tests to pass on my
2013/8/12 Mark Thomas wrote:
I'm wondering about adding enableWebSockets() and enableJSPs() methods
to Tomcat which would automatically add the relevant SCI to any Context
created via one of the addContext(...) methods. Thoughts?
+1
2013/8/23 Mark Thomas wrote:
Tomcat 8 needs tc-native with the fix for non-blocking IO [1]. Any
takers for rolling the release?
Mark,
Do we need this for Tomcat 7 as well?
Thanks
Violeta
Hi,
Although I can see that the central build is OK, I cannot build tomcat 7
trunk.
The new class org.apache.tomcat.util.buf.Utf8Encoder
uses java.nio.charset.StandardCharsets which is available only in java 7.
Do you have such problems?
Thanks
Violeta
2013/9/13 Mladen Turk mt...@apache.org
On 09/09/2013 01:31 PM, Mladen Turk wrote:
Version 1.1.28 is bug fixing release.
The proposed release artefacts can be found at [1],
and the build was done using tag [2].
The VOTE will remain open for at least 48 hours.
The Apache Tomcat Native
Hi Mark,
2013/9/13 Mark Thomas ma...@apache.org
a) Unpack JAR resources to the work dir and return a URL to the unpacked
location
-1
In trying to decide between b) and c) I came to the conclusion that it
would be better to keep the war:// url scheme and generic tomcat:// url
schemes
2013/9/16 Mark Thomas ma...@apache.org
Just a quick update.
I'm seeing a APR/native issue leading to JVM crash that I am currently
trying to debug. Unfortunately, the issue doesn't appear to be
particularly repeatable.
Is that issue available in Tomcat 7 also?
Should I wait for it before
Hi Jeremy,
2013/9/13 bugzi...@apache.org
https://issues.apache.org/bugzilla/show_bug.cgi?id=55508
Jeremy Boynes jboy...@apache.org changed:
What|Removed |Added
Hi,
I will tag 7.0.43 later today.
If you need to put something in this version please reply here.
Regards
Violeta
Hi,
2013/9/18 Violeta Georgieva miles...@gmail.com
Hi,
I will tag 7.0.43 later today.
If you need to put something in this version please reply here.
I tried to reproduce the issue [1] with Tomcat 7.0.43 tag.
There are only the warnings below and Tomcat starts. (catalina.bat run
-security
2013/9/19 Mark Thomas ma...@apache.org
On 19/09/2013 11:28, Mark Thomas wrote:
On 19/09/2013 11:21, Violeta Georgieva wrote:
Hi,
2013/9/18 Violeta Georgieva miles...@gmail.com
Hi,
I will tag 7.0.43 later today.
If you need to put something in this version please reply here
The proposed Apache Tomcat 7.0.43 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0 implementation.
Note that use of this functionality requires Java 7.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.43/
The Maven
2013/9/19 Konstantin Kolinko knst.koli...@gmail.com
2013/9/18 violet...@apache.org:
Author: violetagg
Date: Wed Sep 18 19:44:03 2013
New Revision: 1524545
URL: http://svn.apache.org/r1524545
Log:
Tag 7.0.43
Added:
tomcat/tc7.0.x/tags/TOMCAT_7_0_43/ (props changed)
2013/9/20 Jeanfrancois Arcand jfarcand@gmail.com
On 2013-09-20 6:26 AM, Mark Thomas wrote:
On 20/09/2013 11:24, Jeanfrancois Arcand wrote:
Hi,
[X] Broken - do not release
I do test/use Tomcat with WebSocket since 7.0.27. 8.0.0-RC1 worked well
with jsr356, but 7.0.43 is broken. You
2013/9/21 Mark Thomas ma...@apache.org
On 20/09/2013 08:38, Violeta Georgieva wrote:
The proposed Apache Tomcat 7.0.43 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0
implementation.
Note that use of this functionality requires Java 7
2013/9/20 Mark Thomas ma...@apache.org
The proposed Apache Tomcat 8.0.0 release candidate 3 is now available
for voting.
Given this is a release candidate I am working on the basis that it is
equivalent to an alpha. The main changes since RC1 are:
- Updated spec implementations with results
The proposed Apache Tomcat 7.0.44 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0 implementation.
Note that use of this functionality requires Java 7.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.44/
The Maven
2013/9/24 Nick Williams nicho...@nicholaswilliams.net
On Sep 24, 2013, at 11:00 AM, Rossen Stoyanchev wrote:
On Tue, Sep 24, 2013 at 11:40 AM, Mark Thomas ma...@apache.org wrote:
The necessary update to the script that uploads those JARs to the Maven
repo was missed. I think I have
2013/9/25 Mark Thomas ma...@apache.org
On behalf of the Tomcat committers I am pleased to announce that
Konstantin Preißer has been voted in as a new Tomcat committer.
In addition to a number of high quality bug reports and patches,
Konstantin is also responsible for the makeover the Tomcat
The proposed Apache Tomcat 7.0.45 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0 implementation.
Note that use of this functionality requires Java 7.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.45/
The Maven
2013/9/25 Violeta Georgieva miles...@gmail.com
The proposed Apache Tomcat 7.0.45 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0
implementation. Note that use of this functionality requires Java 7.
It can be obtained from:
https
Hi,
I think to start preparing Tomcat 7.0.46 for voting later today.
Please reply here if you need to include something in this release.
Regards
Violeta
2013/10/15 Mark Thomas ma...@apache.org
On 15/10/2013 09:12, Mark Thomas wrote:
On 15/10/2013 09:11, Violeta Georgieva wrote:
Hi,
I think to start preparing Tomcat 7.0.46 for voting later today.
Please reply here if you need to include something in this release.
I want to look
2013/10/15 Mark Thomas ma...@apache.org
On 15/10/2013 16:10, Konstantin Preißer wrote:
Mark,
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Tuesday, October 15, 2013 4:59 PM
To: Tomcat Developers List
Subject: Re: Tagging 7.0.46
Yes, I can
The proposed Apache Tomcat 7.0.46 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0 implementation.
Note that use of this functionality requires Java 7.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.46/
The Maven
Hi Mark,
2013/10/17 Mark Thomas ma...@apache.org
On 16/10/2013 23:47, Konstantin Preißer wrote:
Hmm, unfortunately it seems the Websocket implementation using the
deprecated proprietary API does not work correctly when using the
HTTP APR and NIO connector on Windows...
snip/
With
2013/10/17 Mark Thomas ma...@apache.org
On 17/10/2013 10:52, Violeta Georgieva wrote:
Hi Mark,
2013/10/17 Mark Thomas ma...@apache.org
On 16/10/2013 23:47, Konstantin Preißer wrote:
Hmm, unfortunately it seems the Websocket implementation using the
deprecated proprietary API
2013/10/16 Violeta Georgieva miles...@gmail.com
The proposed Apache Tomcat 7.0.46 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0
implementation. Note that use of this functionality requires Java 7.
It can be obtained from:
https
Hi,
I'm starting with Tomcat 7.0.47 tagging.
Regards
Violeta
2013/10/17 sebb seb...@gmail.com
Please note https://issues.apache.org/bugzilla/show_bug.cgi?id=55663
The text in the NOTICE file is wrong.
Thanks.
I'll fix the tag.
Violeta
The proposed Apache Tomcat 7.0.47 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0 implementation.
Note that use of this functionality requires Java 7.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.47/
The Maven
2013/10/16 Mark Thomas ma...@apache.org
The proposed Apache Tomcat 8.0.0 release candidate 5 is now available
for voting.
Given this is a release candidate I am working on the basis that it is
equivalent to an alpha. The main changes since RC4 are:
- Stability fixes in the APR/native
2013/10/18 Violeta Georgieva miles...@gmail.com
The proposed Apache Tomcat 7.0.47 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0
implementation. Note that use of this functionality requires Java 7.
It can be obtained from:
https
Hi,
I'm looking at the issue with javadoc reported by Rainer [1]
I know that we've decided to use the quick-fix tool for javadoc instead of
jdk 7 [2].
But that was before websocket downport that require jdk 7 for building.
What do you think if we start generating javadoc with jdk 7 when
Hi,
2013/10/18 Violeta Georgieva miles...@gmail.com
The proposed Apache Tomcat 7.0.47 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0
implementation. Note that use of this functionality requires Java 7.
It can be obtained from:
https
Hi,
Can you give me permissions for this repository as I cannot commit there.
Thanks
Violeta
2013/10/24 Mark Thomas ma...@apache.org
On 24/10/2013 14:14, Violeta Georgieva wrote:
Hi,
Can you give me permissions for this repository as I cannot commit
there.
From memory this is set up so only PMC members can commit there because
it triggers copies to the archives and the mirrors
The Apache Tomcat team announces the immediate availability of Apache
Tomcat 7.0.47.
Apache Tomcat is an open source software implementation of the Java
Servlet, JavaServer Pages and Java Expression Language technologies.
This release contains a number of bug fixes and improvements compared to
2013/10/24 Mark Thomas ma...@apache.org
On 24/10/2013 14:43, Violeta Georgieva wrote:
2013/10/24 Mark Thomas ma...@apache.org
On 24/10/2013 14:14, Violeta Georgieva wrote:
Hi,
Can you give me permissions for this repository as I cannot commit
there.
From memory this is set up
2013/10/27 Konstantin Kolinko knst.koli...@gmail.com
2013/10/27 Violeta Georgieva miles...@gmail.com:
Can you also remove the old release (7.0.42) and add my key to the KEYS
file?
Both done.
Thanks
Do you have administrative rights in Bugzilla to add new version for
Tomcat 7
2013/10/28 Rainer Jung rainer.j...@kippdata.de
On 28.10.2013 15:32, Christopher Schultz wrote:
Voiletta
On 10/26/13, 3:59 PM, Violeta Georgieva wrote:
The Apache Tomcat team announces the immediate availability of Apache
Tomcat 7.0.47.
Congratulations on your first release!
+1
2013/11/6 Filip Hanik (mailing lists) devli...@hanik.com
Ladies and Gentlemen,
I'm back,
Welcome!
Regards
Violeta
1 - 100 of 957 matches
Mail list logo