Hello,

Following the release of wicket 1.5-rc2 I've cut a matching release for wicketstuff-core (https://github.com/wicketstuff/core).

The artifacts have been promoted and are now available through the maven central repository.

They can be retrieved like this:

<dependency>
<groupId>org.wicketstuff</groupId>
<artifactId>wicketstuff-springreference</artifactId>
<version>1.5-rc2</version>
</dependency>

The release tag is here: https://github.com/wicketstuff/core/tree/wicketstuff-core-1.5-rc2

Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here: https://github.com/wicketstuff/core/wiki

Release Notes - WicketStuff Core - Version 1.5-rc2:

akiraly (35 commits):
Summary:
    Contributed new wicketstuff-springreference project.
    Contributed new wicketstuff-logback project.
    Various pom updates to better align with upstream wicket release.
    Upgrade from jetty 6 to jetty 7.
    Assorted pom changes to improve the consistency of dependencies used.

Martin Grigorov (22):
Summary:

Issue 10 - Fix wicket-scala-sample in master branch due to upstream change Issue 11 - shiro-example-spring-hibernate pom has a wrong parent version. Update Maven dependencies to newer versions (version that match Wicket's dependencies)
      Improvements to the scala integration project.

Michael O'Cleirigh (7 commits):
Summary:
      Fixing breakage caused by upstream wicket changes since 1.5-RC1.
      Minor changes related to the release.

Christian Strempfer (3 commits):
Summary:
Fixed a bug, which causes the InputBehavior to execute multiple times after an AJAX update.

To see a list of all the commits between wicketstuff-core-1.5-RC1.1 and wicketstuff-core-1.5-rc2 use this command (on branch master in the root directory):

git log --name-only wicketstuff-core-1.5-rc2 wicketstuff-core-1.5-RC1.1..

The plan is to release a 1.5 series version within one month from today. If you commit code and/or want a release sooner let me know as one month is the worst case target.

Regards,

Mike

Reply via email to