Re: [VOTE] Release Apache Wicket 6.5.0

[Korbinian Bachl]

How can it be published there on 19th of January?

That's two (2) days before even the vote was closed!

--
Korbinian

- Ursprüngliche Mail -
> Von: "Guillaume Smet" 
> An: dev@wicket.apache.org
> Gesendet: Mittwoch, 23. Januar 2013 01:28:29
> Betreff: Re: [VOTE] Release Apache Wicket 6.5.0
> 
> On Tue, Jan 22, 2013 at 10:09 PM, Andreas Pieber  wrote:
> > Will the release be available before at m2 central?
> 
> It's already there:
> http://search.maven.org/#search|gav|1|g%3A%22org.apache.wicket%22%20AND%20a%3A%22wicket%22
> 
> --
> Guillaume
> 

Re: [VOTE] Release Apache Wicket 6.5.0

[Emond Papegaaij]

I think they use the file creation date. If you look at 
http://repo1.maven.org/maven2/org/apache/wicket/wicket-core/6.5.0/ you see 
that all files are created at the 18th of jan, but the directory itself was 
created at the 22th of jan.

Emond

On Wednesday 23 January 2013 09:02:44 Korbinian Bachl wrote:
> How can it be published there on 19th of January?
> 
> That's two (2) days before even the vote was closed!
> 
> --
> Korbinian
> 
> - Ursprüngliche Mail -
> 
> > Von: "Guillaume Smet" 
> > An: dev@wicket.apache.org
> > Gesendet: Mittwoch, 23. Januar 2013 01:28:29
> > Betreff: Re: [VOTE] Release Apache Wicket 6.5.0
> > 
> > On Tue, Jan 22, 2013 at 10:09 PM, Andreas Pieber  
wrote:
> > > Will the release be available before at m2 central?
> > 
> > It's already there:
> > http://search.maven.org/#search|gav|1|g%3A%22org.apache.wicket%22%20AND%20
> > a%3A%22wicket%22
> > 
> > --
> > Guillaume

Re: [VOTE] Release Apache Wicket 6.5.0

[Martin Grigorov]

I'm preparing the announcement


On Wed, Jan 23, 2013 at 10:09 AM, Emond Papegaaij <
emond.papega...@topicus.nl> wrote:

> I think they use the file creation date. If you look at
> http://repo1.maven.org/maven2/org/apache/wicket/wicket-core/6.5.0/ you see
> that all files are created at the 18th of jan, but the directory itself was
> created at the 22th of jan.
>
> Emond
>
> On Wednesday 23 January 2013 09:02:44 Korbinian Bachl wrote:
> > How can it be published there on 19th of January?
> >
> > That's two (2) days before even the vote was closed!
> >
> > --
> > Korbinian
> >
> > - Ursprüngliche Mail -
> >
> > > Von: "Guillaume Smet" 
> > > An: dev@wicket.apache.org
> > > Gesendet: Mittwoch, 23. Januar 2013 01:28:29
> > > Betreff: Re: [VOTE] Release Apache Wicket 6.5.0
> > >
> > > On Tue, Jan 22, 2013 at 10:09 PM, Andreas Pieber 
> wrote:
> > > > Will the release be available before at m2 central?
> > >
> > > It's already there:
> > >
> http://search.maven.org/#search|gav|1|g%3A%22org.apache.wicket%22%20AND%20
> > > a%3A%22wicket%22
> > >
> > > --
> > > Guillaume
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com 

[Announce] Apache Wicket 6.5.0 is released

[Martin Grigorov]

This is the fifth maintenance release of the Wicket 6.x series. This
release brings over 32 bug fixes and improvements.

Git tag:
release/wicket-6.5.0

Changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561&version=12323540

Maven:

 org.apache.wicket
 wicket-core
 6.5.0



Download the full distribution (including source):
http://www.apache.org/dyn/closer.cgi/wicket/6.5.0

The Wicket team

Re: [3/4] git commit: Start next development version

[Martin Funk]

Some ".settings" files are also affected.

./wicket-examples/.settings/org.eclipse.wst.common.component
./wicket-experimental/wicket-examples-parent/wicket-examples-war/.settings/org.eclipse.wst.common.component

Is that intended to have the wicket version parameter creep into eclipse 
settings files?

mf


Am 23.01.2013 um 12:18 schrieb Martin Funk :

> This commit didn't do what it promised.
> 
> Still references to 6.5.0-SNAPSHOT left in some pom.xml
> 
> › grep -R "6.5.0" --include "pom.xml" .
> ./archetypes/quickstart/src/main/resources/archetype-resources/pom.xml:   
> 6.5.0-SNAPSHOT
> ./archetypes/quickstart/target/classes/archetype-resources/pom.xml:   
> 6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./pom.xml:6.5.0-SNAPSHOT
> ./testing/wicket-threadtest/pom.xml:  
> 6.5.0-SNAPSHOT
> 
> › git status
> # On branch master
> nothing to commit (working directory clean)
> 
> › git log -1
> commit 68a6c04dca830d526e1ef02869fa467565aa819f
> Merge: 1263da8 697ffe0
> Author: Martijn Dashorst 
> Date:   Tue Jan 22 12:08:07 2013 +0100
> 
>Merge remote-tracking branch 'origin/master'
> 
> 
> 
> 
> mf
> 
> 
> Anfang der weitergeleiteten Nachricht:
> 
>> Von: dasho...@apache.org
>> Betreff: [3/4] git commit: Start next development version
>> Datum: 22. Januar 2013 12:08:39 MEZ
>> An: comm...@wicket.apache.org
>> Antwort an: dev@wicket.apache.org
>> 
>> Start next development version
>> 
>> 
>> Project: http://git-wip-us.apache.org/repos/asf/wicket/repo
>> Commit: http://git-wip-us.apache.org/repos/asf/wicket/commit/1263da8a
>> Tree: http://git-wip-us.apache.org/repos/asf/wicket/tree/1263da8a
>> Diff: http://git-wip-us.apache.org/repos/asf/wicket/diff/1263da8a
>> 
>> Branch: refs/heads/master
>> Commit: 1263da8acbf3f488ac5d50f040869fd74a528b25
>> Parents: 17281a7
>> Author: Martijn Dashorst 
>> Authored: Tue Jan 22 12:05:31 2013 +0100
>> Committer: Martijn Dashorst 
>> Committed: Tue Jan 22 12:05:31 2013 +0100
>> 
>> --
>> archetypes/quickstart/pom.xml  |2 +-
>> pom.xml|   22 +++---
>> testing/wicket-common-tests/pom.xml|2 +-
>> wicket-auth-roles/pom.xml  |2 +-
>> wicket-cdi/pom.xml |2 +-
>> wicket-core/pom.xml|2 +-
>> wicket-datetime/pom.xml|2 +-
>> wicket-devutils/pom.xml|2 +-
>> wicket-examples/pom.xml|2 +-
>> wicket-experimental/pom.xml|2 +-
>> wicket-experimental/wicket-atmosphere/pom.xml  |4 +-
>> wicket-experimental/wicket-bean-validation/pom.xml |4 +-
>> wicket-experimental/wicket-bootstrap/pom.xml   |4 +-
>> wicket-experimental/wicket-examples-parent/pom.xml |4 +-
>> .../wicket-examples-jar/pom.xml|4 +-
>> .../wicket-examples-war/pom.xml|4 +-
>> .../wicket-native-websocket/pom.xml|4 +-
>> .../wicket-native-websocket-core/pom.xml   |4 +-
>> .../wicket-native-websocket-jetty/pom.xml  |4 +-
>> .../wicket-native-websocket-jetty9/pom.xml |4 +-
>> .../wicket-native-websocket-tomcat/pom.xml |4 +-
>> wicket-extensions/pom.xml  |2 +-
>> wicket-guice/pom.xml   |2 +-
>> wicket-ioc/pom.xml |2 +-
>> wicket-jmx/pom.xml |2 +-
>> wicket-objectssizeof-agent/pom.xml |2 +-
>> wicket-request/pom.xml |4 +-
>> wicket-spring/pom.xml  |2 +-
>> wicket-util/pom.xml|2 +-
>> wicket-velocity/pom.xml|2 +-
>> wicket/pom.xml |2 +-
>> 31 files changed, 53 insertions(+), 53 deletions(-)
>> --
>> 
>> 
>> http://git-wip-us.apache.org/repos/asf/wicket/blob/1263da8a/archetypes/quickstart/pom.xml
>> -

Fwd: [3/4] git commit: Start next development version

[Martin Funk]

This commit didn't do what it promised.

Still references to 6.5.0-SNAPSHOT left in some pom.xml

› grep -R "6.5.0" --include "pom.xml" .
./archetypes/quickstart/src/main/resources/archetype-resources/pom.xml: 
6.5.0-SNAPSHOT
./archetypes/quickstart/target/classes/archetype-resources/pom.xml: 
6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./pom.xml:  6.5.0-SNAPSHOT
./testing/wicket-threadtest/pom.xml:
6.5.0-SNAPSHOT

› git status
# On branch master
nothing to commit (working directory clean)

› git log -1
commit 68a6c04dca830d526e1ef02869fa467565aa819f
Merge: 1263da8 697ffe0
Author: Martijn Dashorst 
Date:   Tue Jan 22 12:08:07 2013 +0100

Merge remote-tracking branch 'origin/master'




mf


Anfang der weitergeleiteten Nachricht:

> Von: dasho...@apache.org
> Betreff: [3/4] git commit: Start next development version
> Datum: 22. Januar 2013 12:08:39 MEZ
> An: comm...@wicket.apache.org
> Antwort an: dev@wicket.apache.org
> 
> Start next development version
> 
> 
> Project: http://git-wip-us.apache.org/repos/asf/wicket/repo
> Commit: http://git-wip-us.apache.org/repos/asf/wicket/commit/1263da8a
> Tree: http://git-wip-us.apache.org/repos/asf/wicket/tree/1263da8a
> Diff: http://git-wip-us.apache.org/repos/asf/wicket/diff/1263da8a
> 
> Branch: refs/heads/master
> Commit: 1263da8acbf3f488ac5d50f040869fd74a528b25
> Parents: 17281a7
> Author: Martijn Dashorst 
> Authored: Tue Jan 22 12:05:31 2013 +0100
> Committer: Martijn Dashorst 
> Committed: Tue Jan 22 12:05:31 2013 +0100
> 
> --
> archetypes/quickstart/pom.xml  |2 +-
> pom.xml|   22 +++---
> testing/wicket-common-tests/pom.xml|2 +-
> wicket-auth-roles/pom.xml  |2 +-
> wicket-cdi/pom.xml |2 +-
> wicket-core/pom.xml|2 +-
> wicket-datetime/pom.xml|2 +-
> wicket-devutils/pom.xml|2 +-
> wicket-examples/pom.xml|2 +-
> wicket-experimental/pom.xml|2 +-
> wicket-experimental/wicket-atmosphere/pom.xml  |4 +-
> wicket-experimental/wicket-bean-validation/pom.xml |4 +-
> wicket-experimental/wicket-bootstrap/pom.xml   |4 +-
> wicket-experimental/wicket-examples-parent/pom.xml |4 +-
> .../wicket-examples-jar/pom.xml|4 +-
> .../wicket-examples-war/pom.xml|4 +-
> .../wicket-native-websocket/pom.xml|4 +-
> .../wicket-native-websocket-core/pom.xml   |4 +-
> .../wicket-native-websocket-jetty/pom.xml  |4 +-
> .../wicket-native-websocket-jetty9/pom.xml |4 +-
> .../wicket-native-websocket-tomcat/pom.xml |4 +-
> wicket-extensions/pom.xml  |2 +-
> wicket-guice/pom.xml   |2 +-
> wicket-ioc/pom.xml |2 +-
> wicket-jmx/pom.xml |2 +-
> wicket-objectssizeof-agent/pom.xml |2 +-
> wicket-request/pom.xml |4 +-
> wicket-spring/pom.xml  |2 +-
> wicket-util/pom.xml|2 +-
> wicket-velocity/pom.xml|2 +-
> wicket/pom.xml |2 +-
> 31 files changed, 53 insertions(+), 53 deletions(-)
> --
> 
> 
> http://git-wip-us.apache.org/repos/asf/wicket/blob/1263da8a/archetypes/quickstart/pom.xml
> --
> diff --git a/archetypes/quickstart/pom.xml b/archetypes/quickstart/pom.xml
> index c50b821..08b9071 100644
> --- a/archetypes/quickstart/pom.xml
> +++ b/archetypes/quickstart/pom.xml
> @@ -20,7 +20,7 @@
>   
>   org.apache.wicket
>   wicket-parent
> - 6.5.0-SNAPSHOT
> + 6.6.0-SNAPSHOT
>   ../../pom.xml
>   
>   wicket-archetype-quickstart
> 

Feature Question: Semi stateless Behavior after Session Expiry

[Bernard]

Hi,

As an outsider to the Wicket developer community (sorry), I am trying
to improve the response to the dreaded PageExpiredException in my
application, currently with focus on non-AJAX pages.

The result of testing responses for every of my pages is horrible
because almost no pages are stateless. I don't want to go the
stateless path yet because in that case I feel I lose Wicket's
productivity advantage. It is just too convenient to pass LDM's in
page constructors compared with coding PageParameter and dealing with
the obvious checks avoiding security exploits.

For most stateful pages, some hierarchy will never change such as a
Link, StatelessLink sign-out menu item. It is frustrating to present
the user with denial of service (PageExpiredException) in case the
user wants to sign out after session expiry. Users cannot understand
that especially with a remember-me cookie that always gives them a
session whatever they do.

I am looking for a result where after expiry Wicket will execute some
requests by treating the page as if it was stateless even if it isn't.

This is a compromise approach, but if successful it has the advantage
that the additional effort of making a page stateless would need to be
spent only where it is really obvious and worth it.

Obviously some things must not happen such as updating a list item
where the page does not get a model for it from a default constructor.

But a sign-out link which is always in the same place of the page
hierarchy should get its onClick method executed.

I am asking for the support of the developer community for this
feature being supported inside the Wicket framework. My selling point
is that from my perspective PageExpiredException is Wicket's Achilles
heel, and making progress in this area, even gradually, would be
beneficial for most users of the framework.

Kind Regards,

Bernard