Re: [DISSCUSSION] can we drop wicketstuff-pushd*

[Tobias Soloschenko]

+1 to remove 

kind regards

Tobias

> Am 01.04.2022 um 20:12 schrieb Ernesto Reinaldo Barreiro :
> 
> +1 to remove
> 
>> On Fri, Apr 1, 2022 at 12:51 AM Martin Grigorov 
>> wrote:
>> 
>> +1 to drop it!
>> 
>> If someone uses it then (s)he can use the old releases and send a PR later
>> to revive it!
>> 
>> On Fri, Apr 1, 2022 at 5:20 AM Maxim Solodovnik 
>> wrote:
>> 
>>> Hello All,
>>> 
>>> AFAIK these days push is available out-of-the-box via websockets
>>> Do we need all these components?
>>> 
>>> If we do need them can anyone take a look at `push-cometd`?
>>> cometd-java-client/cometd-java-server seems to be changed a lot
>>> and the version we are currently using reported to be vulnerable:
>>> 
>>> 
>> https://sbom.lift.sonatype.com/report/T1-a0368c8f29fdaa555824-83a6cd82eac598-1648715554-9fa6855eebd24639bf9f6239d6d95ddf
>>> 
>>> WDYT? :))
>>> 
>>> --
>>> Best regards,
>>> Maxim
>>> 
>> 
> 
> 
> -- 
> Regards - Ernesto Reinaldo Barreiro

[VOTE] Release Apache Wicket 9.9.1

[Andrea Del Bene]

This is a vote to release Apache Wicket 9.9.1

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 9.9.1
[ ] No, don't release Apache Wicket 9.9.1, because ...

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

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

Staging repository:

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

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-9.9.1
    Release tag: rel/wicket-9.9.1




    CHANGELOG for 9.9.1:

** Bug

    * [WICKET-6966] - IndexOutOfBounds in InSessionPageStore

** Improvement

    * [WICKET-6963] - Use singletons for PanelMarkupSourcingStrategy

Jenkins build is back to normal : Wicket » Wicket 9.x (Draft) #104

[Apache Jenkins Server]

See 

Jenkins build is back to normal : Wicket » Wicket 9.x (Draft) » Wicket Request #104

[Apache Jenkins Server]

See 

Re: Hotfix 9.9.1

[Andrea Del Bene]

That's a nice idea!

On 01/04/22 20:18, Martin Grigorov wrote:

Please update Spring!

On Fri, Apr 1, 2022, 19:55 Thomas Heigl  wrote:


+1. Thank you Andrea!

On Fri, Apr 1, 2022 at 6:22 PM Ernesto Reinaldo Barreiro <
reier...@gmail.com>
wrote:


+1. Many thanks for taking care of releases!

On Fri, Apr 1, 2022 at 8:22 AM Andrea Del Bene 
wrote:


I will start to rollout this version in few hours. If I have to wait

for

some last-minute change let me know.

--
Andrea Del Bene.
Apache Wicket committer.



--
Regards - Ernesto Reinaldo Barreiro

Re: Hotfix 9.9.1

[Martin Grigorov]

Please update Spring!

On Fri, Apr 1, 2022, 19:55 Thomas Heigl  wrote:

> +1. Thank you Andrea!
>
> On Fri, Apr 1, 2022 at 6:22 PM Ernesto Reinaldo Barreiro <
> reier...@gmail.com>
> wrote:
>
> > +1. Many thanks for taking care of releases!
> >
> > On Fri, Apr 1, 2022 at 8:22 AM Andrea Del Bene 
> > wrote:
> >
> > > I will start to rollout this version in few hours. If I have to wait
> for
> > > some last-minute change let me know.
> > >
> > > --
> > > Andrea Del Bene.
> > > Apache Wicket committer.
> > >
> >
> >
> > --
> > Regards - Ernesto Reinaldo Barreiro
> >
>

Re: [DISSCUSSION] can we drop wicketstuff-pushd*

[Ernesto Reinaldo Barreiro]

+1 to remove

On Fri, Apr 1, 2022 at 12:51 AM Martin Grigorov 
wrote:

> +1 to drop it!
>
> If someone uses it then (s)he can use the old releases and send a PR later
> to revive it!
>
> On Fri, Apr 1, 2022 at 5:20 AM Maxim Solodovnik 
> wrote:
>
> > Hello All,
> >
> > AFAIK these days push is available out-of-the-box via websockets
> > Do we need all these components?
> >
> > If we do need them can anyone take a look at `push-cometd`?
> > cometd-java-client/cometd-java-server seems to be changed a lot
> > and the version we are currently using reported to be vulnerable:
> >
> >
> https://sbom.lift.sonatype.com/report/T1-a0368c8f29fdaa555824-83a6cd82eac598-1648715554-9fa6855eebd24639bf9f6239d6d95ddf
> >
> > WDYT? :))
> >
> > --
> > Best regards,
> > Maxim
> >
>


-- 
Regards - Ernesto Reinaldo Barreiro

Re: Hotfix 9.9.1

[Thomas Heigl]

+1. Thank you Andrea!

On Fri, Apr 1, 2022 at 6:22 PM Ernesto Reinaldo Barreiro 
wrote:

> +1. Many thanks for taking care of releases!
>
> On Fri, Apr 1, 2022 at 8:22 AM Andrea Del Bene 
> wrote:
>
> > I will start to rollout this version in few hours. If I have to wait for
> > some last-minute change let me know.
> >
> > --
> > Andrea Del Bene.
> > Apache Wicket committer.
> >
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Re: Hotfix 9.9.1

[Ernesto Reinaldo Barreiro]

+1. Many thanks for taking care of releases!

On Fri, Apr 1, 2022 at 8:22 AM Andrea Del Bene  wrote:

> I will start to rollout this version in few hours. If I have to wait for
> some last-minute change let me know.
>
> --
> Andrea Del Bene.
> Apache Wicket committer.
>


-- 
Regards - Ernesto Reinaldo Barreiro

Hotfix 9.9.1

[Andrea Del Bene]

I will start to rollout this version in few hours. If I have to wait for
some last-minute change let me know.

-- 
Andrea Del Bene.
Apache Wicket committer.

Re: wicket 9.9.0 - MarkupExceptions after upgrade - any idea why I get this?

[Korbinian Bachl]

PS: with "rendering" I mean the kind of page composition from changed HTML 
source, not the rerendering in terms of changed on page content due to Java 
code... 

I think I have expressed myself not clear and good here. Sorry :(

- Ursprüngliche Mail -
> Von: "Korbinian Bachl" 
> An: "dev" 
> Gesendet: Freitag, 1. April 2022 12:27:19
> Betreff: Re: wicket 9.9.0 - MarkupExceptions after upgrade - any idea why I 
> get this?

> Hi Thomas,
> 
> it is indeed WICKET-6963. The reason from my understanding is the way we 
> "treat"
> pages & components here. I tried to make a small wicket quickstart to show the
> problem but I wasn't able to reproduce the problem. I then tried to reproduce
> it with our cms base (https://github.com/brix-cms/brix-cms) and then it 
> happens
> on rare occasions (even DEMO works... one just must hammer it with jmeter or
> sth like that - much concurrence needed).
> 
> See, we use brix cms and this has custom tags tiles etc. as well as a custom
> page that renders the content:
> https://github.com/brix-cms/brix-cms/blob/master/brix-core/src/main/java/org/brixcms/web/nodepage/BrixNodeWebPage.java
> https://github.com/brix-cms/brix-cms/blob/master/brix-core/src/main/java/org/brixcms/markup/web/BrixMarkupNodeWebPage.java
> 
> What brix does is, basically spoken, it takes a node from a JCR and 
> understands
> this as a kind of receipe to create a wicket page, decorate it with tiles
> (special kind of wicket-panels in brix terms), header items etc. Thus 
> rendering
> and rerendering pages often... very often (contrary to regular wicket apps...
> these usually only render once as HTML-sources stays fixed - see
> https://github.com/brix-cms/brix-cms/wiki/Templating ).
> When now many concurrenct requests come in and at the same time it rerenders
> something then the final static with the "wrong" flag gets leaked into the
> wrong rendering and therefore creates this 503 errors.
> 
> AFAIK a "static final" even allows java to reuse this item in any other 
> threads
> without any limitations as only the reference is thread safe but not the
> contents - am I right here?
> 
> 
> Anyway, I can asure you that I made a nearly similar mistake by myself not 
> long
> ago when I thought I optimize some fields to final static and only production
> errors let me know :X
> 
> 
> Do you know when a 9.9.1 will be out?
> 
> Best,
> 
> KB
> 
> 
> 
> 
> 
> - Ursprüngliche Mail -
>> Von: "Thomas Heigl"
>> An: "dev" 
>> Gesendet: Donnerstag, 31. März 2022 11:35:45
>> Betreff: Re: wicket 9.9.0 - MarkupExceptions after upgrade - any idea why I 
>> get
>> this?
> 
>> It's just a single commit. I have reverted it for both 9.x and master.
>> 
>> Best,
>> 
>> Thomas
>> 
>> On Thu, Mar 31, 2022 at 11:06 AM Andrea Del Bene
>> wrote:
>> 
>>> On Thu, Mar 31, 2022 at 10:33 AM Thomas Heigl  wrote:
>>>
>>> > Ok I had a closer look at AssociatedMarkupSourcingStrategy and the code
>>> > related to this flag is quite convoluted and full of TODOs and WHY
>>> > comments. I think I will have to do another take on this and replace the
>>> > field with a parameter, but this will take some time.
>>> >
>>> > I would suggest we revert WICKET-6963 for now and release 9.9.1.
>>> >
>>> > Sorry for that! I was confident that my change was good, because it
>>> worked
>>> > without problems in our production environment.
>>> >
>>> >
>>>  Don't worry, these things happened :-) . Could you take care of reverting
>>> WICKET-6963 on git? Or if it's just a commit I can do it by myself.
>>>
>>>
>>> > Thomas
>>> >
>>> > On Thu, Mar 31, 2022 at 10:18 AM Thomas Heigl
>>> wrote:
>>> >
>>> > > Although the JavaDoc states that this should be possible:
>>> > >
>>> > >   // reset for each render in case the strategy is re-used
>>> > > noMoreWicketHeadTagsAllowed = false;
>>> > >
>>> > > It would be great if we had a failing test-case for this. In my
>>> > production
>>> > > environment with about 5000 panels, there are none of these issues.
>>> > >
>>> > > Thomas
>>> > >
>>> > > On Thu, Mar 31, 2022 at 10:14 AM Thomas Heigl
>>> > wrote:
>>> > >
>>> > >> I think we will have to revert WICKET-6963.
>>> > >>
>>> > >> I somehow overlooked the non-final field noMoreWicketHeadTagsAllowed
>>> > >> in AssociatedMarkupSourcingStrategy. If this flag gets set, the
>>> > singleton
>>> > >> strategy doesn't work.
>>> > >>
>>> > >> Thomas
>>> > >>
>>> > >> On Thu, Mar 31, 2022 at 10:11 AM Thomas Heigl
>>> > >> wrote:
>>> > >>
>>> > >>> This is probably caused by my change in
>>> > >>> https://issues.apache.org/jira/browse/WICKET-6963
>>> > >>>
>>> > >>> I have been using this code in production for a couple of weeks now
>>> > >>> without issues, but there seem to be cases where the singleton
>>> strategy
>>> > >>> doesn't work.
>>> > >>>
>>> > >>> Can you reproduce this issue in a test-case?
>>> > >>>
>>> > >>> Thomas
>>> > >>>
>>> > >>> On Thu, Mar 31, 2022 at 10:06 AM Maxim Solodovnik <
>>> > solomax...@gmail.com>
>>> > >>> wrote:
>>> > >>>
>>> > >>

Re: wicket 9.9.0 - MarkupExceptions after upgrade - any idea why I get this?

[Korbinian Bachl]

Hi Thomas,

it is indeed WICKET-6963. The reason from my understanding is the way we 
"treat" pages & components here. I tried to make a small wicket quickstart to 
show the problem but I wasn't able to reproduce the problem. I then tried to 
reproduce it with our cms base (https://github.com/brix-cms/brix-cms) and then 
it happens on rare occasions (even DEMO works... one just must hammer it with 
jmeter or sth like that - much concurrence needed).

See, we use brix cms and this has custom tags tiles etc. as well as a custom 
page that renders the content:
https://github.com/brix-cms/brix-cms/blob/master/brix-core/src/main/java/org/brixcms/web/nodepage/BrixNodeWebPage.java
 
https://github.com/brix-cms/brix-cms/blob/master/brix-core/src/main/java/org/brixcms/markup/web/BrixMarkupNodeWebPage.java

What brix does is, basically spoken, it takes a node from a JCR and understands 
this as a kind of receipe to create a wicket page, decorate it with tiles 
(special kind of wicket-panels in brix terms), header items etc. Thus rendering 
and rerendering pages often... very often (contrary to regular wicket apps... 
these usually only render once as HTML-sources stays fixed - see 
https://github.com/brix-cms/brix-cms/wiki/Templating ). 
When now many concurrenct requests come in and at the same time it rerenders 
something then the final static with the "wrong" flag gets leaked into the 
wrong rendering and therefore creates this 503 errors.

AFAIK a "static final" even allows java to reuse this item in any other threads 
without any limitations as only the reference is thread safe but not the 
contents - am I right here?


Anyway, I can asure you that I made a nearly similar mistake by myself not long 
ago when I thought I optimize some fields to final static and only production 
errors let me know :X


Do you know when a 9.9.1 will be out?

Best,

KB





- Ursprüngliche Mail -
> Von: "Thomas Heigl" 
> An: "dev" 
> Gesendet: Donnerstag, 31. März 2022 11:35:45
> Betreff: Re: wicket 9.9.0 - MarkupExceptions after upgrade - any idea why I 
> get this?

> It's just a single commit. I have reverted it for both 9.x and master.
> 
> Best,
> 
> Thomas
> 
> On Thu, Mar 31, 2022 at 11:06 AM Andrea Del Bene 
> wrote:
> 
>> On Thu, Mar 31, 2022 at 10:33 AM Thomas Heigl  wrote:
>>
>> > Ok I had a closer look at AssociatedMarkupSourcingStrategy and the code
>> > related to this flag is quite convoluted and full of TODOs and WHY
>> > comments. I think I will have to do another take on this and replace the
>> > field with a parameter, but this will take some time.
>> >
>> > I would suggest we revert WICKET-6963 for now and release 9.9.1.
>> >
>> > Sorry for that! I was confident that my change was good, because it
>> worked
>> > without problems in our production environment.
>> >
>> >
>>  Don't worry, these things happened :-) . Could you take care of reverting
>> WICKET-6963 on git? Or if it's just a commit I can do it by myself.
>>
>>
>> > Thomas
>> >
>> > On Thu, Mar 31, 2022 at 10:18 AM Thomas Heigl 
>> wrote:
>> >
>> > > Although the JavaDoc states that this should be possible:
>> > >
>> > >   // reset for each render in case the strategy is re-used
>> > > noMoreWicketHeadTagsAllowed = false;
>> > >
>> > > It would be great if we had a failing test-case for this. In my
>> > production
>> > > environment with about 5000 panels, there are none of these issues.
>> > >
>> > > Thomas
>> > >
>> > > On Thu, Mar 31, 2022 at 10:14 AM Thomas Heigl 
>> > wrote:
>> > >
>> > >> I think we will have to revert WICKET-6963.
>> > >>
>> > >> I somehow overlooked the non-final field noMoreWicketHeadTagsAllowed
>> > >> in AssociatedMarkupSourcingStrategy. If this flag gets set, the
>> > singleton
>> > >> strategy doesn't work.
>> > >>
>> > >> Thomas
>> > >>
>> > >> On Thu, Mar 31, 2022 at 10:11 AM Thomas Heigl 
>> > >> wrote:
>> > >>
>> > >>> This is probably caused by my change in
>> > >>> https://issues.apache.org/jira/browse/WICKET-6963
>> > >>>
>> > >>> I have been using this code in production for a couple of weeks now
>> > >>> without issues, but there seem to be cases where the singleton
>> strategy
>> > >>> doesn't work.
>> > >>>
>> > >>> Can you reproduce this issue in a test-case?
>> > >>>
>> > >>> Thomas
>> > >>>
>> > >>> On Thu, Mar 31, 2022 at 10:06 AM Maxim Solodovnik <
>> > solomax...@gmail.com>
>> > >>> wrote:
>> > >>>
>> >  " tags are only allowed before , ,
>> >  
>> >  etc. tag"
>> >  sounds reasonable :)
>> > 
>> >  On Thu, 31 Mar 2022 at 14:56, Korbinian Bachl <
>> >  korbinian.ba...@whiskyworld.de> wrote:
>> > 
>> >  > Hi,
>> >  >
>> >  > I deployed our app on 9.9.0 this morning and after initializing a
>> >  crawl of
>> >  > the page I ended up getting a low quote of 503s.
>> >  >
>> >  > The 503s are always the same:
>> >  > 2022-03-31 09:35:05,031 ERROR
>> >  [org.apache.wicket.DefaultExceptionMapper]
>> >  > Unexpected error occurred
>> >

Jenkins build is back to normal : Wicket » wicket-9.x #105

[Apache Jenkins Server]

See 

Build failed in Jenkins: Wicket » Wicket 9.x (Draft) #103

[Apache Jenkins Server]

See 


Changes:

[Sven Meier] WICKET-6966 do not record session size by default


--
[...truncated 100.21 KB...]
[INFO] 
[INFO] 
[INFO] --- maven-source-plugin:3.2.1:test-jar (attach-sources) @ wicket-request 
---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:3.9.1:attach-descriptor (attach-descriptor) @ 
wicket-request ---
[INFO] Skipping because packaging 'bundle' is not pom.
[INFO] 
[INFO] --- maven-javadoc-plugin:3.3.0:jar (attach-javadocs) @ wicket-request ---
[INFO] No previous run data found, generating javadoc.
[INFO] 
100 warnings
[WARNING] Javadoc Warnings
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] javadoc: warning - The code being documented uses packages in the 
unnamed module, but the packages defined in 
https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.
[WARNING] jav

Build failed in Jenkins: Wicket » Wicket 9.x (Draft) » Wicket Request #103

[Apache Jenkins Server]

See 


Changes:


--
[INFO] 
[INFO] --< org.apache.wicket:wicket-request >--
[INFO] Building Wicket Request 9.10.0-SNAPSHOT   [3/32]
[INFO] ---[ bundle ]---
[INFO] 
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ wicket-request ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven) @ wicket-request 
---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
wicket-request ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.7.0:process (default) @ 
wicket-request ---
[INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
[INFO] Copying 3 resources from 1 bundle.
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.7.0:process 
(process-resource-bundles) @ wicket-request ---
[INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
[INFO] Copying 3 resources from 1 bundle.
[INFO] 
[INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @ 
wicket-request ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ 
wicket-request ---
[WARNING] 
***
[WARNING] * Required filename-based automodules detected: 
[commons-fileupload-1.4.jar, javax.servlet-api-3.1.0.jar]. Please don't publish 
this project to a public artifact repository! *
[WARNING] 
***
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 46 source files to 

[INFO] 
[INFO] --- maven-bundle-plugin:5.1.3:manifest (bundle-manifest) @ 
wicket-request ---
[WARNING] Manifest org.apache.wicket:wicket-request:bundle:9.10.0-SNAPSHOT : 
Unused Import-Package instructions: [org.junit.jupiter*] 
[INFO] 
[INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources) @ 
wicket-request ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ 
wicket-request ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 10 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @ wicket-request 
---
[INFO] 
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.apache.wicket.request.http.handler.RedirectRequestHandlerTest
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.466 s 
- in org.apache.wicket.request.http.handler.RedirectRequestHandlerTest
[INFO] Running org.apache.wicket.request.mapper.parameter.PageParametersTest
SLF4J: No SLF4J providers were found.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#noProviders for further details.
[INFO] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.115 s 
- in org.apache.wicket.request.mapper.parameter.PageParametersTest
[INFO] Running 
org.apache.wicket.request.mapper.parameter.UrlPathPageParametersEncoderTest
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.03 s - 
in org.apache.wicket.request.mapper.parameter.UrlPathPageParametersEncoderTest
[INFO] Running 
org.apache.wicket.request.mapper.parameter.PageParametersEncoderTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 s 
- in org.apache.wicket.request.mapper.parameter.PageParametersEncoderTest
[INFO] Running org.apache.wicket.request.mapper.CompoundRequestMapperTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Sk