You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Kalle Korhonen <ka...@gmail.com> on 2013/03/31 08:17:51 UTC
T5.3.7 release anyone?
Is anybody in need of T5.3.7? I'm not quite ready myself just yet but there
are a few relevant fixes for us and I could put a few more in. Is anybody
else looking for a 5.3.7 release? Massimo, I think you've done the last
5.3.x releases. How's your experience been regarding the release process?
Is everything documented, any gotchas, pain points etc? Or would you
perhaps be willing to cut one more release yourself?
Kalle
Re: T5.3.7 release anyone?
Posted by Massimo Lusetti <ml...@gmail.com>.
On Mon, Apr 22, 2013 at 5:16 AM, Kalle Korhonen
<ka...@gmail.com>wrote:
On Sun, Apr 21, 2013 at 8:52 AM, Massimo Lusetti <ml...@gmail.com> wrote:
>
> > On Thu, Apr 18, 2013 at 7:15 PM, Kalle Korhonen
> > <ka...@gmail.com>wrote:
> > Hi Kalle, here PlastiUtilsTests.groovy is failing at line 33 which comes
> > from your commit 742fac0e
> > Please give it a look.
> >
>
> Hmm, odd works for me (I did clean before):
> :plastic:test
>
> BUILD SUCCESSFUL
>
> Total time: 19.463 secs
> ---
>
> What's the error, you sure you've recompiled PlasticInternalUtils since
> I've made getStreamForPath package private instead of private? Suppose it
> could be some kind of OS-specific thing since it's dealing with file paths.
> Need to know your stack trace to say more.
>
I'm building on a Linux box as a normal user with Oracle Java :
java version "1.7.0_10"
Java(TM) SE Runtime Environment (build 1.7.0_10-b18)
Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode)
Hadn't had time to investigate more deeper but it fails cause at lien 411
of PlasticInternalUtils.java the classloader method getResource return a
null URL, btw the file you're creating in the tests is there.
I'll looking at it this evening
--
Massimo
Re: T5.3.7 release anyone?
Posted by Kalle Korhonen <ka...@gmail.com>.
Thanks for fixing it, exactly, we need to use SeleniumTestCase only.
AbstractIntegrationTestSuite had a hard dependency on Jetty 5. I didn't
have the project on my workspace but I don't know why the gradle build
didn't catch compilation failure.
Kalle
On Tue, Apr 23, 2013 at 1:13 AM, Massimo Lusetti <ml...@gmail.com> wrote:
> On Mon, Apr 22, 2013 at 5:16 AM, Kalle Korhonen
> <ka...@gmail.com>wrote:
>
> On Sun, Apr 21, 2013 at 8:52 AM, Massimo Lusetti <ml...@gmail.com>
> wrote:
> >
> > > On Thu, Apr 18, 2013 at 7:15 PM, Kalle Korhonen
> > > <ka...@gmail.com>wrote:
> > > Hi Kalle, here PlastiUtilsTests.groovy is failing at line 33 which
> comes
> > > from your commit 742fac0e
> > > Please give it a look.
> > >
> >
> > Hmm, odd works for me (I did clean before):
> > :plastic:test
> >
> > BUILD SUCCESSFUL
> >
> > Total time: 19.463 secs
> > ---
> >
> > What's the error, you sure you've recompiled PlasticInternalUtils since
> > I've made getStreamForPath package private instead of private? Suppose it
> > could be some kind of OS-specific thing since it's dealing with file
> paths.
> > Need to know your stack trace to say more.
> >
> > Kalle
> >
> > Kalle
> >
>
>
> Hi Kalle,
> I would ask for you to check the repository (branch 5.3) cause to me is
> seems you've deleted AbstractIntegrationTestSuite in f656ce399
> but UploadIntegrationTest still reference it.
>
> Take a look:
>
> https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=tree;f=tapestry-test/src/main/java/org/apache/tapestry5/test;h=be928ee5a6dd3417143642dda4c2f837ad92bd3e;hb=5.3
>
> https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=blob;f=tapestry-upload/src/test/java/org/apache/tapestry5/upload/integration/UploadIntegrationTest.java;h=8ed9a5cede8a5f47fc27d24fcccc899d3c042286;hb=5.3
>
>
> Cheers
> --
> Massimo
>
Re: T5.3.7 release anyone?
Posted by Massimo Lusetti <ml...@gmail.com>.
On Mon, Apr 22, 2013 at 5:16 AM, Kalle Korhonen
<ka...@gmail.com>wrote:
On Sun, Apr 21, 2013 at 8:52 AM, Massimo Lusetti <ml...@gmail.com> wrote:
>
> > On Thu, Apr 18, 2013 at 7:15 PM, Kalle Korhonen
> > <ka...@gmail.com>wrote:
> > Hi Kalle, here PlastiUtilsTests.groovy is failing at line 33 which comes
> > from your commit 742fac0e
> > Please give it a look.
> >
>
> Hmm, odd works for me (I did clean before):
> :plastic:test
>
> BUILD SUCCESSFUL
>
> Total time: 19.463 secs
> ---
>
> What's the error, you sure you've recompiled PlasticInternalUtils since
> I've made getStreamForPath package private instead of private? Suppose it
> could be some kind of OS-specific thing since it's dealing with file paths.
> Need to know your stack trace to say more.
>
> Kalle
>
> Kalle
>
Hi Kalle,
I would ask for you to check the repository (branch 5.3) cause to me is
seems you've deleted AbstractIntegrationTestSuite in f656ce399
but UploadIntegrationTest still reference it.
Take a look:
https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=tree;f=tapestry-test/src/main/java/org/apache/tapestry5/test;h=be928ee5a6dd3417143642dda4c2f837ad92bd3e;hb=5.3
https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=blob;f=tapestry-upload/src/test/java/org/apache/tapestry5/upload/integration/UploadIntegrationTest.java;h=8ed9a5cede8a5f47fc27d24fcccc899d3c042286;hb=5.3
Cheers
--
Massimo
Re: T5.3.7 release anyone?
Posted by Kalle Korhonen <ka...@gmail.com>.
On Sun, Apr 21, 2013 at 8:52 AM, Massimo Lusetti <ml...@gmail.com> wrote:
> On Thu, Apr 18, 2013 at 7:15 PM, Kalle Korhonen
> <ka...@gmail.com>wrote:
> Hi Kalle, here PlastiUtilsTests.groovy is failing at line 33 which comes
> from your commit 742fac0e
> Please give it a look.
>
Hmm, odd works for me (I did clean before):
:plastic:test
BUILD SUCCESSFUL
Total time: 19.463 secs
---
What's the error, you sure you've recompiled PlasticInternalUtils since
I've made getStreamForPath package private instead of private? Suppose it
could be some kind of OS-specific thing since it's dealing with file paths.
Need to know your stack trace to say more.
Kalle
Kalle
Re: T5.3.7 release anyone?
Posted by Massimo Lusetti <ml...@gmail.com>.
On Thu, Apr 18, 2013 at 7:15 PM, Kalle Korhonen
<ka...@gmail.com>wrote:
Totally, I had several tests failing in 5.3. In fact, when I started, the
> majority of the tests didn't run at all because the version of Selenium
> used was too old. I can take a look at some I suspect can be easily fixed
> but not signing up to guarantee they all succeed.
>
>
Hi Kalle, here PlastiUtilsTests.groovy is failing at line 33 which comes
from your commit 742fac0e
Please give it a look.
Cheers
--
Massimo
Re: T5.3.7 release anyone?
Posted by Kalle Korhonen <ka...@gmail.com>.
Totally, I had several tests failing in 5.3. In fact, when I started, the
majority of the tests didn't run at all because the version of Selenium
used was too old. I can take a look at some I suspect can be easily fixed
but not signing up to guarantee they all succeed.
Kalle
On Thu, Apr 18, 2013 at 5:38 AM, Taha Hafeez Siddiqi <
tawus.tapestry@gmail.com> wrote:
> Hi Kalle
>
> My tests keep failing in the 5.3 branch. Are you seeing any such thing.
> After cloning I am just running
>
> ./gradlew clean test
>
> I am running the tests on an OS 10.8
>
> Darwin iMac.local 12.0.0 Darwin Kernel Version 12.0.0: Sun Jun 24 23:00:16
> PDT 2012; root:xnu-2050.7.9~1/RELEASE_X86_64 x86_64
>
> Java version is : sun/oracle java 1.6.0_37
>
> 9 tests are failing in tapestry-core. Here are stack trace for two of them.
>
>
>
> checks_for_eof
> Test class: org.apache.tapestry5.internal.services.ClientDataEncoderTest
>
> java.lang.RuntimeException: Exception constructing service
> 'ClientDataEncoder': Error invoking constructor public
> org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager)
> throws java.io.UnsupportedEncodingException: Unable to delegate method
> invocation to property 'request' of <Proxy for
> RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the
> property is null.
> at
> org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:75)
> at
> org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.createObject(JustInTimeObjectCreator.java:54)
> at $ClientDataEncoder_12f6054338afd086.delegate(Unknown Source)
> at $ClientDataEncoder_12f6054338afd086.createSink(Unknown Source)
> at
> org.apache.tapestry5.internal.services.ClientDataEncoderTest.checks_for_eof(ClientDataEncoderTest.java:68)
> at
> org.gradle.api.internal.tasks.testing.testng.TestNGTestClassProcessor.stop(TestNGTestClassProcessor.java:103)
>
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:58)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at $Proxy2.stop(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.stop(TestWorker.java:110)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.TypeCastDispatch.dispatch(TypeCastDispatch.java:30)
> at
> org.gradle.messaging.remote.internal.WorkerProtocol.handleIncoming(WorkerProtocol.java:53)
> at
> org.gradle.messaging.remote.internal.WorkerProtocol.handleIncoming(WorkerProtocol.java:31)
> at
> org.gradle.messaging.remote.internal.ProtocolStack$ProtocolStage.handleIncoming(ProtocolStack.java:167)
> at
> org.gradle.messaging.remote.internal.ProtocolStack$BottomStage.handleIncoming(ProtocolStack.java:277)
> at
> org.gradle.messaging.remote.internal.ProtocolStack$BottomConnection$1.run(ProtocolStack.java:299)
> at
> org.gradle.messaging.remote.internal.ProtocolStack$ExecuteRunnable.dispatch(ProtocolStack.java:120)
> at
> org.gradle.messaging.remote.internal.ProtocolStack$ExecuteRunnable.dispatch(ProtocolStack.java:116)
> at
> org.gradle.messaging.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:132)
> at
> org.gradle.messaging.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:33)
> at
> org.gradle.messaging.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:72)
> at
> org.gradle.messaging.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: org.apache.tapestry5.ioc.internal.OperationException: Error
> invoking constructor public
> org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager)
> throws java.io.UnsupportedEncodingException: Unable to delegate method
> invocation to property 'request' of <Proxy for
> RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the
> property is null.
> at
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.logAndRethrow(OperationTrackerImpl.java:121)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:88)
> at
> org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
> at
> org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
> at
> org.apache.tapestry5.ioc.internal.util.ConstructionPlan.createObject(ConstructionPlan.java:60)
> at
> org.apache.tapestry5.ioc.internal.ConstructorServiceCreator.createObject(ConstructorServiceCreator.java:61)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
> at
> org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
> at
> org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator.createObject(OperationTrackingObjectCreator.java:49)
> at
> org.apache.tapestry5.ioc.internal.SingletonServiceLifecycle.createService(SingletonServiceLifecycle.java:29)
> at
> org.apache.tapestry5.ioc.internal.LifecycleWrappedServiceCreator.createObject(LifecycleWrappedServiceCreator.java:46)
> at
> org.apache.tapestry5.ioc.internal.AdvisorStackBuilder.createObject(AdvisorStackBuilder.java:63)
> at
> org.apache.tapestry5.ioc.internal.InterceptorStackBuilder.createObject(InterceptorStackBuilder.java:54)
> at
> org.apache.tapestry5.ioc.internal.RecursiveServiceCreationCheckWrapper.createObject(RecursiveServiceCreationCheckWrapper.java:60)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
> at
> org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
> at
> org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator.createObject(OperationTrackingObjectCreator.java:49)
> at
> org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:66)
> ... 59 more
> Caused by: java.lang.RuntimeException: Error invoking constructor public
> org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager)
> throws java.io.UnsupportedEncodingException: Unable to delegate method
> invocation to property 'request' of <Proxy for
> RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the
> property is null.
> at
> org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:57)
> at
> org.apache.tapestry5.ioc.internal.util.LoggingInvokableWrapper.invoke(LoggingInvokableWrapper.java:42)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
> ... 79 more
> Caused by: java.lang.NullPointerException: Unable to delegate method
> invocation to property 'request' of <Proxy for
> RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the
> property is null.
> at $Request_12f6054338afd08b.readProperty(Unknown Source)
> at $Request_12f6054338afd08b.isXHR(Unknown Source)
> at $Request_12f6054338afd04a.isXHR(Unknown Source)
> at
> org.apache.tapestry5.internal.alerts.AlertManagerImpl.alert(AlertManagerImpl.java:69)
> at
> org.apache.tapestry5.internal.alerts.AlertManagerImpl.error(AlertManagerImpl.java:62)
> at $AlertManager_12f6054338afd088.error(Unknown Source)
> at
> org.apache.tapestry5.internal.services.ClientDataEncoderImpl.<init>(ClientDataEncoderImpl.java:59)
> at
> org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:48)
> ... 81 more
> ... Removed 34 stack frames
>
>
> multiple_changes
> Test class:
> org.apache.tapestry5.internal.services.ClientPersistentFieldStorageImplTest
> java.lang.RuntimeException: Exception constructing service
> 'ClientDataEncoder': Error invoking constructor public
> org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager)
> throws java.io.UnsupportedEncodingException: Unable to delegate method
> invocation to property 'request' of <Proxy for
> RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the
> property is null.
> at
> org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:75)
> at
> org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.createObject(JustInTimeObjectCreator.java:54)
> at $ClientDataEncoder_12f6054338afd086.delegate(Unknown Source)
> at $ClientDataEncoder_12f6054338afd086.createSink(Unknown Source)
> at
> org.apache.tapestry5.internal.services.ClientPersistentFieldStorageImpl.refreshClientData(ClientPersistentFieldStorageImpl.java:267)
> at
> org.apache.tapestry5.internal.services.ClientPersistentFieldStorageImpl.updateLink(ClientPersistentFieldStorageImpl.java:137)
> at
> org.apache.tapestry5.internal.services.ClientPersistentFieldStorageImplTest.multiple_changes(ClientPersistentFieldStorageImplTest.java:159)
> at
> org.gradle.api.internal.tasks.testing.testng.TestNGTestClassProcessor.stop(TestNGTestClassProcessor.java:103)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:58)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at $Proxy2.stop(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.stop(TestWorker.java:110)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.TypeCastDispatch.dispatch(TypeCastDispatch.java:30)
> at
> org.gradle.messaging.remote.internal.WorkerProtocol.handleIncoming(WorkerProtocol.java:53)
> at
> org.gradle.messaging.remote.internal.WorkerProtocol.handleIncoming(WorkerProtocol.java:31)
> at
> org.gradle.messaging.remote.internal.ProtocolStack$ProtocolStage.handleIncoming(ProtocolStack.java:167)
> at
> org.gradle.messaging.remote.internal.ProtocolStack$BottomStage.handleIncoming(ProtocolStack.java:277)
> at
> org.gradle.messaging.remote.internal.ProtocolStack$BottomConnection$1.run(ProtocolStack.java:299)
> at
> org.gradle.messaging.remote.internal.ProtocolStack$ExecuteRunnable.dispatch(ProtocolStack.java:120)
> at
> org.gradle.messaging.remote.internal.ProtocolStack$ExecuteRunnable.dispatch(ProtocolStack.java:116)
> at
> org.gradle.messaging.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:132)
> at
> org.gradle.messaging.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:33)
> at
> org.gradle.messaging.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:72)
> at
> org.gradle.messaging.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: org.apache.tapestry5.ioc.internal.OperationException: Error
> invoking constructor public
> org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager)
> throws java.io.UnsupportedEncodingException: Unable to delegate method
> invocation to property 'request' of <Proxy for
> RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the
> property is null.
> at
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.logAndRethrow(OperationTrackerImpl.java:121)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:88)
> at
> org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
> at
> org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
> at
> org.apache.tapestry5.ioc.internal.util.ConstructionPlan.createObject(ConstructionPlan.java:60)
> at
> org.apache.tapestry5.ioc.internal.ConstructorServiceCreator.createObject(ConstructorServiceCreator.java:61)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
> at
> org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
> at
> org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator.createObject(OperationTrackingObjectCreator.java:49)
> at
> org.apache.tapestry5.ioc.internal.SingletonServiceLifecycle.createService(SingletonServiceLifecycle.java:29)
> at
> org.apache.tapestry5.ioc.internal.LifecycleWrappedServiceCreator.createObject(LifecycleWrappedServiceCreator.java:46)
> at
> org.apache.tapestry5.ioc.internal.AdvisorStackBuilder.createObject(AdvisorStackBuilder.java:63)
> at
> org.apache.tapestry5.ioc.internal.InterceptorStackBuilder.createObject(InterceptorStackBuilder.java:54)
> at
> org.apache.tapestry5.ioc.internal.RecursiveServiceCreationCheckWrapper.createObject(RecursiveServiceCreationCheckWrapper.java:60)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
> at
> org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
> at
> org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator.createObject(OperationTrackingObjectCreator.java:49)
> at
> org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:66)
> ... 61 more
> Caused by: java.lang.RuntimeException: Error invoking constructor public
> org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager)
> throws java.io.UnsupportedEncodingException: Unable to delegate method
> invocation to property 'request' of <Proxy for
> RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the
> property is null.
> at
> org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:57)
> at
> org.apache.tapestry5.ioc.internal.util.LoggingInvokableWrapper.invoke(LoggingInvokableWrapper.java:42)
> at
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
> ... 81 more
> Caused by: java.lang.NullPointerException: Unable to delegate method
> invocation to property 'request' of <Proxy for
> RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the
> property is null.
> at $Request_12f6054338afd08b.readProperty(Unknown Source)
> at $Request_12f6054338afd08b.isXHR(Unknown Source)
> at $Request_12f6054338afd04a.isXHR(Unknown Source)
> at
> org.apache.tapestry5.internal.alerts.AlertManagerImpl.alert(AlertManagerImpl.java:69)
> at
> org.apache.tapestry5.internal.alerts.AlertManagerImpl.error(AlertManagerImpl.java:62)
> at $AlertManager_12f6054338afd088.error(Unknown Source)
> at
> org.apache.tapestry5.internal.services.ClientDataEncoderImpl.<init>(ClientDataEncoderImpl.java:59)
> at
> org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:48)
> ... 83 more
> ... Removed 34 stack frames
>
>
> regards
> Taha
>
>
> On 17-Apr-2013, at 11:43 PM, Kalle Korhonen <ka...@gmail.com>
> wrote:
>
> > On Wed, Apr 17, 2013 at 12:49 AM, Massimo Lusetti <mlusetti@gmail.com
> >wrote:
> >
> >> On Mon, Apr 15, 2013 at 3:30 PM, Kalle Korhonen
> >> <ka...@gmail.com>wrote:
> >>>
> >> Thanks, going to spin it asap, maybe the weekend.
> >>
> >
> > Thanks Massimo, appreciated!
> >
> > Kalle
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: T5.3.7 release anyone?
Posted by Alejandro Scandroli <al...@gmail.com>.
Hi Taha
In the 5.3.6 tag there is a fix for issues with the
ClientDataEncoderTest that wasn't merged back to the 5.3 branch.
| * aac42f1 Fixed TAP5-2013: "Parameters" table often too wide in
component javadocs Also fixed broken tapestry.png image on JavaDoc
index page
| * 742fac0 FIXED - TAP5-1995: Tapestry5 Application can not be
deployed as Tomcat7 HotDeploy Package - apply Chris Poulsen's patch -
add test, make PlasticInternalUtils.getStreamForPath() package private
| | * 5c777af (tag: 5.3.6) Fix some tests broken by a recent change to
ClientDataEncoderImpl
| | * 0eacb8c Roll version number forward to 5.3.6 prior to release
| |/
| * 3b5badd Use the application root package, not the application
version number, as the provisional HMAC passphrase
This is the commit:
https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=5c777afe5a99399290de8f7b56d69ca5e46c7e67
Looks like it could be related to the issue you are experiencing.
Cheers.
Alejandro.
On Thu, Apr 18, 2013 at 2:38 PM, Taha Hafeez Siddiqi
<ta...@gmail.com> wrote:
> Hi Kalle
>
> My tests keep failing in the 5.3 branch. Are you seeing any such thing. After cloning I am just running
>
> ./gradlew clean test
>
> I am running the tests on an OS 10.8
>
> Darwin iMac.local 12.0.0 Darwin Kernel Version 12.0.0: Sun Jun 24 23:00:16 PDT 2012; root:xnu-2050.7.9~1/RELEASE_X86_64 x86_64
>
> Java version is : sun/oracle java 1.6.0_37
>
> 9 tests are failing in tapestry-core. Here are stack trace for two of them.
>
>
>
> checks_for_eof
> Test class: org.apache.tapestry5.internal.services.ClientDataEncoderTest
>
> java.lang.RuntimeException: Exception constructing service 'ClientDataEncoder': Error invoking constructor public org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager) throws java.io.UnsupportedEncodingException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
> at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:75)
> at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.createObject(JustInTimeObjectCreator.java:54)
> at $ClientDataEncoder_12f6054338afd086.delegate(Unknown Source)
> at $ClientDataEncoder_12f6054338afd086.createSink(Unknown Source)
> at org.apache.tapestry5.internal.services.ClientDataEncoderTest.checks_for_eof(ClientDataEncoderTest.java:68)
> at org.gradle.api.internal.tasks.testing.testng.TestNGTestClassProcessor.stop(TestNGTestClassProcessor.java:103)
>
> at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:58)
> at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at $Proxy2.stop(Unknown Source)
> at org.gradle.api.internal.tasks.testing.worker.TestWorker.stop(TestWorker.java:110)
> at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at org.gradle.messaging.remote.internal.TypeCastDispatch.dispatch(TypeCastDispatch.java:30)
> at org.gradle.messaging.remote.internal.WorkerProtocol.handleIncoming(WorkerProtocol.java:53)
> at org.gradle.messaging.remote.internal.WorkerProtocol.handleIncoming(WorkerProtocol.java:31)
> at org.gradle.messaging.remote.internal.ProtocolStack$ProtocolStage.handleIncoming(ProtocolStack.java:167)
> at org.gradle.messaging.remote.internal.ProtocolStack$BottomStage.handleIncoming(ProtocolStack.java:277)
> at org.gradle.messaging.remote.internal.ProtocolStack$BottomConnection$1.run(ProtocolStack.java:299)
> at org.gradle.messaging.remote.internal.ProtocolStack$ExecuteRunnable.dispatch(ProtocolStack.java:120)
> at org.gradle.messaging.remote.internal.ProtocolStack$ExecuteRunnable.dispatch(ProtocolStack.java:116)
> at org.gradle.messaging.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:132)
> at org.gradle.messaging.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:33)
> at org.gradle.messaging.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:72)
> at org.gradle.messaging.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: org.apache.tapestry5.ioc.internal.OperationException: Error invoking constructor public org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager) throws java.io.UnsupportedEncodingException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
> at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.logAndRethrow(OperationTrackerImpl.java:121)
> at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:88)
> at org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
> at org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
> at org.apache.tapestry5.ioc.internal.util.ConstructionPlan.createObject(ConstructionPlan.java:60)
> at org.apache.tapestry5.ioc.internal.ConstructorServiceCreator.createObject(ConstructorServiceCreator.java:61)
> at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45)
> at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
> at org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
> at org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
> at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator.createObject(OperationTrackingObjectCreator.java:49)
> at org.apache.tapestry5.ioc.internal.SingletonServiceLifecycle.createService(SingletonServiceLifecycle.java:29)
> at org.apache.tapestry5.ioc.internal.LifecycleWrappedServiceCreator.createObject(LifecycleWrappedServiceCreator.java:46)
> at org.apache.tapestry5.ioc.internal.AdvisorStackBuilder.createObject(AdvisorStackBuilder.java:63)
> at org.apache.tapestry5.ioc.internal.InterceptorStackBuilder.createObject(InterceptorStackBuilder.java:54)
> at org.apache.tapestry5.ioc.internal.RecursiveServiceCreationCheckWrapper.createObject(RecursiveServiceCreationCheckWrapper.java:60)
> at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45)
> at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
> at org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
> at org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
> at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator.createObject(OperationTrackingObjectCreator.java:49)
> at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:66)
> ... 59 more
> Caused by: java.lang.RuntimeException: Error invoking constructor public org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager) throws java.io.UnsupportedEncodingException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
> at org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:57)
> at org.apache.tapestry5.ioc.internal.util.LoggingInvokableWrapper.invoke(LoggingInvokableWrapper.java:42)
> at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
> ... 79 more
> Caused by: java.lang.NullPointerException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
> at $Request_12f6054338afd08b.readProperty(Unknown Source)
> at $Request_12f6054338afd08b.isXHR(Unknown Source)
> at $Request_12f6054338afd04a.isXHR(Unknown Source)
> at org.apache.tapestry5.internal.alerts.AlertManagerImpl.alert(AlertManagerImpl.java:69)
> at org.apache.tapestry5.internal.alerts.AlertManagerImpl.error(AlertManagerImpl.java:62)
> at $AlertManager_12f6054338afd088.error(Unknown Source)
> at org.apache.tapestry5.internal.services.ClientDataEncoderImpl.<init>(ClientDataEncoderImpl.java:59)
> at org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:48)
> ... 81 more
> ... Removed 34 stack frames
>
>
> multiple_changes
> Test class: org.apache.tapestry5.internal.services.ClientPersistentFieldStorageImplTest
> java.lang.RuntimeException: Exception constructing service 'ClientDataEncoder': Error invoking constructor public org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager) throws java.io.UnsupportedEncodingException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
> at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:75)
> at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.createObject(JustInTimeObjectCreator.java:54)
> at $ClientDataEncoder_12f6054338afd086.delegate(Unknown Source)
> at $ClientDataEncoder_12f6054338afd086.createSink(Unknown Source)
> at org.apache.tapestry5.internal.services.ClientPersistentFieldStorageImpl.refreshClientData(ClientPersistentFieldStorageImpl.java:267)
> at org.apache.tapestry5.internal.services.ClientPersistentFieldStorageImpl.updateLink(ClientPersistentFieldStorageImpl.java:137)
> at org.apache.tapestry5.internal.services.ClientPersistentFieldStorageImplTest.multiple_changes(ClientPersistentFieldStorageImplTest.java:159)
> at org.gradle.api.internal.tasks.testing.testng.TestNGTestClassProcessor.stop(TestNGTestClassProcessor.java:103)
> at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:58)
> at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at $Proxy2.stop(Unknown Source)
> at org.gradle.api.internal.tasks.testing.worker.TestWorker.stop(TestWorker.java:110)
> at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at org.gradle.messaging.remote.internal.TypeCastDispatch.dispatch(TypeCastDispatch.java:30)
> at org.gradle.messaging.remote.internal.WorkerProtocol.handleIncoming(WorkerProtocol.java:53)
> at org.gradle.messaging.remote.internal.WorkerProtocol.handleIncoming(WorkerProtocol.java:31)
> at org.gradle.messaging.remote.internal.ProtocolStack$ProtocolStage.handleIncoming(ProtocolStack.java:167)
> at org.gradle.messaging.remote.internal.ProtocolStack$BottomStage.handleIncoming(ProtocolStack.java:277)
> at org.gradle.messaging.remote.internal.ProtocolStack$BottomConnection$1.run(ProtocolStack.java:299)
> at org.gradle.messaging.remote.internal.ProtocolStack$ExecuteRunnable.dispatch(ProtocolStack.java:120)
> at org.gradle.messaging.remote.internal.ProtocolStack$ExecuteRunnable.dispatch(ProtocolStack.java:116)
> at org.gradle.messaging.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:132)
> at org.gradle.messaging.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:33)
> at org.gradle.messaging.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:72)
> at org.gradle.messaging.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: org.apache.tapestry5.ioc.internal.OperationException: Error invoking constructor public org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager) throws java.io.UnsupportedEncodingException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
> at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.logAndRethrow(OperationTrackerImpl.java:121)
> at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:88)
> at org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
> at org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
> at org.apache.tapestry5.ioc.internal.util.ConstructionPlan.createObject(ConstructionPlan.java:60)
> at org.apache.tapestry5.ioc.internal.ConstructorServiceCreator.createObject(ConstructorServiceCreator.java:61)
> at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45)
> at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
> at org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
> at org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
> at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator.createObject(OperationTrackingObjectCreator.java:49)
> at org.apache.tapestry5.ioc.internal.SingletonServiceLifecycle.createService(SingletonServiceLifecycle.java:29)
> at org.apache.tapestry5.ioc.internal.LifecycleWrappedServiceCreator.createObject(LifecycleWrappedServiceCreator.java:46)
> at org.apache.tapestry5.ioc.internal.AdvisorStackBuilder.createObject(AdvisorStackBuilder.java:63)
> at org.apache.tapestry5.ioc.internal.InterceptorStackBuilder.createObject(InterceptorStackBuilder.java:54)
> at org.apache.tapestry5.ioc.internal.RecursiveServiceCreationCheckWrapper.createObject(RecursiveServiceCreationCheckWrapper.java:60)
> at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45)
> at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
> at org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
> at org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
> at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator.createObject(OperationTrackingObjectCreator.java:49)
> at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:66)
> ... 61 more
> Caused by: java.lang.RuntimeException: Error invoking constructor public org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager) throws java.io.UnsupportedEncodingException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
> at org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:57)
> at org.apache.tapestry5.ioc.internal.util.LoggingInvokableWrapper.invoke(LoggingInvokableWrapper.java:42)
> at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
> ... 81 more
> Caused by: java.lang.NullPointerException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
> at $Request_12f6054338afd08b.readProperty(Unknown Source)
> at $Request_12f6054338afd08b.isXHR(Unknown Source)
> at $Request_12f6054338afd04a.isXHR(Unknown Source)
> at org.apache.tapestry5.internal.alerts.AlertManagerImpl.alert(AlertManagerImpl.java:69)
> at org.apache.tapestry5.internal.alerts.AlertManagerImpl.error(AlertManagerImpl.java:62)
> at $AlertManager_12f6054338afd088.error(Unknown Source)
> at org.apache.tapestry5.internal.services.ClientDataEncoderImpl.<init>(ClientDataEncoderImpl.java:59)
> at org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:48)
> ... 83 more
> ... Removed 34 stack frames
>
>
> regards
> Taha
>
>
> On 17-Apr-2013, at 11:43 PM, Kalle Korhonen <ka...@gmail.com> wrote:
>
>> On Wed, Apr 17, 2013 at 12:49 AM, Massimo Lusetti <ml...@gmail.com>wrote:
>>
>>> On Mon, Apr 15, 2013 at 3:30 PM, Kalle Korhonen
>>> <ka...@gmail.com>wrote:
>>>>
>>> Thanks, going to spin it asap, maybe the weekend.
>>>
>>
>> Thanks Massimo, appreciated!
>>
>> Kalle
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5.3.7 release anyone?
Posted by Taha Hafeez Siddiqi <ta...@gmail.com>.
Hi Kalle
My tests keep failing in the 5.3 branch. Are you seeing any such thing. After cloning I am just running
./gradlew clean test
I am running the tests on an OS 10.8
Darwin iMac.local 12.0.0 Darwin Kernel Version 12.0.0: Sun Jun 24 23:00:16 PDT 2012; root:xnu-2050.7.9~1/RELEASE_X86_64 x86_64
Java version is : sun/oracle java 1.6.0_37
9 tests are failing in tapestry-core. Here are stack trace for two of them.
checks_for_eof
Test class: org.apache.tapestry5.internal.services.ClientDataEncoderTest
java.lang.RuntimeException: Exception constructing service 'ClientDataEncoder': Error invoking constructor public org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager) throws java.io.UnsupportedEncodingException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:75)
at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.createObject(JustInTimeObjectCreator.java:54)
at $ClientDataEncoder_12f6054338afd086.delegate(Unknown Source)
at $ClientDataEncoder_12f6054338afd086.createSink(Unknown Source)
at org.apache.tapestry5.internal.services.ClientDataEncoderTest.checks_for_eof(ClientDataEncoderTest.java:68)
at org.gradle.api.internal.tasks.testing.testng.TestNGTestClassProcessor.stop(TestNGTestClassProcessor.java:103)
at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:58)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at $Proxy2.stop(Unknown Source)
at org.gradle.api.internal.tasks.testing.worker.TestWorker.stop(TestWorker.java:110)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at org.gradle.messaging.remote.internal.TypeCastDispatch.dispatch(TypeCastDispatch.java:30)
at org.gradle.messaging.remote.internal.WorkerProtocol.handleIncoming(WorkerProtocol.java:53)
at org.gradle.messaging.remote.internal.WorkerProtocol.handleIncoming(WorkerProtocol.java:31)
at org.gradle.messaging.remote.internal.ProtocolStack$ProtocolStage.handleIncoming(ProtocolStack.java:167)
at org.gradle.messaging.remote.internal.ProtocolStack$BottomStage.handleIncoming(ProtocolStack.java:277)
at org.gradle.messaging.remote.internal.ProtocolStack$BottomConnection$1.run(ProtocolStack.java:299)
at org.gradle.messaging.remote.internal.ProtocolStack$ExecuteRunnable.dispatch(ProtocolStack.java:120)
at org.gradle.messaging.remote.internal.ProtocolStack$ExecuteRunnable.dispatch(ProtocolStack.java:116)
at org.gradle.messaging.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:132)
at org.gradle.messaging.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:33)
at org.gradle.messaging.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:72)
at org.gradle.messaging.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Caused by: org.apache.tapestry5.ioc.internal.OperationException: Error invoking constructor public org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager) throws java.io.UnsupportedEncodingException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.logAndRethrow(OperationTrackerImpl.java:121)
at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:88)
at org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
at org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
at org.apache.tapestry5.ioc.internal.util.ConstructionPlan.createObject(ConstructionPlan.java:60)
at org.apache.tapestry5.ioc.internal.ConstructorServiceCreator.createObject(ConstructorServiceCreator.java:61)
at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45)
at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
at org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
at org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator.createObject(OperationTrackingObjectCreator.java:49)
at org.apache.tapestry5.ioc.internal.SingletonServiceLifecycle.createService(SingletonServiceLifecycle.java:29)
at org.apache.tapestry5.ioc.internal.LifecycleWrappedServiceCreator.createObject(LifecycleWrappedServiceCreator.java:46)
at org.apache.tapestry5.ioc.internal.AdvisorStackBuilder.createObject(AdvisorStackBuilder.java:63)
at org.apache.tapestry5.ioc.internal.InterceptorStackBuilder.createObject(InterceptorStackBuilder.java:54)
at org.apache.tapestry5.ioc.internal.RecursiveServiceCreationCheckWrapper.createObject(RecursiveServiceCreationCheckWrapper.java:60)
at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45)
at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
at org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
at org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator.createObject(OperationTrackingObjectCreator.java:49)
at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:66)
... 59 more
Caused by: java.lang.RuntimeException: Error invoking constructor public org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager) throws java.io.UnsupportedEncodingException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
at org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:57)
at org.apache.tapestry5.ioc.internal.util.LoggingInvokableWrapper.invoke(LoggingInvokableWrapper.java:42)
at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
... 79 more
Caused by: java.lang.NullPointerException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
at $Request_12f6054338afd08b.readProperty(Unknown Source)
at $Request_12f6054338afd08b.isXHR(Unknown Source)
at $Request_12f6054338afd04a.isXHR(Unknown Source)
at org.apache.tapestry5.internal.alerts.AlertManagerImpl.alert(AlertManagerImpl.java:69)
at org.apache.tapestry5.internal.alerts.AlertManagerImpl.error(AlertManagerImpl.java:62)
at $AlertManager_12f6054338afd088.error(Unknown Source)
at org.apache.tapestry5.internal.services.ClientDataEncoderImpl.<init>(ClientDataEncoderImpl.java:59)
at org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:48)
... 81 more
... Removed 34 stack frames
multiple_changes
Test class: org.apache.tapestry5.internal.services.ClientPersistentFieldStorageImplTest
java.lang.RuntimeException: Exception constructing service 'ClientDataEncoder': Error invoking constructor public org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager) throws java.io.UnsupportedEncodingException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:75)
at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.createObject(JustInTimeObjectCreator.java:54)
at $ClientDataEncoder_12f6054338afd086.delegate(Unknown Source)
at $ClientDataEncoder_12f6054338afd086.createSink(Unknown Source)
at org.apache.tapestry5.internal.services.ClientPersistentFieldStorageImpl.refreshClientData(ClientPersistentFieldStorageImpl.java:267)
at org.apache.tapestry5.internal.services.ClientPersistentFieldStorageImpl.updateLink(ClientPersistentFieldStorageImpl.java:137)
at org.apache.tapestry5.internal.services.ClientPersistentFieldStorageImplTest.multiple_changes(ClientPersistentFieldStorageImplTest.java:159)
at org.gradle.api.internal.tasks.testing.testng.TestNGTestClassProcessor.stop(TestNGTestClassProcessor.java:103)
at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:58)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at $Proxy2.stop(Unknown Source)
at org.gradle.api.internal.tasks.testing.worker.TestWorker.stop(TestWorker.java:110)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at org.gradle.messaging.remote.internal.TypeCastDispatch.dispatch(TypeCastDispatch.java:30)
at org.gradle.messaging.remote.internal.WorkerProtocol.handleIncoming(WorkerProtocol.java:53)
at org.gradle.messaging.remote.internal.WorkerProtocol.handleIncoming(WorkerProtocol.java:31)
at org.gradle.messaging.remote.internal.ProtocolStack$ProtocolStage.handleIncoming(ProtocolStack.java:167)
at org.gradle.messaging.remote.internal.ProtocolStack$BottomStage.handleIncoming(ProtocolStack.java:277)
at org.gradle.messaging.remote.internal.ProtocolStack$BottomConnection$1.run(ProtocolStack.java:299)
at org.gradle.messaging.remote.internal.ProtocolStack$ExecuteRunnable.dispatch(ProtocolStack.java:120)
at org.gradle.messaging.remote.internal.ProtocolStack$ExecuteRunnable.dispatch(ProtocolStack.java:116)
at org.gradle.messaging.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:132)
at org.gradle.messaging.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:33)
at org.gradle.messaging.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:72)
at org.gradle.messaging.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Caused by: org.apache.tapestry5.ioc.internal.OperationException: Error invoking constructor public org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager) throws java.io.UnsupportedEncodingException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.logAndRethrow(OperationTrackerImpl.java:121)
at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:88)
at org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
at org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
at org.apache.tapestry5.ioc.internal.util.ConstructionPlan.createObject(ConstructionPlan.java:60)
at org.apache.tapestry5.ioc.internal.ConstructorServiceCreator.createObject(ConstructorServiceCreator.java:61)
at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45)
at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
at org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
at org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator.createObject(OperationTrackingObjectCreator.java:49)
at org.apache.tapestry5.ioc.internal.SingletonServiceLifecycle.createService(SingletonServiceLifecycle.java:29)
at org.apache.tapestry5.ioc.internal.LifecycleWrappedServiceCreator.createObject(LifecycleWrappedServiceCreator.java:46)
at org.apache.tapestry5.ioc.internal.AdvisorStackBuilder.createObject(AdvisorStackBuilder.java:63)
at org.apache.tapestry5.ioc.internal.InterceptorStackBuilder.createObject(InterceptorStackBuilder.java:54)
at org.apache.tapestry5.ioc.internal.RecursiveServiceCreationCheckWrapper.createObject(RecursiveServiceCreationCheckWrapper.java:60)
at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45)
at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
at org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.invoke(PerThreadOperationTracker.java:87)
at org.apache.tapestry5.ioc.internal.RegistryImpl.invoke(RegistryImpl.java:1124)
at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator.createObject(OperationTrackingObjectCreator.java:49)
at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:66)
... 61 more
Caused by: java.lang.RuntimeException: Error invoking constructor public org.apache.tapestry5.internal.services.ClientDataEncoderImpl(org.apache.tapestry5.services.URLEncoder,java.lang.String,org.slf4j.Logger,java.lang.String,org.apache.tapestry5.alerts.AlertManager) throws java.io.UnsupportedEncodingException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
at org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:57)
at org.apache.tapestry5.ioc.internal.util.LoggingInvokableWrapper.invoke(LoggingInvokableWrapper.java:42)
at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:74)
... 81 more
Caused by: java.lang.NullPointerException: Unable to delegate method invocation to property 'request' of <Proxy for RequestGlobals(org.apache.tapestry5.services.RequestGlobals)>, because the property is null.
at $Request_12f6054338afd08b.readProperty(Unknown Source)
at $Request_12f6054338afd08b.isXHR(Unknown Source)
at $Request_12f6054338afd04a.isXHR(Unknown Source)
at org.apache.tapestry5.internal.alerts.AlertManagerImpl.alert(AlertManagerImpl.java:69)
at org.apache.tapestry5.internal.alerts.AlertManagerImpl.error(AlertManagerImpl.java:62)
at $AlertManager_12f6054338afd088.error(Unknown Source)
at org.apache.tapestry5.internal.services.ClientDataEncoderImpl.<init>(ClientDataEncoderImpl.java:59)
at org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:48)
... 83 more
... Removed 34 stack frames
regards
Taha
On 17-Apr-2013, at 11:43 PM, Kalle Korhonen <ka...@gmail.com> wrote:
> On Wed, Apr 17, 2013 at 12:49 AM, Massimo Lusetti <ml...@gmail.com>wrote:
>
>> On Mon, Apr 15, 2013 at 3:30 PM, Kalle Korhonen
>> <ka...@gmail.com>wrote:
>>>
>> Thanks, going to spin it asap, maybe the weekend.
>>
>
> Thanks Massimo, appreciated!
>
> Kalle
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5.3.7 release anyone?
Posted by Kalle Korhonen <ka...@gmail.com>.
On Wed, Apr 17, 2013 at 12:49 AM, Massimo Lusetti <ml...@gmail.com>wrote:
> On Mon, Apr 15, 2013 at 3:30 PM, Kalle Korhonen
> <ka...@gmail.com>wrote:
> >
> Thanks, going to spin it asap, maybe the weekend.
>
Thanks Massimo, appreciated!
Kalle
Re: T5.3.7 release anyone?
Posted by Massimo Lusetti <ml...@gmail.com>.
On Mon, Apr 15, 2013 at 3:30 PM, Kalle Korhonen
<ka...@gmail.com>wrote:
Spent the better part of my Saturday to get the test suite going again with
> the latest FF on the 5.3 branch. Resolving the actual issues was easy and I
> don't have anything else to add to 5.3.7 at this point. There are a few
> test failures but I don't think I added any. I'll be testing 5.3.7 locally
> against a live application today, and then it's all yours Massimo.
>
> Kalle
>
>
Thanks, going to spin it asap, maybe the weekend.
--
Massimo
Re: T5.3.7 release anyone?
Posted by Taha Hafeez Siddiqi <ta...@gmail.com>.
Sorry Ivan
I have already assigned it to myself but couldn't get much time. Will do it today or tomorrow (hopefully)
regards
Taha
On 17-Apr-2013, at 3:37 PM, Ivan Khalopik <ik...@gmail.com> wrote:
> What about https://issues.apache.org/jira/browse/TAP5-2100 ?
>
>
> On Wed, Apr 17, 2013 at 12:54 PM, Dmitry Gusev <dm...@gmail.com>wrote:
>
>> It was working ok, but I still updated the patch and moved servlet
>> container runner instance reference from private field to ITestContext
>> attribute. Should be fine now.
>>
>> On Wed, Apr 17, 2013 at 12:05 PM, Dmitry Gusev <dmitry.gusev@gmail.com
>>> wrote:
>>
>>> Massimo,
>>>
>>> you made me think it may not work as expected with multiple threads.
>>> Not sure if its possible to launch multiple containers simultaneously
>>> though, but if its possible this will not work as expected.
>>> I will check this.
>>>
>>>
>>> On Wed, Apr 17, 2013 at 12:00 PM, Dmitry Gusev <dmitry.gusev@gmail.com
>>> wrote:
>>>
>>>> The behavior wasn't changed, its just in previous versions shutdown was
>>>> made from java.lang.Runnable wrapper which is now direct call to
>>>> ServletContainerRunner.stop()
>>>>
>>>> I've added private field that holds reference to ServletContainerRunner
>> instance
>>>> so that I can get ServletContext from it, and I use this field's values
>> in
>>>> shutdown logic, so its basically the same. I could leave it as before
>> but
>>>> in this case we would hold two different references in different places
>> to
>>>> the same ServletContainerRunner object.
>>>>
>>>>
>>>> On Wed, Apr 17, 2013 at 11:55 AM, Massimo Lusetti <mlusetti@gmail.com
>>> wrote:
>>>>
>>>>> On Wed, Apr 17, 2013 at 9:13 AM, Dmitry Gusev <dmitry.gusev@gmail.com
>>>>>> wrote:
>>>>>
>>>>> I hope its not too late for 5.3.7
>>>>>>
>>>>>> Can somebody review and apply the patch and test from
>>>>>> https://issues.apache.org/jira/browse/TAP5-2107 please?
>>>>>> Its really a tiny, but valuable improvement for me.
>>>>>>
>>>>>>
>>>>> Hi Dimitry,
>>>>> I've just scrolled down at your patch but it seems it slightly change
>>>>> the
>>>>> behavior of SeleniumTestCase during the shutdown phase, am I right?
>>>>>
>>>>> --
>>>>> Massimo
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Dmitry Gusev
>>>>
>>>> AnjLab Team
>>>> http://anjlab.com
>>>>
>>>
>>>
>>>
>>> --
>>> Dmitry Gusev
>>>
>>> AnjLab Team
>>> http://anjlab.com
>>>
>>
>>
>>
>> --
>> Dmitry Gusev
>>
>> AnjLab Team
>> http://anjlab.com
>>
>
>
>
> --
> BR
> Ivan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5.3.7 release anyone?
Posted by Ivan Khalopik <ik...@gmail.com>.
What about https://issues.apache.org/jira/browse/TAP5-2100 ?
On Wed, Apr 17, 2013 at 12:54 PM, Dmitry Gusev <dm...@gmail.com>wrote:
> It was working ok, but I still updated the patch and moved servlet
> container runner instance reference from private field to ITestContext
> attribute. Should be fine now.
>
> On Wed, Apr 17, 2013 at 12:05 PM, Dmitry Gusev <dmitry.gusev@gmail.com
> >wrote:
>
> > Massimo,
> >
> > you made me think it may not work as expected with multiple threads.
> > Not sure if its possible to launch multiple containers simultaneously
> > though, but if its possible this will not work as expected.
> > I will check this.
> >
> >
> > On Wed, Apr 17, 2013 at 12:00 PM, Dmitry Gusev <dmitry.gusev@gmail.com
> >wrote:
> >
> >> The behavior wasn't changed, its just in previous versions shutdown was
> >> made from java.lang.Runnable wrapper which is now direct call to
> >> ServletContainerRunner.stop()
> >>
> >> I've added private field that holds reference to ServletContainerRunner
> instance
> >> so that I can get ServletContext from it, and I use this field's values
> in
> >> shutdown logic, so its basically the same. I could leave it as before
> but
> >> in this case we would hold two different references in different places
> to
> >> the same ServletContainerRunner object.
> >>
> >>
> >> On Wed, Apr 17, 2013 at 11:55 AM, Massimo Lusetti <mlusetti@gmail.com
> >wrote:
> >>
> >>> On Wed, Apr 17, 2013 at 9:13 AM, Dmitry Gusev <dmitry.gusev@gmail.com
> >>> >wrote:
> >>>
> >>> I hope its not too late for 5.3.7
> >>> >
> >>> > Can somebody review and apply the patch and test from
> >>> > https://issues.apache.org/jira/browse/TAP5-2107 please?
> >>> > Its really a tiny, but valuable improvement for me.
> >>> >
> >>> >
> >>> Hi Dimitry,
> >>> I've just scrolled down at your patch but it seems it slightly change
> >>> the
> >>> behavior of SeleniumTestCase during the shutdown phase, am I right?
> >>>
> >>> --
> >>> Massimo
> >>>
> >>
> >>
> >>
> >> --
> >> Dmitry Gusev
> >>
> >> AnjLab Team
> >> http://anjlab.com
> >>
> >
> >
> >
> > --
> > Dmitry Gusev
> >
> > AnjLab Team
> > http://anjlab.com
> >
>
>
>
> --
> Dmitry Gusev
>
> AnjLab Team
> http://anjlab.com
>
--
BR
Ivan
Re: T5.3.7 release anyone?
Posted by Dmitry Gusev <dm...@gmail.com>.
It was working ok, but I still updated the patch and moved servlet
container runner instance reference from private field to ITestContext
attribute. Should be fine now.
On Wed, Apr 17, 2013 at 12:05 PM, Dmitry Gusev <dm...@gmail.com>wrote:
> Massimo,
>
> you made me think it may not work as expected with multiple threads.
> Not sure if its possible to launch multiple containers simultaneously
> though, but if its possible this will not work as expected.
> I will check this.
>
>
> On Wed, Apr 17, 2013 at 12:00 PM, Dmitry Gusev <dm...@gmail.com>wrote:
>
>> The behavior wasn't changed, its just in previous versions shutdown was
>> made from java.lang.Runnable wrapper which is now direct call to
>> ServletContainerRunner.stop()
>>
>> I've added private field that holds reference to ServletContainerRunner instance
>> so that I can get ServletContext from it, and I use this field's values in
>> shutdown logic, so its basically the same. I could leave it as before but
>> in this case we would hold two different references in different places to
>> the same ServletContainerRunner object.
>>
>>
>> On Wed, Apr 17, 2013 at 11:55 AM, Massimo Lusetti <ml...@gmail.com>wrote:
>>
>>> On Wed, Apr 17, 2013 at 9:13 AM, Dmitry Gusev <dmitry.gusev@gmail.com
>>> >wrote:
>>>
>>> I hope its not too late for 5.3.7
>>> >
>>> > Can somebody review and apply the patch and test from
>>> > https://issues.apache.org/jira/browse/TAP5-2107 please?
>>> > Its really a tiny, but valuable improvement for me.
>>> >
>>> >
>>> Hi Dimitry,
>>> I've just scrolled down at your patch but it seems it slightly change
>>> the
>>> behavior of SeleniumTestCase during the shutdown phase, am I right?
>>>
>>> --
>>> Massimo
>>>
>>
>>
>>
>> --
>> Dmitry Gusev
>>
>> AnjLab Team
>> http://anjlab.com
>>
>
>
>
> --
> Dmitry Gusev
>
> AnjLab Team
> http://anjlab.com
>
--
Dmitry Gusev
AnjLab Team
http://anjlab.com
Re: T5.3.7 release anyone?
Posted by Dmitry Gusev <dm...@gmail.com>.
Massimo,
you made me think it may not work as expected with multiple threads.
Not sure if its possible to launch multiple containers simultaneously
though, but if its possible this will not work as expected.
I will check this.
On Wed, Apr 17, 2013 at 12:00 PM, Dmitry Gusev <dm...@gmail.com>wrote:
> The behavior wasn't changed, its just in previous versions shutdown was
> made from java.lang.Runnable wrapper which is now direct call to
> ServletContainerRunner.stop()
>
> I've added private field that holds reference to ServletContainerRunner instance
> so that I can get ServletContext from it, and I use this field's values in
> shutdown logic, so its basically the same. I could leave it as before but
> in this case we would hold two different references in different places to
> the same ServletContainerRunner object.
>
>
> On Wed, Apr 17, 2013 at 11:55 AM, Massimo Lusetti <ml...@gmail.com>wrote:
>
>> On Wed, Apr 17, 2013 at 9:13 AM, Dmitry Gusev <dmitry.gusev@gmail.com
>> >wrote:
>>
>> I hope its not too late for 5.3.7
>> >
>> > Can somebody review and apply the patch and test from
>> > https://issues.apache.org/jira/browse/TAP5-2107 please?
>> > Its really a tiny, but valuable improvement for me.
>> >
>> >
>> Hi Dimitry,
>> I've just scrolled down at your patch but it seems it slightly change
>> the
>> behavior of SeleniumTestCase during the shutdown phase, am I right?
>>
>> --
>> Massimo
>>
>
>
>
> --
> Dmitry Gusev
>
> AnjLab Team
> http://anjlab.com
>
--
Dmitry Gusev
AnjLab Team
http://anjlab.com
Re: T5.3.7 release anyone?
Posted by Dmitry Gusev <dm...@gmail.com>.
The behavior wasn't changed, its just in previous versions shutdown was
made from java.lang.Runnable wrapper which is now direct call to
ServletContainerRunner.stop()
I've added private field that holds reference to
ServletContainerRunner instance
so that I can get ServletContext from it, and I use this field's values in
shutdown logic, so its basically the same. I could leave it as before but
in this case we would hold two different references in different places to
the same ServletContainerRunner object.
On Wed, Apr 17, 2013 at 11:55 AM, Massimo Lusetti <ml...@gmail.com>wrote:
> On Wed, Apr 17, 2013 at 9:13 AM, Dmitry Gusev <dmitry.gusev@gmail.com
> >wrote:
>
> I hope its not too late for 5.3.7
> >
> > Can somebody review and apply the patch and test from
> > https://issues.apache.org/jira/browse/TAP5-2107 please?
> > Its really a tiny, but valuable improvement for me.
> >
> >
> Hi Dimitry,
> I've just scrolled down at your patch but it seems it slightly change the
> behavior of SeleniumTestCase during the shutdown phase, am I right?
>
> --
> Massimo
>
--
Dmitry Gusev
AnjLab Team
http://anjlab.com
Re: T5.3.7 release anyone?
Posted by Massimo Lusetti <ml...@gmail.com>.
On Wed, Apr 17, 2013 at 9:13 AM, Dmitry Gusev <dm...@gmail.com>wrote:
I hope its not too late for 5.3.7
>
> Can somebody review and apply the patch and test from
> https://issues.apache.org/jira/browse/TAP5-2107 please?
> Its really a tiny, but valuable improvement for me.
>
>
Hi Dimitry,
I've just scrolled down at your patch but it seems it slightly change the
behavior of SeleniumTestCase during the shutdown phase, am I right?
--
Massimo
Re: T5.3.7 release anyone?
Posted by Dmitry Gusev <dm...@gmail.com>.
I hope its not too late for 5.3.7
Can somebody review and apply the patch and test from
https://issues.apache.org/jira/browse/TAP5-2107 please?
Its really a tiny, but valuable improvement for me.
On Mon, Apr 15, 2013 at 5:30 PM, Kalle Korhonen
<ka...@gmail.com>wrote:
> Spent the better part of my Saturday to get the test suite going again with
> the latest FF on the 5.3 branch. Resolving the actual issues was easy and I
> don't have anything else to add to 5.3.7 at this point. There are a few
> test failures but I don't think I added any. I'll be testing 5.3.7 locally
> against a live application today, and then it's all yours Massimo.
>
> Kalle
>
>
> On Tue, Apr 9, 2013 at 8:37 AM, Kalle Korhonen
> <ka...@gmail.com>wrote:
>
> > Massimo thanks! Next week please - I'm putting a few easy ones in still,
> > actually have some real time carved out for that this week.
> >
> > Kalle
> >
> >
> >
> > On Tue, Apr 9, 2013 at 2:13 AM, Massimo Lusetti <mlusetti@gmail.com
> >wrote:
> >
> >> I'm going to give a whirl to the release process in the next days (maybe
> >> early next week) ...
> >>
> >>
> >> On Tue, Apr 2, 2013 at 8:43 PM, Luca Menegus <luca.menegus@dbmsrl.com
> >> >wrote:
> >>
> >> > ... TAP5-2101 got it's first vote on jira ;)
> >> >
> >> > (I'll stop spamming dev right now)
> >> >
> >> > ----- Original Message -----
> >> > > From: "Luca Menegus" <lu...@dbmsrl.com>
> >> > > To: "Tapestry development" <de...@tapestry.apache.org>
> >> > > Sent: Tuesday, April 2, 2013 8:14:20 PM
> >> > > Subject: Re: T5.3.7 release anyone?
> >> > >
> >> > >
> >> > > Done TAP5-2101,
> >> > > thank very much to anybody taking time to review it,
> >> > > regards,
> >> > > luca
> >> > >
> >> > >
> >> > > [1] https://issues.apache.org/jira/browse/TAP5-2101
> >> > >
> >> > >
> >> > >
> >> > > ----- Original Message -----
> >> > > > From: "Kalle Korhonen" <ka...@gmail.com>
> >> > > > To: "Tapestry development" <de...@tapestry.apache.org>
> >> > > > Sent: Tuesday, April 2, 2013 6:28:50 PM
> >> > > > Subject: Re: T5.3.7 release anyone?
> >> > > >
> >> > > > Open an issue to get that in and refer to it here. I'm pretty sure
> >> that
> >> > > > there's no hope to get an issue fixed for T5.3.7 at this point
> >> unless a
> >> > > > committer is already working on it or there's a clean patch with a
> >> > test on
> >> > > > it.
> >> > > >
> >> > > > Kalle
> >> > > >
> >> > > >
> >> > > > On Tue, Apr 2, 2013 at 9:11 AM, Luca Menegus
> >> > > > <lu...@dbmsrl.com>wrote:
> >> > > >
> >> > > > > Hi all,
> >> > > > > do you think somebody has the time to look our problem with
> >> > > > > tapestry-beanvalidation?
> >> > > > >
> >> > > > >
> >> > > > >
> >> >
> >>
> http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/BeanEditor-should-always-provide-a-new-BeanValidationContext-JSR-303-td5713975.html#a5714049
> >> > > > >
> >> > > > > At the moment even:
> >> > > > > <t:form validate="this">
> >> > > > > <t:BeanEditor object="beanA" />
> >> > > > > <t:BeanEditor object=" beanB " />
> >> > > > > <t:form/>
> >> > > > >
> >> > > > > Is not (bean)validating properly....
> >> > > > >
> >> > > > > In the original message i provided a patch (with test case). If
> >> > anybody
> >> > > > > is
> >> > > > > interest in fixing this issue I'm ready to create a ticket,
> >> re-post
> >> > the
> >> > > > > patch do whatever is needed to get it upstream
> >> > > > >
> >> > > > > Thanks,
> >> > > > > Luca
> >> > > > > ----- Original Message -----
> >> > > > > > From: "Kalle Korhonen" <ka...@gmail.com>
> >> > > > > > To: "Tapestry development" <de...@tapestry.apache.org>
> >> > > > > > Sent: Sunday, March 31, 2013 8:17:51 AM
> >> > > > > > Subject: T5.3.7 release anyone?
> >> > > > > >
> >> > > > > > Is anybody in need of T5.3.7? I'm not quite ready myself just
> >> yet
> >> > but
> >> > > > > there
> >> > > > > > are a few relevant fixes for us and I could put a few more in.
> >> Is
> >> > > > > > anybody
> >> > > > > > else looking for a 5.3.7 release? Massimo, I think you've done
> >> the
> >> > last
> >> > > > > > 5.3.x releases. How's your experience been regarding the
> release
> >> > > > > > process?
> >> > > > > > Is everything documented, any gotchas, pain points etc? Or
> would
> >> > you
> >> > > > > > perhaps be willing to cut one more release yourself?
> >> > > > > >
> >> > > > > > Kalle
> >> > > > > >
> >> > > > >
> >> > > > >
> >> ---------------------------------------------------------------------
> >> > > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >> > > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> > >
> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >> > > For additional commands, e-mail: dev-help@tapestry.apache.org
> >> > >
> >> > >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >> >
> >> >
> >>
> >>
> >> --
> >> Massimo
> >> http://meridio.blogspot.com
> >>
> >
> >
>
--
Dmitry Gusev
AnjLab Team
http://anjlab.com
Re: T5.3.7 release anyone?
Posted by Kalle Korhonen <ka...@gmail.com>.
Spent the better part of my Saturday to get the test suite going again with
the latest FF on the 5.3 branch. Resolving the actual issues was easy and I
don't have anything else to add to 5.3.7 at this point. There are a few
test failures but I don't think I added any. I'll be testing 5.3.7 locally
against a live application today, and then it's all yours Massimo.
Kalle
On Tue, Apr 9, 2013 at 8:37 AM, Kalle Korhonen
<ka...@gmail.com>wrote:
> Massimo thanks! Next week please - I'm putting a few easy ones in still,
> actually have some real time carved out for that this week.
>
> Kalle
>
>
>
> On Tue, Apr 9, 2013 at 2:13 AM, Massimo Lusetti <ml...@gmail.com>wrote:
>
>> I'm going to give a whirl to the release process in the next days (maybe
>> early next week) ...
>>
>>
>> On Tue, Apr 2, 2013 at 8:43 PM, Luca Menegus <luca.menegus@dbmsrl.com
>> >wrote:
>>
>> > ... TAP5-2101 got it's first vote on jira ;)
>> >
>> > (I'll stop spamming dev right now)
>> >
>> > ----- Original Message -----
>> > > From: "Luca Menegus" <lu...@dbmsrl.com>
>> > > To: "Tapestry development" <de...@tapestry.apache.org>
>> > > Sent: Tuesday, April 2, 2013 8:14:20 PM
>> > > Subject: Re: T5.3.7 release anyone?
>> > >
>> > >
>> > > Done TAP5-2101,
>> > > thank very much to anybody taking time to review it,
>> > > regards,
>> > > luca
>> > >
>> > >
>> > > [1] https://issues.apache.org/jira/browse/TAP5-2101
>> > >
>> > >
>> > >
>> > > ----- Original Message -----
>> > > > From: "Kalle Korhonen" <ka...@gmail.com>
>> > > > To: "Tapestry development" <de...@tapestry.apache.org>
>> > > > Sent: Tuesday, April 2, 2013 6:28:50 PM
>> > > > Subject: Re: T5.3.7 release anyone?
>> > > >
>> > > > Open an issue to get that in and refer to it here. I'm pretty sure
>> that
>> > > > there's no hope to get an issue fixed for T5.3.7 at this point
>> unless a
>> > > > committer is already working on it or there's a clean patch with a
>> > test on
>> > > > it.
>> > > >
>> > > > Kalle
>> > > >
>> > > >
>> > > > On Tue, Apr 2, 2013 at 9:11 AM, Luca Menegus
>> > > > <lu...@dbmsrl.com>wrote:
>> > > >
>> > > > > Hi all,
>> > > > > do you think somebody has the time to look our problem with
>> > > > > tapestry-beanvalidation?
>> > > > >
>> > > > >
>> > > > >
>> >
>> http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/BeanEditor-should-always-provide-a-new-BeanValidationContext-JSR-303-td5713975.html#a5714049
>> > > > >
>> > > > > At the moment even:
>> > > > > <t:form validate="this">
>> > > > > <t:BeanEditor object="beanA" />
>> > > > > <t:BeanEditor object=" beanB " />
>> > > > > <t:form/>
>> > > > >
>> > > > > Is not (bean)validating properly....
>> > > > >
>> > > > > In the original message i provided a patch (with test case). If
>> > anybody
>> > > > > is
>> > > > > interest in fixing this issue I'm ready to create a ticket,
>> re-post
>> > the
>> > > > > patch do whatever is needed to get it upstream
>> > > > >
>> > > > > Thanks,
>> > > > > Luca
>> > > > > ----- Original Message -----
>> > > > > > From: "Kalle Korhonen" <ka...@gmail.com>
>> > > > > > To: "Tapestry development" <de...@tapestry.apache.org>
>> > > > > > Sent: Sunday, March 31, 2013 8:17:51 AM
>> > > > > > Subject: T5.3.7 release anyone?
>> > > > > >
>> > > > > > Is anybody in need of T5.3.7? I'm not quite ready myself just
>> yet
>> > but
>> > > > > there
>> > > > > > are a few relevant fixes for us and I could put a few more in.
>> Is
>> > > > > > anybody
>> > > > > > else looking for a 5.3.7 release? Massimo, I think you've done
>> the
>> > last
>> > > > > > 5.3.x releases. How's your experience been regarding the release
>> > > > > > process?
>> > > > > > Is everything documented, any gotchas, pain points etc? Or would
>> > you
>> > > > > > perhaps be willing to cut one more release yourself?
>> > > > > >
>> > > > > > Kalle
>> > > > > >
>> > > > >
>> > > > >
>> ---------------------------------------------------------------------
>> > > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> > > > > For additional commands, e-mail: dev-help@tapestry.apache.org
>> > > > >
>> > > > >
>> > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> > > For additional commands, e-mail: dev-help@tapestry.apache.org
>> > >
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> > For additional commands, e-mail: dev-help@tapestry.apache.org
>> >
>> >
>>
>>
>> --
>> Massimo
>> http://meridio.blogspot.com
>>
>
>
Re: T5.3.7 release anyone?
Posted by Kalle Korhonen <ka...@gmail.com>.
Massimo thanks! Next week please - I'm putting a few easy ones in still,
actually have some real time carved out for that this week.
Kalle
On Tue, Apr 9, 2013 at 2:13 AM, Massimo Lusetti <ml...@gmail.com> wrote:
> I'm going to give a whirl to the release process in the next days (maybe
> early next week) ...
>
>
> On Tue, Apr 2, 2013 at 8:43 PM, Luca Menegus <luca.menegus@dbmsrl.com
> >wrote:
>
> > ... TAP5-2101 got it's first vote on jira ;)
> >
> > (I'll stop spamming dev right now)
> >
> > ----- Original Message -----
> > > From: "Luca Menegus" <lu...@dbmsrl.com>
> > > To: "Tapestry development" <de...@tapestry.apache.org>
> > > Sent: Tuesday, April 2, 2013 8:14:20 PM
> > > Subject: Re: T5.3.7 release anyone?
> > >
> > >
> > > Done TAP5-2101,
> > > thank very much to anybody taking time to review it,
> > > regards,
> > > luca
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/TAP5-2101
> > >
> > >
> > >
> > > ----- Original Message -----
> > > > From: "Kalle Korhonen" <ka...@gmail.com>
> > > > To: "Tapestry development" <de...@tapestry.apache.org>
> > > > Sent: Tuesday, April 2, 2013 6:28:50 PM
> > > > Subject: Re: T5.3.7 release anyone?
> > > >
> > > > Open an issue to get that in and refer to it here. I'm pretty sure
> that
> > > > there's no hope to get an issue fixed for T5.3.7 at this point
> unless a
> > > > committer is already working on it or there's a clean patch with a
> > test on
> > > > it.
> > > >
> > > > Kalle
> > > >
> > > >
> > > > On Tue, Apr 2, 2013 at 9:11 AM, Luca Menegus
> > > > <lu...@dbmsrl.com>wrote:
> > > >
> > > > > Hi all,
> > > > > do you think somebody has the time to look our problem with
> > > > > tapestry-beanvalidation?
> > > > >
> > > > >
> > > > >
> >
> http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/BeanEditor-should-always-provide-a-new-BeanValidationContext-JSR-303-td5713975.html#a5714049
> > > > >
> > > > > At the moment even:
> > > > > <t:form validate="this">
> > > > > <t:BeanEditor object="beanA" />
> > > > > <t:BeanEditor object=" beanB " />
> > > > > <t:form/>
> > > > >
> > > > > Is not (bean)validating properly....
> > > > >
> > > > > In the original message i provided a patch (with test case). If
> > anybody
> > > > > is
> > > > > interest in fixing this issue I'm ready to create a ticket, re-post
> > the
> > > > > patch do whatever is needed to get it upstream
> > > > >
> > > > > Thanks,
> > > > > Luca
> > > > > ----- Original Message -----
> > > > > > From: "Kalle Korhonen" <ka...@gmail.com>
> > > > > > To: "Tapestry development" <de...@tapestry.apache.org>
> > > > > > Sent: Sunday, March 31, 2013 8:17:51 AM
> > > > > > Subject: T5.3.7 release anyone?
> > > > > >
> > > > > > Is anybody in need of T5.3.7? I'm not quite ready myself just yet
> > but
> > > > > there
> > > > > > are a few relevant fixes for us and I could put a few more in. Is
> > > > > > anybody
> > > > > > else looking for a 5.3.7 release? Massimo, I think you've done
> the
> > last
> > > > > > 5.3.x releases. How's your experience been regarding the release
> > > > > > process?
> > > > > > Is everything documented, any gotchas, pain points etc? Or would
> > you
> > > > > > perhaps be willing to cut one more release yourself?
> > > > > >
> > > > > > Kalle
> > > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
> --
> Massimo
> http://meridio.blogspot.com
>
Re: T5.3.7 release anyone?
Posted by Massimo Lusetti <ml...@gmail.com>.
I'm going to give a whirl to the release process in the next days (maybe
early next week) ...
On Tue, Apr 2, 2013 at 8:43 PM, Luca Menegus <lu...@dbmsrl.com>wrote:
> ... TAP5-2101 got it's first vote on jira ;)
>
> (I'll stop spamming dev right now)
>
> ----- Original Message -----
> > From: "Luca Menegus" <lu...@dbmsrl.com>
> > To: "Tapestry development" <de...@tapestry.apache.org>
> > Sent: Tuesday, April 2, 2013 8:14:20 PM
> > Subject: Re: T5.3.7 release anyone?
> >
> >
> > Done TAP5-2101,
> > thank very much to anybody taking time to review it,
> > regards,
> > luca
> >
> >
> > [1] https://issues.apache.org/jira/browse/TAP5-2101
> >
> >
> >
> > ----- Original Message -----
> > > From: "Kalle Korhonen" <ka...@gmail.com>
> > > To: "Tapestry development" <de...@tapestry.apache.org>
> > > Sent: Tuesday, April 2, 2013 6:28:50 PM
> > > Subject: Re: T5.3.7 release anyone?
> > >
> > > Open an issue to get that in and refer to it here. I'm pretty sure that
> > > there's no hope to get an issue fixed for T5.3.7 at this point unless a
> > > committer is already working on it or there's a clean patch with a
> test on
> > > it.
> > >
> > > Kalle
> > >
> > >
> > > On Tue, Apr 2, 2013 at 9:11 AM, Luca Menegus
> > > <lu...@dbmsrl.com>wrote:
> > >
> > > > Hi all,
> > > > do you think somebody has the time to look our problem with
> > > > tapestry-beanvalidation?
> > > >
> > > >
> > > >
> http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/BeanEditor-should-always-provide-a-new-BeanValidationContext-JSR-303-td5713975.html#a5714049
> > > >
> > > > At the moment even:
> > > > <t:form validate="this">
> > > > <t:BeanEditor object="beanA" />
> > > > <t:BeanEditor object=" beanB " />
> > > > <t:form/>
> > > >
> > > > Is not (bean)validating properly....
> > > >
> > > > In the original message i provided a patch (with test case). If
> anybody
> > > > is
> > > > interest in fixing this issue I'm ready to create a ticket, re-post
> the
> > > > patch do whatever is needed to get it upstream
> > > >
> > > > Thanks,
> > > > Luca
> > > > ----- Original Message -----
> > > > > From: "Kalle Korhonen" <ka...@gmail.com>
> > > > > To: "Tapestry development" <de...@tapestry.apache.org>
> > > > > Sent: Sunday, March 31, 2013 8:17:51 AM
> > > > > Subject: T5.3.7 release anyone?
> > > > >
> > > > > Is anybody in need of T5.3.7? I'm not quite ready myself just yet
> but
> > > > there
> > > > > are a few relevant fixes for us and I could put a few more in. Is
> > > > > anybody
> > > > > else looking for a 5.3.7 release? Massimo, I think you've done the
> last
> > > > > 5.3.x releases. How's your experience been regarding the release
> > > > > process?
> > > > > Is everything documented, any gotchas, pain points etc? Or would
> you
> > > > > perhaps be willing to cut one more release yourself?
> > > > >
> > > > > Kalle
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Massimo
http://meridio.blogspot.com
Re: T5.3.7 release anyone?
Posted by Luca Menegus <lu...@dbmsrl.com>.
... TAP5-2101 got it's first vote on jira ;)
(I'll stop spamming dev right now)
----- Original Message -----
> From: "Luca Menegus" <lu...@dbmsrl.com>
> To: "Tapestry development" <de...@tapestry.apache.org>
> Sent: Tuesday, April 2, 2013 8:14:20 PM
> Subject: Re: T5.3.7 release anyone?
>
>
> Done TAP5-2101,
> thank very much to anybody taking time to review it,
> regards,
> luca
>
>
> [1] https://issues.apache.org/jira/browse/TAP5-2101
>
>
>
> ----- Original Message -----
> > From: "Kalle Korhonen" <ka...@gmail.com>
> > To: "Tapestry development" <de...@tapestry.apache.org>
> > Sent: Tuesday, April 2, 2013 6:28:50 PM
> > Subject: Re: T5.3.7 release anyone?
> >
> > Open an issue to get that in and refer to it here. I'm pretty sure that
> > there's no hope to get an issue fixed for T5.3.7 at this point unless a
> > committer is already working on it or there's a clean patch with a test on
> > it.
> >
> > Kalle
> >
> >
> > On Tue, Apr 2, 2013 at 9:11 AM, Luca Menegus
> > <lu...@dbmsrl.com>wrote:
> >
> > > Hi all,
> > > do you think somebody has the time to look our problem with
> > > tapestry-beanvalidation?
> > >
> > >
> > > http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/BeanEditor-should-always-provide-a-new-BeanValidationContext-JSR-303-td5713975.html#a5714049
> > >
> > > At the moment even:
> > > <t:form validate="this">
> > > <t:BeanEditor object="beanA" />
> > > <t:BeanEditor object=" beanB " />
> > > <t:form/>
> > >
> > > Is not (bean)validating properly....
> > >
> > > In the original message i provided a patch (with test case). If anybody
> > > is
> > > interest in fixing this issue I'm ready to create a ticket, re-post the
> > > patch do whatever is needed to get it upstream
> > >
> > > Thanks,
> > > Luca
> > > ----- Original Message -----
> > > > From: "Kalle Korhonen" <ka...@gmail.com>
> > > > To: "Tapestry development" <de...@tapestry.apache.org>
> > > > Sent: Sunday, March 31, 2013 8:17:51 AM
> > > > Subject: T5.3.7 release anyone?
> > > >
> > > > Is anybody in need of T5.3.7? I'm not quite ready myself just yet but
> > > there
> > > > are a few relevant fixes for us and I could put a few more in. Is
> > > > anybody
> > > > else looking for a 5.3.7 release? Massimo, I think you've done the last
> > > > 5.3.x releases. How's your experience been regarding the release
> > > > process?
> > > > Is everything documented, any gotchas, pain points etc? Or would you
> > > > perhaps be willing to cut one more release yourself?
> > > >
> > > > Kalle
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5.3.7 release anyone?
Posted by Luca Menegus <lu...@dbmsrl.com>.
Done TAP5-2101,
thank very much to anybody taking time to review it,
regards,
luca
[1] https://issues.apache.org/jira/browse/TAP5-2101
----- Original Message -----
> From: "Kalle Korhonen" <ka...@gmail.com>
> To: "Tapestry development" <de...@tapestry.apache.org>
> Sent: Tuesday, April 2, 2013 6:28:50 PM
> Subject: Re: T5.3.7 release anyone?
>
> Open an issue to get that in and refer to it here. I'm pretty sure that
> there's no hope to get an issue fixed for T5.3.7 at this point unless a
> committer is already working on it or there's a clean patch with a test on
> it.
>
> Kalle
>
>
> On Tue, Apr 2, 2013 at 9:11 AM, Luca Menegus <lu...@dbmsrl.com>wrote:
>
> > Hi all,
> > do you think somebody has the time to look our problem with
> > tapestry-beanvalidation?
> >
> >
> > http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/BeanEditor-should-always-provide-a-new-BeanValidationContext-JSR-303-td5713975.html#a5714049
> >
> > At the moment even:
> > <t:form validate="this">
> > <t:BeanEditor object="beanA" />
> > <t:BeanEditor object=" beanB " />
> > <t:form/>
> >
> > Is not (bean)validating properly....
> >
> > In the original message i provided a patch (with test case). If anybody is
> > interest in fixing this issue I'm ready to create a ticket, re-post the
> > patch do whatever is needed to get it upstream
> >
> > Thanks,
> > Luca
> > ----- Original Message -----
> > > From: "Kalle Korhonen" <ka...@gmail.com>
> > > To: "Tapestry development" <de...@tapestry.apache.org>
> > > Sent: Sunday, March 31, 2013 8:17:51 AM
> > > Subject: T5.3.7 release anyone?
> > >
> > > Is anybody in need of T5.3.7? I'm not quite ready myself just yet but
> > there
> > > are a few relevant fixes for us and I could put a few more in. Is anybody
> > > else looking for a 5.3.7 release? Massimo, I think you've done the last
> > > 5.3.x releases. How's your experience been regarding the release process?
> > > Is everything documented, any gotchas, pain points etc? Or would you
> > > perhaps be willing to cut one more release yourself?
> > >
> > > Kalle
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5.3.7 release anyone?
Posted by Kalle Korhonen <ka...@gmail.com>.
Open an issue to get that in and refer to it here. I'm pretty sure that
there's no hope to get an issue fixed for T5.3.7 at this point unless a
committer is already working on it or there's a clean patch with a test on
it.
Kalle
On Tue, Apr 2, 2013 at 9:11 AM, Luca Menegus <lu...@dbmsrl.com>wrote:
> Hi all,
> do you think somebody has the time to look our problem with
> tapestry-beanvalidation?
>
>
> http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/BeanEditor-should-always-provide-a-new-BeanValidationContext-JSR-303-td5713975.html#a5714049
>
> At the moment even:
> <t:form validate="this">
> <t:BeanEditor object="beanA" />
> <t:BeanEditor object=" beanB " />
> <t:form/>
>
> Is not (bean)validating properly....
>
> In the original message i provided a patch (with test case). If anybody is
> interest in fixing this issue I'm ready to create a ticket, re-post the
> patch do whatever is needed to get it upstream
>
> Thanks,
> Luca
> ----- Original Message -----
> > From: "Kalle Korhonen" <ka...@gmail.com>
> > To: "Tapestry development" <de...@tapestry.apache.org>
> > Sent: Sunday, March 31, 2013 8:17:51 AM
> > Subject: T5.3.7 release anyone?
> >
> > Is anybody in need of T5.3.7? I'm not quite ready myself just yet but
> there
> > are a few relevant fixes for us and I could put a few more in. Is anybody
> > else looking for a 5.3.7 release? Massimo, I think you've done the last
> > 5.3.x releases. How's your experience been regarding the release process?
> > Is everything documented, any gotchas, pain points etc? Or would you
> > perhaps be willing to cut one more release yourself?
> >
> > Kalle
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: T5.3.7 release anyone?
Posted by Luca Menegus <lu...@dbmsrl.com>.
Hi all,
do you think somebody has the time to look our problem with tapestry-beanvalidation?
http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/BeanEditor-should-always-provide-a-new-BeanValidationContext-JSR-303-td5713975.html#a5714049
At the moment even:
<t:form validate="this">
<t:BeanEditor object="beanA" />
<t:BeanEditor object=" beanB " />
<t:form/>
Is not (bean)validating properly....
In the original message i provided a patch (with test case). If anybody is interest in fixing this issue I'm ready to create a ticket, re-post the patch do whatever is needed to get it upstream
Thanks,
Luca
----- Original Message -----
> From: "Kalle Korhonen" <ka...@gmail.com>
> To: "Tapestry development" <de...@tapestry.apache.org>
> Sent: Sunday, March 31, 2013 8:17:51 AM
> Subject: T5.3.7 release anyone?
>
> Is anybody in need of T5.3.7? I'm not quite ready myself just yet but there
> are a few relevant fixes for us and I could put a few more in. Is anybody
> else looking for a 5.3.7 release? Massimo, I think you've done the last
> 5.3.x releases. How's your experience been regarding the release process?
> Is everything documented, any gotchas, pain points etc? Or would you
> perhaps be willing to cut one more release yourself?
>
> Kalle
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5.3.7 release anyone?
Posted by Dimitris Zenios <di...@gmail.com>.
It could be nice if this bug can be resolved before 5.3.7
https://issues.apache.org/jira/browse/TAP5-2025
Cheers
On Mon, Apr 1, 2013 at 10:27 AM, Massimo Lusetti <ml...@gmail.com> wrote:
> I agree. Some minor fixes are in 5.3 branch and not release (if memory
> serve) so a release would be nice.
>
> We could plan a release asap, Kalle what's left for you? Others?
>
> Cheers
>
>
> On Sun, Mar 31, 2013 at 1:26 PM, Bob Harner <bo...@gmail.com> wrote:
>
> > I do think a 5.3.7 release would be worthwhile. It seems to me that
> > 5.4 needs a bit more shaking out (and documenting) before it is ready
> > for release. Also, it has been almost 6 months since 5.3.6 was
> > released, and until then we were producing a release about every 2
> > months on average.
> >
> > On Sun, Mar 31, 2013 at 2:17 AM, Kalle Korhonen
> > <ka...@gmail.com> wrote:
> > > Is anybody in need of T5.3.7? I'm not quite ready myself just yet but
> > there
> > > are a few relevant fixes for us and I could put a few more in. Is
> anybody
> > > else looking for a 5.3.7 release? Massimo, I think you've done the last
> > > 5.3.x releases. How's your experience been regarding the release
> process?
> > > Is everything documented, any gotchas, pain points etc? Or would you
> > > perhaps be willing to cut one more release yourself?
> > >
> > > Kalle
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
> --
> Massimo
> http://meridio.blogspot.com
>
Re: T5.3.7 release anyone?
Posted by Howard Lewis Ship <hl...@gmail.com>.
+0 I'm not aware of any specific issues that affect my applications but I
have no problem with a 5.3.7 release.
On Tue, Apr 2, 2013 at 7:42 AM, Denis Stepanov <de...@gmail.com>wrote:
> It would be nice if someone would apply the patch from
> https://issues.apache.org/jira/browse/TAP5-2084 and include it in T5.3.7.
>
> Good candidate could be https://issues.apache.org/jira/browse/TAP5-2051reduces memory footprint, it's already applied in 5.4.
>
> Denis
>
> Apr 1, 2013 v 8:12 PM, Lenny Primak <lp...@hope.nyc.ny.us>:
>
> > How about this one?
> >
> > https://issues.apache.org/jira/browse/TAP5-2014
> >
> > On Apr 1, 2013, at 1:38 PM, Kalle Korhonen <ka...@gmail.com>
> wrote:
> >
> >> Thanks Bob, Massimo. At least
> >> https://issues.apache.org/jira/browse/TAP5-2097 and
> >> https://issues.apache.org/jira/browse/TAP5-1890 merge to T5.3 for me,
> and
> >> need to check if there was anything else. I can get them done this week.
> >>
> >> Kalle
> >>
> >>
> >> On Mon, Apr 1, 2013 at 12:27 AM, Massimo Lusetti <ml...@gmail.com>
> wrote:
> >>
> >>> I agree. Some minor fixes are in 5.3 branch and not release (if memory
> >>> serve) so a release would be nice.
> >>>
> >>> We could plan a release asap, Kalle what's left for you? Others?
> >>>
> >>> Cheers
> >>>
> >>>
> >>> On Sun, Mar 31, 2013 at 1:26 PM, Bob Harner <bo...@gmail.com>
> wrote:
> >>>
> >>>> I do think a 5.3.7 release would be worthwhile. It seems to me that
> >>>> 5.4 needs a bit more shaking out (and documenting) before it is ready
> >>>> for release. Also, it has been almost 6 months since 5.3.6 was
> >>>> released, and until then we were producing a release about every 2
> >>>> months on average.
> >>>>
> >>>> On Sun, Mar 31, 2013 at 2:17 AM, Kalle Korhonen
> >>>> <ka...@gmail.com> wrote:
> >>>>> Is anybody in need of T5.3.7? I'm not quite ready myself just yet but
> >>>> there
> >>>>> are a few relevant fixes for us and I could put a few more in. Is
> >>> anybody
> >>>>> else looking for a 5.3.7 release? Massimo, I think you've done the
> last
> >>>>> 5.3.x releases. How's your experience been regarding the release
> >>> process?
> >>>>> Is everything documented, any gotchas, pain points etc? Or would you
> >>>>> perhaps be willing to cut one more release yourself?
> >>>>>
> >>>>> Kalle
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >>>> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>>
> >>>
> >>> --
> >>> Massimo
> >>> http://meridio.blogspot.com
> >>>
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: T5.3.7 release anyone?
Posted by Denis Stepanov <de...@gmail.com>.
It would be nice if someone would apply the patch from https://issues.apache.org/jira/browse/TAP5-2084 and include it in T5.3.7.
Good candidate could be https://issues.apache.org/jira/browse/TAP5-2051 reduces memory footprint, it's already applied in 5.4.
Denis
Apr 1, 2013 v 8:12 PM, Lenny Primak <lp...@hope.nyc.ny.us>:
> How about this one?
>
> https://issues.apache.org/jira/browse/TAP5-2014
>
> On Apr 1, 2013, at 1:38 PM, Kalle Korhonen <ka...@gmail.com> wrote:
>
>> Thanks Bob, Massimo. At least
>> https://issues.apache.org/jira/browse/TAP5-2097 and
>> https://issues.apache.org/jira/browse/TAP5-1890 merge to T5.3 for me, and
>> need to check if there was anything else. I can get them done this week.
>>
>> Kalle
>>
>>
>> On Mon, Apr 1, 2013 at 12:27 AM, Massimo Lusetti <ml...@gmail.com> wrote:
>>
>>> I agree. Some minor fixes are in 5.3 branch and not release (if memory
>>> serve) so a release would be nice.
>>>
>>> We could plan a release asap, Kalle what's left for you? Others?
>>>
>>> Cheers
>>>
>>>
>>> On Sun, Mar 31, 2013 at 1:26 PM, Bob Harner <bo...@gmail.com> wrote:
>>>
>>>> I do think a 5.3.7 release would be worthwhile. It seems to me that
>>>> 5.4 needs a bit more shaking out (and documenting) before it is ready
>>>> for release. Also, it has been almost 6 months since 5.3.6 was
>>>> released, and until then we were producing a release about every 2
>>>> months on average.
>>>>
>>>> On Sun, Mar 31, 2013 at 2:17 AM, Kalle Korhonen
>>>> <ka...@gmail.com> wrote:
>>>>> Is anybody in need of T5.3.7? I'm not quite ready myself just yet but
>>>> there
>>>>> are a few relevant fixes for us and I could put a few more in. Is
>>> anybody
>>>>> else looking for a 5.3.7 release? Massimo, I think you've done the last
>>>>> 5.3.x releases. How's your experience been regarding the release
>>> process?
>>>>> Is everything documented, any gotchas, pain points etc? Or would you
>>>>> perhaps be willing to cut one more release yourself?
>>>>>
>>>>> Kalle
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>> --
>>> Massimo
>>> http://meridio.blogspot.com
>>>
Re: T5.3.7 release anyone?
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
How about this one?
https://issues.apache.org/jira/browse/TAP5-2014
On Apr 1, 2013, at 1:38 PM, Kalle Korhonen <ka...@gmail.com> wrote:
> Thanks Bob, Massimo. At least
> https://issues.apache.org/jira/browse/TAP5-2097 and
> https://issues.apache.org/jira/browse/TAP5-1890 merge to T5.3 for me, and
> need to check if there was anything else. I can get them done this week.
>
> Kalle
>
>
> On Mon, Apr 1, 2013 at 12:27 AM, Massimo Lusetti <ml...@gmail.com> wrote:
>
>> I agree. Some minor fixes are in 5.3 branch and not release (if memory
>> serve) so a release would be nice.
>>
>> We could plan a release asap, Kalle what's left for you? Others?
>>
>> Cheers
>>
>>
>> On Sun, Mar 31, 2013 at 1:26 PM, Bob Harner <bo...@gmail.com> wrote:
>>
>>> I do think a 5.3.7 release would be worthwhile. It seems to me that
>>> 5.4 needs a bit more shaking out (and documenting) before it is ready
>>> for release. Also, it has been almost 6 months since 5.3.6 was
>>> released, and until then we were producing a release about every 2
>>> months on average.
>>>
>>> On Sun, Mar 31, 2013 at 2:17 AM, Kalle Korhonen
>>> <ka...@gmail.com> wrote:
>>>> Is anybody in need of T5.3.7? I'm not quite ready myself just yet but
>>> there
>>>> are a few relevant fixes for us and I could put a few more in. Is
>> anybody
>>>> else looking for a 5.3.7 release? Massimo, I think you've done the last
>>>> 5.3.x releases. How's your experience been regarding the release
>> process?
>>>> Is everything documented, any gotchas, pain points etc? Or would you
>>>> perhaps be willing to cut one more release yourself?
>>>>
>>>> Kalle
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>> --
>> Massimo
>> http://meridio.blogspot.com
>>
Re: T5.3.7 release anyone?
Posted by Kalle Korhonen <ka...@gmail.com>.
Thanks Bob, Massimo. At least
https://issues.apache.org/jira/browse/TAP5-2097 and
https://issues.apache.org/jira/browse/TAP5-1890 merge to T5.3 for me, and
need to check if there was anything else. I can get them done this week.
Kalle
On Mon, Apr 1, 2013 at 12:27 AM, Massimo Lusetti <ml...@gmail.com> wrote:
> I agree. Some minor fixes are in 5.3 branch and not release (if memory
> serve) so a release would be nice.
>
> We could plan a release asap, Kalle what's left for you? Others?
>
> Cheers
>
>
> On Sun, Mar 31, 2013 at 1:26 PM, Bob Harner <bo...@gmail.com> wrote:
>
> > I do think a 5.3.7 release would be worthwhile. It seems to me that
> > 5.4 needs a bit more shaking out (and documenting) before it is ready
> > for release. Also, it has been almost 6 months since 5.3.6 was
> > released, and until then we were producing a release about every 2
> > months on average.
> >
> > On Sun, Mar 31, 2013 at 2:17 AM, Kalle Korhonen
> > <ka...@gmail.com> wrote:
> > > Is anybody in need of T5.3.7? I'm not quite ready myself just yet but
> > there
> > > are a few relevant fixes for us and I could put a few more in. Is
> anybody
> > > else looking for a 5.3.7 release? Massimo, I think you've done the last
> > > 5.3.x releases. How's your experience been regarding the release
> process?
> > > Is everything documented, any gotchas, pain points etc? Or would you
> > > perhaps be willing to cut one more release yourself?
> > >
> > > Kalle
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
> --
> Massimo
> http://meridio.blogspot.com
>
Re: T5.3.7 release anyone?
Posted by Massimo Lusetti <ml...@gmail.com>.
I agree. Some minor fixes are in 5.3 branch and not release (if memory
serve) so a release would be nice.
We could plan a release asap, Kalle what's left for you? Others?
Cheers
On Sun, Mar 31, 2013 at 1:26 PM, Bob Harner <bo...@gmail.com> wrote:
> I do think a 5.3.7 release would be worthwhile. It seems to me that
> 5.4 needs a bit more shaking out (and documenting) before it is ready
> for release. Also, it has been almost 6 months since 5.3.6 was
> released, and until then we were producing a release about every 2
> months on average.
>
> On Sun, Mar 31, 2013 at 2:17 AM, Kalle Korhonen
> <ka...@gmail.com> wrote:
> > Is anybody in need of T5.3.7? I'm not quite ready myself just yet but
> there
> > are a few relevant fixes for us and I could put a few more in. Is anybody
> > else looking for a 5.3.7 release? Massimo, I think you've done the last
> > 5.3.x releases. How's your experience been regarding the release process?
> > Is everything documented, any gotchas, pain points etc? Or would you
> > perhaps be willing to cut one more release yourself?
> >
> > Kalle
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Massimo
http://meridio.blogspot.com
Re: T5.3.7 release anyone?
Posted by Bob Harner <bo...@gmail.com>.
I do think a 5.3.7 release would be worthwhile. It seems to me that
5.4 needs a bit more shaking out (and documenting) before it is ready
for release. Also, it has been almost 6 months since 5.3.6 was
released, and until then we were producing a release about every 2
months on average.
On Sun, Mar 31, 2013 at 2:17 AM, Kalle Korhonen
<ka...@gmail.com> wrote:
> Is anybody in need of T5.3.7? I'm not quite ready myself just yet but there
> are a few relevant fixes for us and I could put a few more in. Is anybody
> else looking for a 5.3.7 release? Massimo, I think you've done the last
> 5.3.x releases. How's your experience been regarding the release process?
> Is everything documented, any gotchas, pain points etc? Or would you
> perhaps be willing to cut one more release yourself?
>
> Kalle
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org