Re: FYI: fix for WICKET-6078

2019-10-26 Thread Martin Grigorov
Thank you, Andrea! On Sat, Oct 26, 2019, 10:32 Andrea Del Bene wrote: > Hi, > as you might have noted, I did a fix for WICKET-6078 as the new code > checked request method (GET and POST) in a case-sensitive way, breaking > normal form submission. > > Cheers. > -- > Andrea Del Bene. > Apache

Re: FYI

2019-10-08 Thread Maxim Solodovnik
Great news :) On Tue, 8 Oct 2019 at 14:41, Andrea Del Bene wrote: > Great! Thank you Martin! > > On Tue, Oct 8, 2019 at 5:10 AM Martin Grigorov > wrote: > > > On Mon, Oct 7, 2019, 16:33 Martin Grigorov wrote: > > > > > I've found a workaround: execute `mvn clean javadoc:aggregate` as a > > >

Re: FYI

2019-10-08 Thread Andrea Del Bene
Great! Thank you Martin! On Tue, Oct 8, 2019 at 5:10 AM Martin Grigorov wrote: > On Mon, Oct 7, 2019, 16:33 Martin Grigorov wrote: > > > I've found a workaround: execute `mvn clean javadoc:aggregate` as a > > separate step after `mvn deploy` > > > > In r1051190 at > > >

Re: FYI

2019-10-07 Thread Martin Grigorov
On Mon, Oct 7, 2019, 16:33 Martin Grigorov wrote: > I've found a workaround: execute `mvn clean javadoc:aggregate` as a > separate step after `mvn deploy` > > In r1051190 at > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects > I've split the step into

Re: FYI

2019-10-07 Thread Martin Grigorov
I've found a workaround: execute `mvn clean javadoc:aggregate` as a separate step after `mvn deploy` In r1051190 at https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects I've split the step into two steps. But now the build failed due to some NPM bug:

Re: FYI

2019-07-23 Thread Andrea Del Bene
I think I might found a bug with maven-javadoc-plugin: https://issues.apache.org/jira/browse/MJAVADOC-618 On Mon, Jul 22, 2019 at 6:36 PM Andrea Del Bene wrote: > After the fix applied by Martin we have another more strange message error > during javadoc:aggregate. I couldn't find any possible

Re: FYI

2019-07-22 Thread Andrea Del Bene
After the fix applied by Martin we have another more strange message error during javadoc:aggregate. I couldn't find any possible cause yet: [INFO] --- maven-javadoc-plugin:3.1.1:aggregate (default-cli) @ wicket-parent --- [INFO] Toolchain in maven-javadoc-plugin:

Re: FYI

2019-07-13 Thread Martin Grigorov
Hi, I've committed a change to Wicket's Buildbot config that adds JAVA_HOME for the Java 11, 13 and 14 builds. Hopefully this will fix the problem! On Fri, Jul 12, 2019 at 5:01 PM Andrea Del Bene wrote: > Problem with javadoc-maven-plugin 3.1.x and CI: > >

Re: FYI

2019-07-12 Thread Maxim Solodovnik
Yes, java11 is the default one The weird thing: `javadoc-no-fork` goal works as expected while `jar` goal produces error :( On Fri, 12 Jul 2019 at 21:44, Andrea Del Bene wrote: > > Have you got Java 11 as default JDK? If I try to run javadoc:aggregate with > Java 8 as default JDK I get similar

Re: FYI

2019-07-12 Thread Andrew Kondratev
I also had strange issues with maven 3.6.0, seems like toolchains do not work properly and I have to switch java home, or to run the maven with appropriate java version by hand to make it work. On Sat, 13 Jul 2019 at 02:44, Andrea Del Bene wrote: > Have you got Java 11 as default JDK? If I try

Re: FYI: additional commit for WICKET-6662

2019-05-18 Thread Maxim Solodovnik
Thanks for catching this one :) On Sun, 19 May 2019 at 01:04, Andrea Del Bene wrote: > Hi, > > today I've noted that using version 9.0.0-M2-SNAPSHOT led to a constant > usage of CPU from task ModificationWatcher. I've spotted a silly line of > code I wrote for WICKET-6662. Since no one opened

Re: FYI: updated Jetty version in master branch

2017-10-13 Thread Andrea Del Bene
 thank you! I've noticed the problem when I tried to create a Wicket quickstart for 8 SNAPSHOT and I couldn't run it with Jetty On Fri, Oct 13, 2017 at 5:58 PM, Maxim Solodovnik wrote: > Did it couple days ago :)) >

Re: FYI: updated Jetty version in master branch

2017-10-13 Thread Maxim Solodovnik
Did it couple days ago :)) https://github.com/wicketstuff/core/blob/master/pom.xml#L232 On Fri, Oct 13, 2017 at 10:38 PM, Andrea Del Bene wrote: > For the 'very last' I mean 9.4.7 :-) > > On Fri, Oct 13, 2017 at 5:30 PM, Maxim Solodovnik > wrote: > >

Re: FYI: updated Jetty version in master branch

2017-10-13 Thread Andrea Del Bene
For the 'very last' I mean 9.4.7 :-) On Fri, Oct 13, 2017 at 5:30 PM, Maxim Solodovnik wrote: > Good to know :) > Wicketstuff is already updated :) > > On Fri, Oct 13, 2017 at 10:29 PM, Andrea Del Bene > wrote: > > > The 2.9.x version of Log4j 2

Re: FYI: updated Jetty version in master branch

2017-10-13 Thread Maxim Solodovnik
Good to know :) Wicketstuff is already updated :) On Fri, Oct 13, 2017 at 10:29 PM, Andrea Del Bene wrote: > The 2.9.x version of Log4j 2 triggered an error on jetty due to this issue > (I guess): https://github.com/eclipse/jetty.project/issues/1797 > > Updating Jetty to