Re: [RESULT] Release Apache Taglibs Parent POM 1
thanks Jeremy. 2012/3/1 Jeremy Boynes > +1 votes from olamy, mturk and kkolinko; no -1's > > Issues raised during the vote: > * duplicate LICENSE and NOTICE files, and how to avoid this > * site contents > * version of commons-skin used for site > to be addressed before we release any of the taglibs > > Thanks. I'll promote the staging repo later this week. > Jeremy > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Lei Wang (Rex) rwonly AT apache.org
what does j_security_check do in clustering?
Dear Tomcat devs, I meet a problem when config a web project which using the form based security in clustering. When I set session affinity = true in my front http server, the security check was done in single node, there is no problem with that. But if I set affinity = false, the requests from the security check process are sent to 2 nodes, and it is really strange.. eg: 1. From index.html(NodeA), try to access protected resouce 2. Go to the logon.html(NodeB), I input the id/passwd, and then submit 3. The request looks like sent to NodeA, but did not do any check operation. Does that work as design? that is, if I wanna use form check security, my cluster must be session affinity? Thanks in advance! -Rex
Re: what does j_security_check do in clustering?
hi Mark, Thanks, I will send a mail there. I thought developers hold more knowledge on this. So just want a confirm of my question. -Rex 2009/9/16 Mark Thomas > Rex Wang wrote: > > Dear Tomcat devs, > > > > I meet a problem when config a web project which using the form based > > security in clustering. > > > > When I set session affinity = true in my front http server, the security > > check was done in single node, there is no problem with that. > > But if I set affinity = false, the requests from the security check > process > > are sent to 2 nodes, and it is really strange.. eg: > > > > 1. From index.html(NodeA), try to access protected resouce > > 2. Go to the logon.html(NodeB), I input the id/passwd, and then submit > > 3. The request looks like sent to NodeA, but did not do any check > operation. > > > > Does that work as design? that is, if I wanna use form check security, my > > cluster must be session affinity? > > That would be a question for the users list. > > Mark > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: [taglibs] Time to release 1.2.0?
+1 again.. how is the release going? 2011/3/27 Jeremy Boynes > On Mar 25, 2011, at 2:15 AM, Mark Thomas wrote: > > > On 23/01/2011 20:41, Jeremy Boynes wrote: > >> The only bug remaining that impact the JSTL libraries is #46052 (locale > performance on 1.6). Henri suggested releasing in its current form which > sounds reasonable. Should we release this as 1.2.0? Is this a good version > number - should we use something like 1.2.0-beta? > >> > >> This will be the first release in a long time and the first since the > switch to a Maven based build. The process is described here > >> http://www.apache.org/dev/publishing-maven-artifacts.html > >> > >> I think we need to release the parent POM first to get it in the central > repo, and then the artifacts that depend on it. > >> > >> I'd volunteer to RM this but: > >> 1) I'm not a PMC member (which I don't think matters if we get enough > votes from PMC members) > >> 2) I'd need to update my PGP key in the WoT (somehow) > >> 3) I've not done the above process before so will likely mess things up. > >> > >> If we're ready to do this I'd suggest going for it this week. > >> Thoughts? > > > > +1 > > > > Ping. What happened to this? > > From my side, Olivier's patch for Maven 3 looked good and then my personal > life got in the way. I'll get it applied and tested and then publish a > candidate. > > -- > Jeremy > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Lei Wang (Rex) rwonly AT apache.org
The status of tomcat taglibs project?
Hi Devs, I just checked out the taglibs source code from http://svn.apache.org/repos/asf/tomcat/taglibs/standard/trunk and try to replace the sun implementation in my build. But the first problem jumped in is that I can not even build it. Because maven can not find its parent pom: org.apache.taglibs taglibs-parent 1-SNAPSHOT >>Project ID: null:taglibs-standard:pom:1.2-SNAPSHOT >>Reason: Cannot find parent: org.apache.taglibs:taglibs-parent for project: null:taglibs-standard:pom:1.2-SNAPSHOT for project null:taglibs-standard:pom:1.2-SNAP >>SHOT Could anyone tell me any clue about this? or it has never been built since transferred from jakarta project? And, does tomcat community have any plan to release the taglibs? Any comment is appreciated. Regards, -- Lei Wang (Rex) rwonly AT apache.org
Re: The status of tomcat taglibs project?
Thank you sebb and Jeremy, Glad to see many fixes in the past few weeks. And I have more questions :-) 1. I open a new item(#50064) in bugzilla to discuss bundle-ify the taglibs jars and also provided a patch. Any comments about this idea? 2. When do you plan to make the first release? Our project really wants to switch to the open source implementation.. 3. For the patch in #48773, could anyone help review and apply it? -Rex 2010/9/30 Jeremy Boynes > On Sep 24, 2010, at 11:37 PM, Rex Wang wrote: > > Could anyone tell me any clue about this? or it has never been built > since > > transferred from jakarta project? > > I can confirm I have built it but, as sebb said, you need to install the > parent pom locally first as there's no released version. > > > And, does tomcat community have any plan to release the taglibs? > > We should :-) > -- > Jeremy > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Lei Wang (Rex) rwonly AT apache.org
Re: [taglibs] Pick common format for test class names
+1 for *Test.java 2010/10/8 Jeremy Boynes > We have different formats for test class names and need to specifically > list them in the pom.xml file. > > i'd like to propose picking a standard format and using a single wildcarded > pattern to select them. The defaults for the surefire plugin are: >**/Test*.java >**/*Test.java >**/*TestCase.java > > i would suggest one of the latter 2 to avoid conflicts with inner classes > (e.g. TestTransformSupport$1) > > Thoughts? > Jeremy > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Lei Wang (Rex) rwonly AT apache.org
Re: [taglibs] Release for 1.2, was: The status of tomcat taglibs project?
+1, Thanks for raising this! Jeremy. Also, hope the release can be made as OSGi bundles. -Rex 2010/10/10 Jeremy Boynes > On Oct 9, 2010, at 12:37 AM, Rex Wang wrote: > > > > 2. When do you plan to make the first release? Our project really wants > to > > switch to the open source implementation.. > > Trunk now passes the JSTL1.2 TCK so we can release when we want to. > However, there have already been some large changes in the 1.2 stream (such > as the move to the Tomcat project, using a 1.5 runtime, switching to Maven > build) that will be visible to users so if we are going to make any others > my vote would be to do that before releasing 1.2.0 so they are only impacted > once; examples of these are: > > * using a different XPath implementation to fix the performance issues with > the XML tags (changes dependencies) > * splitting out the 1.0 compatibility support into a different artifact > * clean-up on the Maven POMs (especially any changes that impact the parent > POM) > > We may also need to revise the release process based on the move to the > Tomcat project and Maven build. > > With that in mind, what do people think about shooting for a release > towards the end of the month? -- Lei Wang (Rex) rwonly AT apache.org
Re: [taglibs] [Bug 50064] bundle-ify the taglibs jars
Thanks Jeremy, Is that because the group id dose not start with org.apache.tomcat...? 2010/11/1 Jeremy Boynes > Patch applied but unable to deploy to the snapshot repository. > I don't see an entry for taglibs in Nexus so opening a issue with them to > get us created. > > On Oct 31, 2010, at 11:26 AM, bugzi...@apache.org wrote: > > > https://issues.apache.org/bugzilla/show_bug.cgi?id=50064 > > > > --- Comment #7 from Jeremy Boynes 2010-10-31 > 14:26:45 EDT --- > > Patches applied, thanks. > > > > -- > > Configure bugmail: > https://issues.apache.org/bugzilla/userprefs.cgi?tab=email > > --- You are receiving this mail because: --- > > You are the assignee for the bug. > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Lei Wang (Rex) rwonly AT apache.org
Re: [g...@vmgump]: Project tomcat-taglibs-standard (in module tomcat-taglibs) failed
I don't think so. After deploy the artifacts to apache.snapshots, I think
this problem can go away.
2010/11/2 Jeremy Boynes
> This started failing with r1029387. If I remove the
> bundle from the spec module then the reactor starts
> resolving it again. Could this be something with the bundle plugin not
> working with the package goal?
>
> I'm going to revert the bundle packaging until we can resolve this.
>
> On Nov 1, 2010, at 6:33 PM, Gump wrote:
>
> > To whom it may engage...
> >
> > This is an automated request, but not an unsolicited one. For
> > more information please visit http://gump.apache.org/nagged.html,
> > and/or contact the folk at gene...@gump.apache.org.
> >
> > Project tomcat-taglibs-standard has an issue affecting its community
> integration.
> > This issue affects 2 projects.
> > The current state of this project is 'Failed', with reason 'Build
> Failed'.
> > For reference only, the following projects are affected by this:
> >- tomcat-taglibs-standard : Standard Taglib
> >- tomcat-taglibs-standard-install : JSP Taglibs
> >
> >
> > Full details are available at:
> >
> http://vmgump.apache.org/gump/public/tomcat-taglibs/tomcat-taglibs-standard/index.html
> >
> > That said, some information snippets are provided here.
> >
> > The following annotations (debug/informational/warning/error messages)
> were provided:
> > -INFO- Optional dependency httpunit failed with reason build failed
> > -DEBUG- (Gump generated) Maven2 Settings in:
> /srv/gump/public/workspace/tomcat-taglibs/standard/gump_mvn_settings.xml
> > -INFO- Failed with reason build failed
> > -DEBUG- Maven POM in:
> /srv/gump/public/workspace/tomcat-taglibs/standard/pom.xml
> > -DEBUG- Extracted fallback artifacts from Gump Repository
> >
> >
> >
> > The following work was performed:
> >
> http://vmgump.apache.org/gump/public/tomcat-taglibs/tomcat-taglibs-standard/gump_work/build_tomcat-taglibs_tomcat-taglibs-standard.html
> > Work Name: build_tomcat-taglibs_tomcat-taglibs-standard (Type: Build)
> > Work ended in a state of : Failed
> > Elapsed: 19 secs
> > Command Line: mvn --batch-mode -DskipTests=true --settings
> /srv/gump/public/workspace/tomcat-taglibs/standard/gump_mvn_settings.xml
> package
> > [Working Directory: /srv/gump/public/workspace/tomcat-taglibs/standard]
> > -
> > [INFO] Compiling 7 source files to
> /srv/gump/public/workspace/tomcat-taglibs/standard/impl/target/test-classes
> > [INFO] [surefire:test {execution: default-test}]
> > [INFO] Tests are skipped.
> > [INFO] [bundle:bundle {execution: default-bundle}]
> > [INFO]
>
> > [INFO] Building Apache Standard Taglib - JSTL 1.0 Compatibility
> > [INFO]task-segment: [package]
> > [INFO]
>
> > [INFO] [remote-resources:process {execution: default}]
> > [INFO] snapshot org.apache.taglibs:taglibs-standard-impl:1.2-SNAPSHOT:
> checking for updates from apache.snapshots
> > Downloading:
> http://localhost:8192/repo/m2-snapshot-repository/org/apache/taglibs/taglibs-standard-impl/1.2-SNAPSHOT/taglibs-standard-impl-1.2-SNAPSHOT.jar
> > [INFO] Unable to find resource
> 'org.apache.taglibs:taglibs-standard-impl:jar:1.2-SNAPSHOT' in repository
> apache.snapshots (http://repository.apache.org/snapshots)
> > [INFO]
>
> > [ERROR] BUILD ERROR
> > [INFO]
>
> > [INFO] Failed to resolve dependencies for one or more projects in the
> reactor. Reason: Missing:
> > --
> > 1) org.apache.taglibs:taglibs-standard-impl:jar:1.2-SNAPSHOT
> >
> > Try downloading the file manually from the project website.
> >
> > Then, install it using the command:
> > mvn install:install-file -DgroupId=org.apache.taglibs
> -DartifactId=taglibs-standard-impl -Dversion=1.2-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
> >
> > Alternatively, if you host your own repository you can deploy the file
> there:
> > mvn deploy:deploy-file -DgroupId=org.apache.taglibs
> -DartifactId=taglibs-standard-impl -Dversion=1.2-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> >
> > Path to dependency:
> > 1) org.apache.taglibs:taglibs-standard-compat:bundle:1.2-SNAPSHOT
> > 2) org.apache.taglibs:taglibs-standard-impl:jar:1.2-SNAPSHOT
> >
> > --
> > 1 required artifact is missing.
> >
> > for artifact:
> > org.apache.taglibs:taglibs-standard-compat:bundle:1.2-SNAPSHOT
> >
> > from the specified remote repositories:
> > gump-central (http://localhost:8192/maven2),
> > gump-apache.snapshots (
> http://localhost:8192/repo/m2-snapshot-repository)
> >
> >
> >
> > [INFO]
>
> > [INFO] For more information, run Maven with the -e switch
> >
Re: [taglibs] [Bug 50064] bundle-ify the taglibs jars
Thank you very much! I will pull in the bundles to Geronimo to have a try. -Rex 2010/11/4 Jeremy Boynes > On Nov 1, 2010, at 9:15 PM, Jeremy Boynes wrote: > > > On Nov 1, 2010, at 7:42 PM, Rex Wang wrote: > > > >> Thanks Jeremy, > >> > >> Is that because the group id dose not start with org.apache.tomcat...? > > > > I think so. I opened the issue asking for org.apache.taglibs to be added > as that's the current group id. > > https://issues.apache.org/jira/browse/INFRA-3129 > > > > Group has been enabled. A build of r1030841 to the snapshot repo. Hope it > works :-) > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Lei Wang (Rex) rwonly AT apache.org
Re: [taglibs] Tab police
What's the formatter you plan to use? Is it public and other committer obeyed? Otherwise, it will mess up again in future.. Anyway, +1 for tab replacement with 4 spaces. -Rex 2010/11/16 Jeremy Boynes > As well as the tabs, there are broader inconsistencies in the style (e.g. > consistent braces, missing javadoc, and the like) that lead to IDE warnings. > > How about running everything through a re-formatter to clean this up? > Downside is that it will make back-patching harder. > +1 from me. > > On Nov 16, 2010, at 5:28 AM, bugzi...@apache.org wrote: > > > https://issues.apache.org/bugzilla/show_bug.cgi?id=50279 > > > > Summary: Tab police > > Product: Taglibs > > Version: unspecified > > Platform: PC > >OS/Version: Windows XP > >Status: NEW > > Severity: normal > > Priority: P2 > > Component: Unknown Taglib > >AssignedTo: dev@tomcat.apache.org > >ReportedBy: s...@apache.org > > > > > > Created an attachment (id=26301) > > --> (https://issues.apache.org/bugzilla/attachment.cgi?id=26301) > > Fix tabs in examples code > > > > There are oodles of tabs in the Taglibs code. > > > > Tabs seem to be set at 8 spaces, at least in the examples section. > > > > I can provide patches for the other code if required. > > > > -- > > Configure bugmail: > https://issues.apache.org/bugzilla/userprefs.cgi?tab=email > > --- You are receiving this mail because: --- > > You are the assignee for the bug. > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Lei Wang (Rex) rwonly AT apache.org
Re: [taglibs] XPath support
2010/10/3 Jeremy Boynes > On Jul 15, 2010, at 12:19 AM, Henri Yandell wrote: > > > On Wed, Jul 14, 2010 at 8:45 PM, Jeremy Boynes > wrote: > >> On Jul 12, 2010, at 7:04 PM, Jeremy Boynes wrote: > >> > >>> I'm going to ping Xalan about the increase in time taken as expressions > are evaluated as I would assume I'm doing something silly. > >> > >> I looked into the Xalan implementation and the problem appears to be in > creation of the DTM used by the underlying implementation. To evaluate the > expression it walks up the DOM tree to the parent and then iterates forward > over the tree until it reaches the initial context node. This leads to a > linear increase in execution time as the context node progresses through the > NodeList from the . > >> > >> I changed and to use Jaxen and did not see this > issue. The execution time for xpath evalutation over 1000 iterations was > constant and substantially faster than with Xalan: total of 62ms reparsing > each time or 21ms if precompiled, down from 1800ms. > >> > >> In light of this I'd like to propose we switch to Jaxen and add it as a > dependency. > > > > Absolutely: +1 > > > > Great work :) > > I've not committed these changes as the latest version of Jaxen is not > available in the Maven repo and there did not appear to be much interest in > doing so. We might be able to get similar improvements using JXPath. > > Could we start the release process without resolving this performance issue? If not, the servicemix bundled jaxen http://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.jaxen/1.1.1_1/ might be a good choice as the dependency. -Rex > -- > Jeremy > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Lei Wang (Rex) rwonly AT apache.org
Re: DO NOT REPLY [Bug 50462] xalan import should not be optional in maven-bundle-plugin
2010/12/22 Jeremy Boynes > On Dec 21, 2010, at 6:15 PM, bugzi...@apache.org wrote: > > > https://issues.apache.org/bugzilla/show_bug.cgi?id=50462 > > > > --- Comment #3 from Rex Wang 2010-12-21 21:15:19 EST > --- > > (In reply to comment #2) > >> It's marked optional in Maven as it is only needed if someone is using > the XML > >> tags. > >> > >> Is there a way to mimic that with the OSGi references? > > > > Not sure about that. > > > > At least, IMO, that is not the correct way by using optional:=resolution > in > > import-package to achieve the requirement. > > > > I think the optional:=resolution directive is used to express that if > osgi > > framework can not resolve the package, the codes in this bundle may use > the > > implementation from itself or from jdk. > > > > So if the codes have hard dependency to (explicitly import) a package, we > > should not make it as optional resolution. > > Perhaps the changes needed to address the performance issue in #27717 are > relevant here. > These stem from issues in Xalan's implementation which would also apply if > we tried to use the JDK's implementation. I had a prototype working with > Jaxen but the project is pushing builds to the Maven repos and does not seem > very active (like, no-one replied to a recent committer call) so depending > on it could be problematic. I was thinking of using JXPath instead (from > commons). > I also don't find JXPATH in maven repo.. However, you also can use the servicemix bundled one: http://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.commons-jxpath, But that is not the least version 1.3. > > With multiple options out there, perhaps we could just have taglibs use an > interface and provide wrappers for each as separate modules. if we did that, > is that something that could be easily handled with OSGi? > I am not very familiar with XPATH. Do you mean the approach like spi? IIUC, xalan implements the spi of javax.xml.transform.TransformerFactory and javax.xml.xpath.XPathFactory. So if xalan is in the path, we can choose it as the xpath implementation. I am not sure if jaxen and jxpath implement the spi either. Why not move to the standard api in jdk instead of defining new apis and wrappers? -Rex > > Thanks > Jeremy > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Lei Wang (Rex) rwonly AT apache.org
Re: DO NOT REPLY [Bug 50462] xalan import should not be optional in maven-bundle-plugin
2010/12/22 Jeremy Boynes > On Dec 21, 2010, at 10:28 PM, Rex Wang wrote: > > > 2010/12/22 Jeremy Boynes > >> > >> Perhaps the changes needed to address the performance issue in #27717 > are > >> relevant here. > >> These stem from issues in Xalan's implementation which would also apply > if > >> we tried to use the JDK's implementation. I had a prototype working with > >> Jaxen but the project is pushing builds to the Maven repos and does not > seem > >> very active (like, no-one replied to a recent committer call) so > depending > >> on it could be problematic. I was thinking of using JXPath instead (from > >> commons). > >> > > I also don't find JXPATH in maven repo.. However, you also can use the > > servicemix bundled one: > > > http://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.commons-jxpath > , > > But that is not the least version 1.3. > > The official one is at: > http://repo2.maven.org/maven2/commons-jxpath/commons-jxpath/1.3/ > > Not sure if it's an OSGi bundle though. > I just saw it. Yes, it is a bundle. But seems made 2 years ago. Is jxpath actively maintained now? Is that what ServiceMix is doing when repackaging? > Yes. > > > > > >> > >> With multiple options out there, perhaps we could just have taglibs use > an > >> interface and provide wrappers for each as separate modules. if we did > that, > >> is that something that could be easily handled with OSGi? > >> > > > > I am not very familiar with XPATH. Do you mean the approach like spi? > > IIUC, xalan implements the spi of javax.xml.transform.TransformerFactory > and > > javax.xml.xpath.XPathFactory. So if xalan is in the path, we can choose > it > > as the xpath implementation. I am not sure if jaxen and jxpath implement > the > > spi either. > > Why not move to the standard api in jdk instead of defining new apis and > > wrappers? > > The XPath implementation in Oracle's JDK was originally based on Xalan and > has the same performance issue. > > One issue with the JAXP API is that it does not allow context to be passed > to the evaluation and so the XPath position() and last() functions can't be > supported (at least, I've not figured out how). Now the current > implementation does not support them either (see #22765) so this may not be > a major issue, but the proprietary APIs in Jaxen and JXPath should enable > this (would need to code it to be sure). > > How about: > * define our own API that allows context to be passed > * create a context-free wrapper for JAXP and remove the hard dependency on > Xalan (solving the optional bundle issue) > * create other wrappers for Jaxen and/or JXPath that can use the context > We could proceed with a release based on the first two steps alone as > there's no regression. > +0 if the reason of defining our own api is only to resolve #22765, since it is not required by spec. And, the performance issue is not a blocker to you to do release? Thanks -Rex > -- > Jeremy > > -- Lei Wang (Rex) rwonly AT apache.org
Re: [taglibs] Time to release 1.2.0?
+1 2011/1/24 Jeremy Boynes > The only bug remaining that impact the JSTL libraries is #46052 (locale > performance on 1.6). Henri suggested releasing in its current form which > sounds reasonable. Should we release this as 1.2.0? Is this a good version > number - should we use something like 1.2.0-beta? > > This will be the first release in a long time and the first since the > switch to a Maven based build. The process is described here >http://www.apache.org/dev/publishing-maven-artifacts.html > > I think we need to release the parent POM first to get it in the central > repo, and then the artifacts that depend on it. > > I'd volunteer to RM this but: > 1) I'm not a PMC member (which I don't think matters if we get enough votes > from PMC members) > 2) I'd need to update my PGP key in the WoT (somehow) > 3) I've not done the above process before so will likely mess things up. > > If we're ready to do this I'd suggest going for it this week. > Thoughts? > Jeremy > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Lei Wang (Rex) rwonly AT apache.org
Re: [RESULTS][VOTE] Release build 6.0.25
Hi, any plan when will 6.0.26 released? Our project has a dependency on it.. Thanks -Rex 2010/3/3 Mladen Turk > On 03/03/2010 08:33 AM, jean-frederic clere wrote: > >> Stable [3] >> Broken [2] >> >> So we go for a 6.0.26. Please commit the stuff voted in STATUS.txt >> >> > And few ones that need votes :) > E.g the trivial exception throwing fix for APR connector on shutdown. > > Regards > -- > ^TM > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Lei Wang (Rex) rwonly AT apache.org
Re: [RESULTS][VOTE] Release build 6.0.25
Thanks! 2010/3/4 jean-frederic clere > On 03/04/2010 04:04 AM, Rex Wang wrote: > > Hi, any plan when will 6.0.26 released? Our project has a dependency on > it.. > > There is still a regression to vote (and test): bug 48827. > If no other problems the release should happen early next week. > > Cheers > > Jean-Frederic > > > > > Thanks > > > > -Rex > > > > 2010/3/3 Mladen Turk > > > >> On 03/03/2010 08:33 AM, jean-frederic clere wrote: > >> > >>> Stable [3] > >>> Broken [2] > >>> > >>> So we go for a 6.0.26. Please commit the stuff voted in STATUS.txt > >>> > >>> > >> And few ones that need votes :) > >> E.g the trivial exception throwing fix for APR connector on shutdown. > >> > >> Regards > >> -- > >> ^TM > >> > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > >> For additional commands, e-mail: dev-h...@tomcat.apache.org > >> > >> > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Lei Wang (Rex) rwonly AT apache.org
