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 guillaume.s...@gmail.com
An: dev@wicket.apache.org
Gesendet: Mittwoch, 23. Januar 2013 01:28:29
Betreff: Re: [VOTE] Release
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
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
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=12310561version=12323540
Maven:
dependency
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
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:
wicket.version6.5.0-SNAPSHOT/wicket.version
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