Re: Wicketstuff build

2018-02-18 Thread Maxim Solodovnik 
Thanks Andrea,

somehow I miss this difference, will fix the Test and perform release
later tonight!

On Sun, Feb 18, 2018 at 10:30 PM, Andrea Del Bene  wrote:
> I don't know why but on master we have
> 'assertFalse(session.isSessionInvalidated());' at the end of the tests while
> on 7.x is assertTrue. It should be a simple typo.
>
>
>
> On 18/02/2018 15:02, Maxim Solodovnik wrote:
>>
>> Also got error at org.wicketstuff.security.SessionInvalidationTest
>> while running tests in wicket-7.x branch
>> According to code invalidate works and did
>> `RequestCycle.get().setMetaData(SESSION_INVALIDATED, true);`
>>
>> but later on
>> `RequestCycle.get().getMetaData(SESSION_INVALIDATED)` returns `true`
>>
>> don't get it :(
>>
>> On Sun, Feb 18, 2018 at 12:21 PM, Maxim Solodovnik 
>> wrote:
>>>
>>> It seems it is impossible to create "secret" Travis command line option
>>> ...
>>> Is this true?
>>>
>>> Am I right thinking the only "correct Travis" way is via Environment
>>> variable?
>>>
>>> On Sun, Feb 18, 2018 at 11:38 AM, Maxim Solodovnik 
>>> wrote:

 Have added possibility to specify API key via command line:

 https://github.com/wicketstuff/core/commit/e7d8ed7721a2dbcdb04082dac5c290c2d17d454b
 Correct API key can be added in Travis config as well

 On Sun, Feb 18, 2018 at 2:42 AM, Andrea Del Bene 
 wrote:
>
> Locally you can temporary use the @ignore tag, but I'm afraid there's
> no
> way to bypass it on Travis. We can just wait long enough to re-run the
> building, hoping that some one else hasn't already reached the query
> limit
> in the meantime.
>
> PS: on 7.x branch I see test
> org.wicketstuff.security.SessionInvalidationTest is failing. I haven't
> investigated the problem yet but it could be something related to the
> changes to mock entities made with WICKET-6441.
>
>
> On 17/02/2018 17:16, Maxim Solodovnik wrote:
>>
>> Hello All,
>>
>> I have started local build of wickestuff right now and got following
>> errors:
>> I believe there might be limitation on query per day/per application
>>
>> What is the correct way to bypass this limitation?
>>
>> Thanks in advance!
>>
>>
>> ---
>>T E S T S
>> ---
>> Running wicket.contrib.gmap.util.GMapTest
>> log4j:WARN No appenders could be found for logger
>> (org.apache.wicket.Application).
>> log4j:WARN Please initialize the log4j system properly.
>> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig
>> for
>> more info.
>> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.358
>> sec -
>> in wicket.contrib.gmap.util.GMapTest
>> Running wicket.contrib.gmap.util.GeocoderTest
>> Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.433
>> sec
>> <<< FAILURE! - in wicket.contrib.gmap.util.GeocoderTest
>> testCenterAndFitZoomForAdress(wicket.contrib.gmap.util.GeocoderTest)
>> Time
>> elapsed: 0.359 sec  <<< ERROR!
>> org.wicketstuff.gmap.geocoder.GeocoderException: OVER_QUERY_LIMIT
>> at org.wicketstuff.gmap.geocoder.Geocoder.decode(Geocoder.java:130)
>> at org.wicketstuff.gmap.geocoder.Geocoder.geocode(Geocoder.java:182)
>> at
>>
>>
>> org.wicketstuff.gmap.geocoder.Geocoder.centerAndFitZoomForAdress(Geocoder.java:254)
>> at
>>
>>
>> wicket.contrib.gmap.util.GeocoderTest.testCenterAndFitZoomForAdress(GeocoderTest.java:61)
>>
>> testGeocoding(wicket.contrib.gmap.util.GeocoderTest)  Time elapsed:
>> 0.074
>> sec  <<< ERROR!
>> org.wicketstuff.gmap.geocoder.GeocoderException: OVER_QUERY_LIMIT
>> at org.wicketstuff.gmap.geocoder.Geocoder.decode(Geocoder.java:130)
>> at org.wicketstuff.gmap.geocoder.Geocoder.geocode(Geocoder.java:182)
>> at
>>
>> wicket.contrib.gmap.util.GeocoderTest.testGeocoding(GeocoderTest.java:41)
>>
>>
>> Results :
>>
>> Tests in error:
>> GeocoderTest.testCenterAndFitZoomForAdress:61 » Geocoder
>> OVER_QUERY_LIMIT
>> GeocoderTest.testGeocoding:41 » Geocoder OVER_QUERY_LIMIT
>>
>>
>>
>>


 --
 WBR
 Maxim aka solomax
>>>
>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>
>>
>>
>



-- 
WBR
Maxim aka solomax

Re: Wicketstuff build

2018-02-18 Thread Andrea Del Bene 
I don't know why but on master we have 
'assertFalse(session.isSessionInvalidated());' at the end of the tests 
while on 7.x is assertTrue. It should be a simple typo.



On 18/02/2018 15:02, Maxim Solodovnik wrote:

Also got error at org.wicketstuff.security.SessionInvalidationTest
while running tests in wicket-7.x branch
According to code invalidate works and did
`RequestCycle.get().setMetaData(SESSION_INVALIDATED, true);`

but later on
`RequestCycle.get().getMetaData(SESSION_INVALIDATED)` returns `true`

don't get it :(

On Sun, Feb 18, 2018 at 12:21 PM, Maxim Solodovnik  wrote:

It seems it is impossible to create "secret" Travis command line option ...
Is this true?

Am I right thinking the only "correct Travis" way is via Environment
variable?

On Sun, Feb 18, 2018 at 11:38 AM, Maxim Solodovnik 
wrote:

Have added possibility to specify API key via command line:
https://github.com/wicketstuff/core/commit/e7d8ed7721a2dbcdb04082dac5c290c2d17d454b
Correct API key can be added in Travis config as well

On Sun, Feb 18, 2018 at 2:42 AM, Andrea Del Bene 
wrote:

Locally you can temporary use the @ignore tag, but I'm afraid there's no
way to bypass it on Travis. We can just wait long enough to re-run the
building, hoping that some one else hasn't already reached the query limit
in the meantime.

PS: on 7.x branch I see test
org.wicketstuff.security.SessionInvalidationTest is failing. I haven't
investigated the problem yet but it could be something related to the
changes to mock entities made with WICKET-6441.


On 17/02/2018 17:16, Maxim Solodovnik wrote:

Hello All,

I have started local build of wickestuff right now and got following
errors:
I believe there might be limitation on query per day/per application

What is the correct way to bypass this limitation?

Thanks in advance!


---
   T E S T S
---
Running wicket.contrib.gmap.util.GMapTest
log4j:WARN No appenders could be found for logger
(org.apache.wicket.Application).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.358
sec -
in wicket.contrib.gmap.util.GMapTest
Running wicket.contrib.gmap.util.GeocoderTest
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.433
sec
<<< FAILURE! - in wicket.contrib.gmap.util.GeocoderTest
testCenterAndFitZoomForAdress(wicket.contrib.gmap.util.GeocoderTest)
Time
elapsed: 0.359 sec  <<< ERROR!
org.wicketstuff.gmap.geocoder.GeocoderException: OVER_QUERY_LIMIT
at org.wicketstuff.gmap.geocoder.Geocoder.decode(Geocoder.java:130)
at org.wicketstuff.gmap.geocoder.Geocoder.geocode(Geocoder.java:182)
at

org.wicketstuff.gmap.geocoder.Geocoder.centerAndFitZoomForAdress(Geocoder.java:254)
at

wicket.contrib.gmap.util.GeocoderTest.testCenterAndFitZoomForAdress(GeocoderTest.java:61)

testGeocoding(wicket.contrib.gmap.util.GeocoderTest)  Time elapsed:
0.074
sec  <<< ERROR!
org.wicketstuff.gmap.geocoder.GeocoderException: OVER_QUERY_LIMIT
at org.wicketstuff.gmap.geocoder.Geocoder.decode(Geocoder.java:130)
at org.wicketstuff.gmap.geocoder.Geocoder.geocode(Geocoder.java:182)
at
wicket.contrib.gmap.util.GeocoderTest.testGeocoding(GeocoderTest.java:41)


Results :

Tests in error:
GeocoderTest.testCenterAndFitZoomForAdress:61 » Geocoder
OVER_QUERY_LIMIT
GeocoderTest.testGeocoding:41 » Geocoder OVER_QUERY_LIMIT







--
WBR
Maxim aka solomax




--
WBR
Maxim aka solomax

Re: Wicketstuff build

2018-02-18 Thread Maxim Solodovnik 
Also got error at org.wicketstuff.security.SessionInvalidationTest
while running tests in wicket-7.x branch
According to code invalidate works and did
`RequestCycle.get().setMetaData(SESSION_INVALIDATED, true);`

but later on
`RequestCycle.get().getMetaData(SESSION_INVALIDATED)` returns `true`

don't get it :(

On Sun, Feb 18, 2018 at 12:21 PM, Maxim Solodovnik  wrote:
> It seems it is impossible to create "secret" Travis command line option ...
> Is this true?
>
> Am I right thinking the only "correct Travis" way is via Environment
> variable?
>
> On Sun, Feb 18, 2018 at 11:38 AM, Maxim Solodovnik 
> wrote:
>>
>> Have added possibility to specify API key via command line:
>> https://github.com/wicketstuff/core/commit/e7d8ed7721a2dbcdb04082dac5c290c2d17d454b
>> Correct API key can be added in Travis config as well
>>
>> On Sun, Feb 18, 2018 at 2:42 AM, Andrea Del Bene 
>> wrote:
>>>
>>> Locally you can temporary use the @ignore tag, but I'm afraid there's no
>>> way to bypass it on Travis. We can just wait long enough to re-run the
>>> building, hoping that some one else hasn't already reached the query limit
>>> in the meantime.
>>>
>>> PS: on 7.x branch I see test
>>> org.wicketstuff.security.SessionInvalidationTest is failing. I haven't
>>> investigated the problem yet but it could be something related to the
>>> changes to mock entities made with WICKET-6441.
>>>
>>>
>>> On 17/02/2018 17:16, Maxim Solodovnik wrote:

 Hello All,

 I have started local build of wickestuff right now and got following
 errors:
 I believe there might be limitation on query per day/per application

 What is the correct way to bypass this limitation?

 Thanks in advance!


 ---
   T E S T S
 ---
 Running wicket.contrib.gmap.util.GMapTest
 log4j:WARN No appenders could be found for logger
 (org.apache.wicket.Application).
 log4j:WARN Please initialize the log4j system properly.
 log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
 more info.
 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.358
 sec -
 in wicket.contrib.gmap.util.GMapTest
 Running wicket.contrib.gmap.util.GeocoderTest
 Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.433
 sec
 <<< FAILURE! - in wicket.contrib.gmap.util.GeocoderTest
 testCenterAndFitZoomForAdress(wicket.contrib.gmap.util.GeocoderTest)
 Time
 elapsed: 0.359 sec  <<< ERROR!
 org.wicketstuff.gmap.geocoder.GeocoderException: OVER_QUERY_LIMIT
 at org.wicketstuff.gmap.geocoder.Geocoder.decode(Geocoder.java:130)
 at org.wicketstuff.gmap.geocoder.Geocoder.geocode(Geocoder.java:182)
 at

 org.wicketstuff.gmap.geocoder.Geocoder.centerAndFitZoomForAdress(Geocoder.java:254)
 at

 wicket.contrib.gmap.util.GeocoderTest.testCenterAndFitZoomForAdress(GeocoderTest.java:61)

 testGeocoding(wicket.contrib.gmap.util.GeocoderTest)  Time elapsed:
 0.074
 sec  <<< ERROR!
 org.wicketstuff.gmap.geocoder.GeocoderException: OVER_QUERY_LIMIT
 at org.wicketstuff.gmap.geocoder.Geocoder.decode(Geocoder.java:130)
 at org.wicketstuff.gmap.geocoder.Geocoder.geocode(Geocoder.java:182)
 at
 wicket.contrib.gmap.util.GeocoderTest.testGeocoding(GeocoderTest.java:41)


 Results :

 Tests in error:
GeocoderTest.testCenterAndFitZoomForAdress:61 » Geocoder
 OVER_QUERY_LIMIT
GeocoderTest.testGeocoding:41 » Geocoder OVER_QUERY_LIMIT




>>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>
>
>
>
> --
> WBR
> Maxim aka solomax



-- 
WBR
Maxim aka solomax

Re: Wicketstuff build

2018-02-18 Thread Andrea Del Bene 
AFAIK you are right. I would choose to use an environment variable 
defined in the env section of .travis.yml.


Thank you Maxim!


On 18/02/2018 06:21, Maxim Solodovnik wrote:

It seems it is impossible to create "secret" Travis command line option ...
Is this true?

Am I right thinking the only "correct Travis" way is via Environment
variable?

On Sun, Feb 18, 2018 at 11:38 AM, Maxim Solodovnik 
wrote:


Have added possibility to specify API key via command line:
https://github.com/wicketstuff/core/commit/e7d8ed7721a2dbcdb04082dac5c290
c2d17d454b
Correct API key can be added in Travis config as well

On Sun, Feb 18, 2018 at 2:42 AM, Andrea Del Bene 
wrote:


Locally you can temporary use the @ignore tag, but I'm afraid there's no
way to bypass it on Travis. We can just wait long enough to re-run the
building, hoping that some one else hasn't already reached the query limit
in the meantime.

PS: on 7.x branch I see test org.wicketstuff.security.SessionInvalidationTest
is failing. I haven't investigated the problem yet but it could be
something related to the changes to mock entities made with WICKET-6441.


On 17/02/2018 17:16, Maxim Solodovnik wrote:


Hello All,

I have started local build of wickestuff right now and got following
errors:
I believe there might be limitation on query per day/per application

What is the correct way to bypass this limitation?

Thanks in advance!


---
   T E S T S
---
Running wicket.contrib.gmap.util.GMapTest
log4j:WARN No appenders could be found for logger
(org.apache.wicket.Application).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.358
sec -
in wicket.contrib.gmap.util.GMapTest
Running wicket.contrib.gmap.util.GeocoderTest
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.433 sec
<<< FAILURE! - in wicket.contrib.gmap.util.GeocoderTest
testCenterAndFitZoomForAdress(wicket.contrib.gmap.util.GeocoderTest)
Time
elapsed: 0.359 sec  <<< ERROR!
org.wicketstuff.gmap.geocoder.GeocoderException: OVER_QUERY_LIMIT
at org.wicketstuff.gmap.geocoder.Geocoder.decode(Geocoder.java:130)
at org.wicketstuff.gmap.geocoder.Geocoder.geocode(Geocoder.java:182)
at
org.wicketstuff.gmap.geocoder.Geocoder.centerAndFitZoomForAd
ress(Geocoder.java:254)
at
wicket.contrib.gmap.util.GeocoderTest.testCenterAndFitZoomFo
rAdress(GeocoderTest.java:61)

testGeocoding(wicket.contrib.gmap.util.GeocoderTest)  Time elapsed:
0.074
sec  <<< ERROR!
org.wicketstuff.gmap.geocoder.GeocoderException: OVER_QUERY_LIMIT
at org.wicketstuff.gmap.geocoder.Geocoder.decode(Geocoder.java:130)
at org.wicketstuff.gmap.geocoder.Geocoder.geocode(Geocoder.java:182)
at wicket.contrib.gmap.util.GeocoderTest.testGeocoding(Geocoder
Test.java:41)


Results :

Tests in error:
GeocoderTest.testCenterAndFitZoomForAdress:61 » Geocoder
OVER_QUERY_LIMIT
GeocoderTest.testGeocoding:41 » Geocoder OVER_QUERY_LIMIT







--
WBR
Maxim aka solomax

Re: [VOTE] Release Apache Wicket 6.29.0

2018-02-18 Thread Maxim Solodovnik 
It seems I can't compile :(
I have jdk6 and maven 3.2.5, but build fails with
"org/codehaus/mojo/clirr/ClirrCheckMojo : Unsupported major.minor
version 51.0"
sorry can't vote :(

On Sun, Feb 18, 2018 at 5:31 PM, Sven Meier  wrote:
> +1
>
> Many thanks
> Sven
>
>
>
> Am 17.02.2018 um 23:47 schrieb Tobias Soloschenko:
>>
>> +1 :-)
>>
>> kind regards
>>
>> Tobias
>>
>>> Am 17.02.2018 um 19:28 schrieb Andrea Del Bene :
>>>
>>> This is a vote to release Apache Wicket 6.29.0
>>>
>>> Please download the source distributions found in our staging area
>>> linked below.
>>>
>>> I have included the signatures for both the source archives. This vote
>>> lasts for 72 hours minimum.
>>>
>>> [ ] Yes, release Apache Wicket 6.29.0
>>> [ ] No, don't release Apache Wicket 6.29.0, because ...
>>>
>>> Distributions, changelog, keys and signatures can be found at:
>>>
>>>  https://dist.apache.org/repos/dist/dev/wicket/6.29.0
>>>
>>> Staging repository:
>>>
>>> https://repository.apache.org/content/repositories/orgapachewicket-1107/
>>>
>>> The binaries are available in the above link, as are a staging
>>> repository for Maven. Typically the vote is on the source, but should
>>> you find a problem with one of the binaries, please let me know, I can
>>> re-roll them some way or the other.
>>>
>>> Staging git repository data:
>>>
>>>  Repository:  g...@github.com:bitstorm/wicket.git
>>>  Branch:  build/wicket-6.29.0
>>>  Release tag: rel/wicket-6.29.0
>>>
>>>
>>> 
>>>
>>>  The signatures for the source release artefacts:
>>>
>>>
>>> Signature for apache-wicket-6.29.0.zip:
>>>
>>>  -BEGIN PGP SIGNATURE-
>>> Version: GnuPG v1
>>>
>>> iQIcBAABAgAGBQJaiFhXAAoJEIePAfqo01bhrh0QAKXGaVgypdlZgaK5b6M3Fxgu
>>> S5LW18OjhEQFQ4yYuz6CE3C/L54u6K4Es6SBhUgAVGuLwaRBdflOfcNA7DRm0Imh
>>> rHcssI6bt7DBxEjIu+XmXEqfgSmZ3P3VQQWGbPtbSMYBXSjhhYFdb8D286U0ec3T
>>> f/vD28ZZmdvRV7NuMKUe54cyMXFebmSfutwQWZqKs/Gx/HOZh4cU2lBbmLvPOuvy
>>> aT1nN7kLhrxROvzOgoyAOo5Dv7HlFrs7eJFQXr1Resz1FTMJrP6sNAQpY3QlcYUa
>>> rORqmxp8H4mXbSVkLk4Kquu6Q6tOcbijUZPZC4Vm5W+xPsBZrsYtJF8S76GZlbq1
>>> tBKlkmwweX/MirHnLwqHaMm43iz7dyf6FS5C9qi0j4GmMKGSh+Lv7Sk1wP3bvyc2
>>> 80loN03gJYCxrse7PcqO65STBjQ8fZlhpHt8yVxwdKJexPJd/aHJHmnoMsJ1FfHj
>>> LxNlHyya34XTpSZBE8Q+Qv47MOLsvGrkbD0876YwjMSQtDX9cUrRC95Hvtvxmqgm
>>> w9GlnnDY8q4Ts9ZZeJSDbanPY3zmAkVrpg+yqlY/pZsFCqh8Wv3L5DUNh+3cUBX+
>>> B7UyK+DJCXOld+81tESZWZhHAN6DXZWrWANrrtkeWO3qtdNLZTaOMAHaaoHPWJEK
>>> xo2Iapi8IzjYJr5jN7nq
>>> =ZuKl
>>> -END PGP SIGNATURE-
>>>
>>> Signature for apache-wicket-6.29.0.tar.gz:
>>>
>>>  -BEGIN PGP SIGNATURE-
>>> Version: GnuPG v1
>>>
>>> iQIcBAABAgAGBQJaiFhXAAoJEIePAfqo01bhPY8P/j6Lwdz9Swa/mHs6EagLTq0s
>>> iArc8ZQzlt8GtnpVr6IIngDcFwvhvsWqCtSpPFmUt74xtZbA6oz6GBhEE0Dmsr9x
>>> 93Ov2aKYRU1pR/H5VkNWqdR67J6QT4amE81T+RzbfQbvcP7YFIIbPOTg4ox3Za61
>>> fu2NlkzB4u9qiPfqad6ylGoVu4mUde+klsnQiHL2dA3DmucChG08I9xjgzqQDIwo
>>> ph2gbieag9RjbgRQEKOYOQcBBS7B8VCNvFxslbchGJEQm6B2QVuQV3+nvyWbjQ0J
>>> u0tpbZA0Wev59dzpLRJDSFcccgBCCII+MP9RZPRuQSUDAyIg/PJ1LFtm/85hxV7C
>>> VqDTMuniLYZT8shTWw4VKQfVGmjso/eRQsNAG7BeMZqxBWQpQQ+6BMoy2piXAavp
>>> RZxO17Ct0V9dPVp7cTTHiet/Iz1oPwkceF5KmaQl1vLhicBbvLF6993ny7iP0Lyo
>>> t+Jh1v4TFf7Daxxgl6q1tO2zDZc94877FXwjZ7b/n37SoRENzTPj+sNhpS3jCZ+E
>>> QxXp/dYU0L6+mVLhJ4XPWAsTljdvnXwHf7S1RBSeEsGb9BM97l6Yh2WpWTgvLiwy
>>> lvdWNkWX1pd6fD1V/XT83FtlQDURPkGN6Bbbfmwh8pSPbzQMn2Q5EXlFTLcTsVhW
>>> QV/yE6KsG5K8AqjY9DdD
>>> =oA/r
>>> -END PGP SIGNATURE-
>>>
>>> 
>>>
>>>  CHANGELOG for 6.29.0:
>>>
>>> ** Bug
>>>
>>>  * [WICKET-6484] - Wicket.Cookie.set does not set 'secure' flag
>>>  * [WICKET-6501] - DefaultPageManagerProvider does not honour
>>> StoreSettings.setAsynchronous(false)
>>>  * [WICKET-6526] - Ajax Buttons do not check for the HTTP method and
>>> thus don't respect Form#onMethodMismatch
>>>  * [WICKET-6530] - Race-condition in session invalidation
>>>
>



-- 
WBR
Maxim aka solomax

Clean-up of wicketstuff modules

2018-02-18 Thread Maxim Solodovnik 
Hello All,

We currently have come commented modules in wicketstuff:

   
   

Maybe it is time for clean-up?


One more question:
We have "coupled" modules:
   serializer-fast
   serializer-fast2

   serializer-kryo
   serializer-kryo2

Maybe it is time to select one of them for master branch?

-- 
WBR
Maxim aka solomax

[ANNOUNCE] WicketStuff 8.0.0-M9 Released

2018-02-18 Thread Maxim Solodovnik 
WicketStuff core 8.0.0-M9 based on Apache Wicket 8.0.0-M9 is released
and soon will be available at Maven Central!

The changelog since 8.0.0-M8 is:

Maxim Solodovnik (14):
  Libraries are updated to the most recent versions
  hazelcast version is updated
  Library versions are updated to most recent ones
  Language files are moved to XML format
  Documentation update
  Libarary versions are updated
  Merge branch 'master' of git://github.com/florianlacreuse/core
into florianlacreuse-master
  Merge branch 'florianlacreuse-master'
  Merge pull request #620 from rene-d-menoto/debug-log-widgets
  White-spaces are fixed
  Fixes issue #621: gson is excluded from compile time
dependencies of closure compiler
  Possibility to specify Google API key via command line is added
  cglib version is reverted to 3.2.5 (ASM 6 seems to be
unsupported), missing serialVersionUID are added
  Wicketstuff 8.0.0-M9 release

Dieter Tremel (8):
  Fixed missing ";" after DataTable javascript.
  Let javadoc link to com.github.openjson.
  Ajax refresh working now by use of OnDomReadyHeaderItem.
  More flexible javascript generation.
  Implement javascript generation for ChartWrapper.
  Merge upstream/master
  Merge branch 'gchart-ajax-fix'
  Implement ajax update of chart inside chart component.

René Dieckmann (5):
  Debug logable widgets. When we log widgets in debug mode, a
NPE is thrown. This happens when no title is provided to widget.
  But it is included in toString on hashCode. Provide a usable
title.
  Debug logable widgets.
  Debug logable widgets.
  Debug logable widgets.
  Debug logable widgets.

Andrea Del Bene (3):
  Fix for unit test as the expected HTML has changed (wicket-event
has been removed)
  Code adapted to WICKET-6503
  Fixed  test for date time. Changed progressbar to comply with
the last 8.x code

Florian Lacreuse (1):
  Added settings support for select2 behavior.


The WicketStuff team

Re: [VOTE] Release Apache Wicket 6.29.0

2018-02-18 Thread Sven Meier 

+1

Many thanks
Sven


Am 17.02.2018 um 23:47 schrieb Tobias Soloschenko:

+1 :-)

kind regards

Tobias


Am 17.02.2018 um 19:28 schrieb Andrea Del Bene :

This is a vote to release Apache Wicket 6.29.0

Please download the source distributions found in our staging area
linked below.

I have included the signatures for both the source archives. This vote
lasts for 72 hours minimum.

[ ] Yes, release Apache Wicket 6.29.0
[ ] No, don't release Apache Wicket 6.29.0, because ...

Distributions, changelog, keys and signatures can be found at:

 https://dist.apache.org/repos/dist/dev/wicket/6.29.0

Staging repository:

https://repository.apache.org/content/repositories/orgapachewicket-1107/

The binaries are available in the above link, as are a staging
repository for Maven. Typically the vote is on the source, but should
you find a problem with one of the binaries, please let me know, I can
re-roll them some way or the other.

Staging git repository data:

 Repository:  g...@github.com:bitstorm/wicket.git
 Branch:  build/wicket-6.29.0
 Release tag: rel/wicket-6.29.0




 The signatures for the source release artefacts:


Signature for apache-wicket-6.29.0.zip:

 -BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAABAgAGBQJaiFhXAAoJEIePAfqo01bhrh0QAKXGaVgypdlZgaK5b6M3Fxgu
S5LW18OjhEQFQ4yYuz6CE3C/L54u6K4Es6SBhUgAVGuLwaRBdflOfcNA7DRm0Imh
rHcssI6bt7DBxEjIu+XmXEqfgSmZ3P3VQQWGbPtbSMYBXSjhhYFdb8D286U0ec3T
f/vD28ZZmdvRV7NuMKUe54cyMXFebmSfutwQWZqKs/Gx/HOZh4cU2lBbmLvPOuvy
aT1nN7kLhrxROvzOgoyAOo5Dv7HlFrs7eJFQXr1Resz1FTMJrP6sNAQpY3QlcYUa
rORqmxp8H4mXbSVkLk4Kquu6Q6tOcbijUZPZC4Vm5W+xPsBZrsYtJF8S76GZlbq1
tBKlkmwweX/MirHnLwqHaMm43iz7dyf6FS5C9qi0j4GmMKGSh+Lv7Sk1wP3bvyc2
80loN03gJYCxrse7PcqO65STBjQ8fZlhpHt8yVxwdKJexPJd/aHJHmnoMsJ1FfHj
LxNlHyya34XTpSZBE8Q+Qv47MOLsvGrkbD0876YwjMSQtDX9cUrRC95Hvtvxmqgm
w9GlnnDY8q4Ts9ZZeJSDbanPY3zmAkVrpg+yqlY/pZsFCqh8Wv3L5DUNh+3cUBX+
B7UyK+DJCXOld+81tESZWZhHAN6DXZWrWANrrtkeWO3qtdNLZTaOMAHaaoHPWJEK
xo2Iapi8IzjYJr5jN7nq
=ZuKl
-END PGP SIGNATURE-

Signature for apache-wicket-6.29.0.tar.gz:

 -BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAABAgAGBQJaiFhXAAoJEIePAfqo01bhPY8P/j6Lwdz9Swa/mHs6EagLTq0s
iArc8ZQzlt8GtnpVr6IIngDcFwvhvsWqCtSpPFmUt74xtZbA6oz6GBhEE0Dmsr9x
93Ov2aKYRU1pR/H5VkNWqdR67J6QT4amE81T+RzbfQbvcP7YFIIbPOTg4ox3Za61
fu2NlkzB4u9qiPfqad6ylGoVu4mUde+klsnQiHL2dA3DmucChG08I9xjgzqQDIwo
ph2gbieag9RjbgRQEKOYOQcBBS7B8VCNvFxslbchGJEQm6B2QVuQV3+nvyWbjQ0J
u0tpbZA0Wev59dzpLRJDSFcccgBCCII+MP9RZPRuQSUDAyIg/PJ1LFtm/85hxV7C
VqDTMuniLYZT8shTWw4VKQfVGmjso/eRQsNAG7BeMZqxBWQpQQ+6BMoy2piXAavp
RZxO17Ct0V9dPVp7cTTHiet/Iz1oPwkceF5KmaQl1vLhicBbvLF6993ny7iP0Lyo
t+Jh1v4TFf7Daxxgl6q1tO2zDZc94877FXwjZ7b/n37SoRENzTPj+sNhpS3jCZ+E
QxXp/dYU0L6+mVLhJ4XPWAsTljdvnXwHf7S1RBSeEsGb9BM97l6Yh2WpWTgvLiwy
lvdWNkWX1pd6fD1V/XT83FtlQDURPkGN6Bbbfmwh8pSPbzQMn2Q5EXlFTLcTsVhW
QV/yE6KsG5K8AqjY9DdD
=oA/r
-END PGP SIGNATURE-



 CHANGELOG for 6.29.0:

** Bug

 * [WICKET-6484] - Wicket.Cookie.set does not set 'secure' flag
 * [WICKET-6501] - DefaultPageManagerProvider does not honour 
StoreSettings.setAsynchronous(false)
 * [WICKET-6526] - Ajax Buttons do not check for the HTTP method and thus 
don't respect Form#onMethodMismatch
 * [WICKET-6530] - Race-condition in session invalidation