Closed GoogleCodeExporter closed 9 years ago
This has already been fixed on trunk (will be future 1.2 release). We could try
to apply the same patch to 1.x branch and release a 1.1.2?
Ernesto
Original comment by reier...@gmail.com
on 29 Nov 2010 at 1:23
Hi Ernesto,
Can you wait the close of the issue 139 please ? (I woulid like to now if this
bug or not). Otherwise, I'm agreed for a new release release (with a migration
with Wicket 1.4.14).
Cheers
Julien Roche
Original comment by roche....@gmail.com
on 29 Nov 2010 at 1:33
Julien,
It seem issue 139 was invalid after all: if proven otherwise we can reopen it.
Cheers,
Ernesto
Original comment by reier...@gmail.com
on 29 Nov 2010 at 2:01
Ernesto,
Yep, the issue 139 is invalide. So you can push a new release.
See you.
Julienn
Original comment by roche....@gmail.com
on 29 Nov 2010 at 2:27
Original comment by roche....@gmail.com
on 1 Dec 2010 at 7:22
Original issue reported on code.google.com by
norc...@gmail.com
on 29 Nov 2010 at 1:08