Re: Preview of new wicket site

[Sebastien Briquet]

Also,

In the wicket8.x start page [1], the version should be updated (2
occurrences)

In the download page [2]
- the "Supported Versions" section might be updated to "security fixes
only, upgrade to 7.x or 8.x"
- the "Unsupported releases" section might be updated to "discontinued,
upgrade to 7.x or 8.x"

[1] http://dashorst.github.io/wicket-site/start/wicket-8.x.html
[2] http://dashorst.github.io/wicket-site/start/download.html

Re: Preview of new wicket site

[Sebastien Briquet]

Hi Martijn,

I really like it! (I think I already said this but still... :p)

IMHO, I'm not sure it is really worth having subsites. There is already the
download page that redirect to each wicket-X.x page, so it might already be
a good place to put announcement and feature list there.

Thanks & best regards,
Sebastien.

Preview of new wicket site

[Martijn Dashorst]

I've uploaded my work in progress to github.

You can find it here:

http://dashorst.github.io/wicket-site/

In this draft I have opted to make a separate wicket 8 part for our
website under "/8" for the announcement and features list.

Is this something we want to expand on further? To make sub sites for
wicket 7, 8 and beyond?

This way you can have

http://wicket.apache.org/7
http://wicket.apache.org/8
http://wicket.apache.org/9

Martijn

-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

Re: New master branch

[Martin Grigorov]

What is the diff in wicket.conf ?

On Tue, May 22, 2018 at 12:15 PM, Andrea Del Bene 
wrote:

> about the new configuration buildbot said:
>
> " The error(s) below happened while validating the committed changes.
> As a precaution, this commit has not yet been applied to BuildBot.
> Please correct the below and commit your fixes:
>
> Traceback (most recent call last):
>   File "/usr/bin/buildbot", line 4, in 
> runner.run()
>   File "/usr/lib/python2.7/dist-packages/buildbot/scripts/runner.py", line
> 763, in run
> sys.exit(subcommandFunction(subconfig))
>   File "/usr/lib/python2.7/dist-packages/buildbot/scripts/checkconfig.py",
> line 55, in checkconfig
> return _loadConfig(basedir=basedir, configFile=configFile, quiet=quiet)
>   File "/usr/lib/python2.7/dist-packages/buildbot/scripts/checkconfig.py",
> line 26, in _loadConfig
> basedir, configFile)
>   File "/usr/lib/python2.7/dist-packages/buildbot/config.py", line 209, in
> loadConfig
> config.check_single_master()
>   File "/usr/lib/python2.7/dist-packages/buildbot/config.py", line 541, in
> check_single_master
> unscheduled_buildernames = set([b.name for b in self.builders])
> AttributeError: 'NoneType' object has no attribute 'name' "
>
> I don't really know what this should mean.
>
>
>
> On Tue, May 22, 2018 at 10:45 AM, Tobias Soloschenko <
> tobiassolosche...@googlemail.com> wrote:
>
> > Thanks for all the work Andrea!
> >
> > kind regards
> >
> > Tobias
> >
> > > Am 22.05.2018 um 10:13 schrieb Andrea Del Bene :
> > >
> > > A quick recap of what I did yesterday:
> > >
> > > - Wicket 8 has been release but I have to send the official announce
> yet.
> > > - I've created a new branch called wicket-8.x for the development of
> the
> > > 8.x version
> > > - master branch now contains what I did in branch wicket-9.x to make
> all
> > > the code base buildable with Java 9 or later.
> > > - I've changed the buildbot config to include the new branch wicket-8.x
> > and
> > > to use java 9 for master. Unfortunately buildbot seems not to like the
> > new
> > > configuration I did and I'm trying to figure out why.
> > >
> > > That's all for now, I'will send the announce mail ASAP and I will
> publish
> > > an article about Wicket 8 on dzone Java once the announce has been
> sent.
> > >
> > > Andrea.
> >
>

Re: New master branch

[Andrea Del Bene]

about the new configuration buildbot said:

" The error(s) below happened while validating the committed changes.
As a precaution, this commit has not yet been applied to BuildBot.
Please correct the below and commit your fixes:

Traceback (most recent call last):
  File "/usr/bin/buildbot", line 4, in 
runner.run()
  File "/usr/lib/python2.7/dist-packages/buildbot/scripts/runner.py", line
763, in run
sys.exit(subcommandFunction(subconfig))
  File "/usr/lib/python2.7/dist-packages/buildbot/scripts/checkconfig.py",
line 55, in checkconfig
return _loadConfig(basedir=basedir, configFile=configFile, quiet=quiet)
  File "/usr/lib/python2.7/dist-packages/buildbot/scripts/checkconfig.py",
line 26, in _loadConfig
basedir, configFile)
  File "/usr/lib/python2.7/dist-packages/buildbot/config.py", line 209, in
loadConfig
config.check_single_master()
  File "/usr/lib/python2.7/dist-packages/buildbot/config.py", line 541, in
check_single_master
unscheduled_buildernames = set([b.name for b in self.builders])
AttributeError: 'NoneType' object has no attribute 'name' "

I don't really know what this should mean.



On Tue, May 22, 2018 at 10:45 AM, Tobias Soloschenko <
tobiassolosche...@googlemail.com> wrote:

> Thanks for all the work Andrea!
>
> kind regards
>
> Tobias
>
> > Am 22.05.2018 um 10:13 schrieb Andrea Del Bene :
> >
> > A quick recap of what I did yesterday:
> >
> > - Wicket 8 has been release but I have to send the official announce yet.
> > - I've created a new branch called wicket-8.x for the development of the
> > 8.x version
> > - master branch now contains what I did in branch wicket-9.x to make all
> > the code base buildable with Java 9 or later.
> > - I've changed the buildbot config to include the new branch wicket-8.x
> and
> > to use java 9 for master. Unfortunately buildbot seems not to like the
> new
> > configuration I did and I'm trying to figure out why.
> >
> > That's all for now, I'will send the announce mail ASAP and I will publish
> > an article about Wicket 8 on dzone Java once the announce has been sent.
> >
> > Andrea.
>

Re: New master branch

[Tobias Soloschenko]

Thanks for all the work Andrea!

kind regards

Tobias

> Am 22.05.2018 um 10:13 schrieb Andrea Del Bene :
> 
> A quick recap of what I did yesterday:
> 
> - Wicket 8 has been release but I have to send the official announce yet.
> - I've created a new branch called wicket-8.x for the development of the
> 8.x version
> - master branch now contains what I did in branch wicket-9.x to make all
> the code base buildable with Java 9 or later.
> - I've changed the buildbot config to include the new branch wicket-8.x and
> to use java 9 for master. Unfortunately buildbot seems not to like the new
> configuration I did and I'm trying to figure out why.
> 
> That's all for now, I'will send the announce mail ASAP and I will publish
> an article about Wicket 8 on dzone Java once the announce has been sent.
> 
> Andrea.

New master branch

[Andrea Del Bene]

A quick recap of what I did yesterday:

- Wicket 8 has been release but I have to send the official announce yet.
- I've created a new branch called wicket-8.x for the development of the
8.x version
- master branch now contains what I did in branch wicket-9.x to make all
the code base buildable with Java 9 or later.
- I've changed the buildbot config to include the new branch wicket-8.x and
to use java 9 for master. Unfortunately buildbot seems not to like the new
configuration I did and I'm trying to figure out why.

That's all for now, I'will send the announce mail ASAP and I will publish
an article about Wicket 8 on dzone Java once the announce has been sent.

Andrea.

Re: wicketstuff wicket15-tree

[Maxim Solodovnik]

Great, will check and continue the wicketstuff build :)

On Tue, May 22, 2018 at 3:09 PM, Martin Grigorov  wrote:
> Done!
> It is traveling to Maven Central too!
>
> On Tue, May 22, 2018 at 10:58 AM, Maxim Solodovnik 
> wrote:
>
>> Thanks Martin!
>>
>> On Tue, May 22, 2018 at 2:57 PM, Martin Grigorov 
>> wrote:
>> > I see that Wicket 8.0.0 is already at Maven Central, so I will make a
>> > release of wicket1.5-tree !
>> >
>> > On Tue, May 22, 2018 at 5:17 AM, Maxim Solodovnik 
>> > wrote:
>> >
>> >> Hello All,
>> >>
>> >> While preparing wicketstuff release I noticed inmethod-grid depends on
>> >> `wicket15-tree`
>> >> Can someone release `wicket15-tree` ?
>> >>
>> >> On Mon, May 21, 2018 at 5:14 PM, Martin Grigorov 
>> >> wrote:
>> >> > On Mon, May 21, 2018 at 1:12 PM, Sven Meier  wrote:
>> >> >
>> >> >> Hi,
>> >> >>
>> >> >> Martin moved the implementation to wicketstuff, so developers can
>> still
>> >> >> use the old implementation in their project.
>> >> >>
>> >> >> I've fixed some things so it is still working with Wicket 8:
>> >> >>
>> >> >> https://github.com/wicketstuff/wicket1.5-tree/commits/master
>> >> >>
>> >> >> wicket1.5-tree isn't part of wicketstuff-code because - as its name
>> >> >> implies - it is legacy and people should move away from it.
>> >> >>
>> >> >
>> >> > Let's release a new version once Wicket 8.0.0 is at Maven Central.
>> >> > As Sven explained there is no reason to be part of wicketstuff/core
>> and
>> >> to
>> >> > cut releases for it regularly.
>> >> >
>> >> >
>> >> >>
>> >> >> Have fun
>> >> >> Sven
>> >> >>
>> >> >>
>> >> >>
>> >> >> Am 21.05.2018 um 11:55 schrieb Maxim Solodovnik:
>> >> >>
>> >> >>> I can't see recent commits here:
>> >> >>> https://github.com/wicketstuff/core/commits/core-1.5.x 
>> >> >>>
>> >> >>> On Mon, May 21, 2018 at 3:26 PM, Andrea Del Bene <
>> an.delb...@gmail.com
>> >> >
>> >> >>> wrote:
>> >> >>>
>> >>  hi,
>> >> 
>> >>  I've seen Sven lately did some work on this module, but I don't
>> >>  understand
>> >>  why its code is separated from the rest of WicketStuff project. In
>> >> this
>> >>  way
>> >>  it cannot be deployed to maven repository as part of WicketStuff
>> >> project.
>> >>  Is it like this on purpose?
>> >> 
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>
>> >>
>> >>
>> >>
>> >> --
>> >> WBR
>> >> Maxim aka solomax
>> >>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>



-- 
WBR
Maxim aka solomax

Re: wicketstuff wicket15-tree

[Martin Grigorov]

Done!
It is traveling to Maven Central too!

On Tue, May 22, 2018 at 10:58 AM, Maxim Solodovnik 
wrote:

> Thanks Martin!
>
> On Tue, May 22, 2018 at 2:57 PM, Martin Grigorov 
> wrote:
> > I see that Wicket 8.0.0 is already at Maven Central, so I will make a
> > release of wicket1.5-tree !
> >
> > On Tue, May 22, 2018 at 5:17 AM, Maxim Solodovnik 
> > wrote:
> >
> >> Hello All,
> >>
> >> While preparing wicketstuff release I noticed inmethod-grid depends on
> >> `wicket15-tree`
> >> Can someone release `wicket15-tree` ?
> >>
> >> On Mon, May 21, 2018 at 5:14 PM, Martin Grigorov 
> >> wrote:
> >> > On Mon, May 21, 2018 at 1:12 PM, Sven Meier  wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> Martin moved the implementation to wicketstuff, so developers can
> still
> >> >> use the old implementation in their project.
> >> >>
> >> >> I've fixed some things so it is still working with Wicket 8:
> >> >>
> >> >> https://github.com/wicketstuff/wicket1.5-tree/commits/master
> >> >>
> >> >> wicket1.5-tree isn't part of wicketstuff-code because - as its name
> >> >> implies - it is legacy and people should move away from it.
> >> >>
> >> >
> >> > Let's release a new version once Wicket 8.0.0 is at Maven Central.
> >> > As Sven explained there is no reason to be part of wicketstuff/core
> and
> >> to
> >> > cut releases for it regularly.
> >> >
> >> >
> >> >>
> >> >> Have fun
> >> >> Sven
> >> >>
> >> >>
> >> >>
> >> >> Am 21.05.2018 um 11:55 schrieb Maxim Solodovnik:
> >> >>
> >> >>> I can't see recent commits here:
> >> >>> https://github.com/wicketstuff/core/commits/core-1.5.x 
> >> >>>
> >> >>> On Mon, May 21, 2018 at 3:26 PM, Andrea Del Bene <
> an.delb...@gmail.com
> >> >
> >> >>> wrote:
> >> >>>
> >>  hi,
> >> 
> >>  I've seen Sven lately did some work on this module, but I don't
> >>  understand
> >>  why its code is separated from the rest of WicketStuff project. In
> >> this
> >>  way
> >>  it cannot be deployed to maven repository as part of WicketStuff
> >> project.
> >>  Is it like this on purpose?
> >> 
> >> >>>
> >> >>>
> >> >>>
> >> >>
> >>
> >>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
> >>
>
>
>
> --
> WBR
> Maxim aka solomax
>

Re: buildbot failure in on wicket-master

[Andrea Del Bene]

I think there's a problem with buildbot. I will open an issue for the INFRA
team. Thank you for removing references to datetime module. I also agree
that specific websocket implementation should be removed from master.

Andrea.

On Tue, May 22, 2018 at 9:59 AM, Emond Papegaaij  wrote:

> This error still persists and I have no idea why. Locally the build is
> fine.
>
> I've removed some more references to the old datetime module, including
> the
> NOTICE about the bsd license. The userguide still mentions the tomcat and
> jetty9 modules for native-websockets. I think that part should be removed,
> right? AFAIK we now only support SSR356 compliant containers.
>
> Best regards,
> Emond
>
> On vrijdag 18 mei 2018 13:35:42 CEST Emond Papegaaij wrote:
> > I highly doubt my commit caused this failure:
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-compiler-plugin: 3.6.2:compile
> > (default-compile) on project wicket-util: Fatal error compiling: Error
> > creating file with javac arguments: No such file or directory -> [Help 1]
> >
> > Emond
> >
> > On vrijdag 18 mei 2018 13:23:31 CEST build...@apache.org wrote:
> > > The Buildbot has detected a new failure on builder wicket-master while
> > > building wicket. Full details are available at:
> > > https://ci.apache.org/builders/wicket-master/builds/933
> > >
> > > Buildbot URL: https://ci.apache.org/
> > >
> > > Buildslave for this Build: bb_slave1_ubuntu
> > >
> > > Build Reason: The SingleBranchScheduler scheduler named
> > > 'on-wicket-master-commit' triggered this build Build Source Stamp:
> [branch
> > > master] 024153133f79ef0bdd4ddbf0605c092fc9977e44 Blamelist: Emond
> > > Papegaaij
> > > 
> > >
> > > BUILD FAILED: failed compile
> > >
> > > Sincerely,
> > >
> > >  -The Buildbot
>
>
>
>
>

Re: buildbot failure in on wicket-master

[Emond Papegaaij]

This error still persists and I have no idea why. Locally the build is fine.

I've removed some more references to the old datetime module, including the 
NOTICE about the bsd license. The userguide still mentions the tomcat and 
jetty9 modules for native-websockets. I think that part should be removed, 
right? AFAIK we now only support SSR356 compliant containers.

Best regards,
Emond

On vrijdag 18 mei 2018 13:35:42 CEST Emond Papegaaij wrote:
> I highly doubt my commit caused this failure:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin: 3.6.2:compile
> (default-compile) on project wicket-util: Fatal error compiling: Error
> creating file with javac arguments: No such file or directory -> [Help 1]
> 
> Emond
> 
> On vrijdag 18 mei 2018 13:23:31 CEST build...@apache.org wrote:
> > The Buildbot has detected a new failure on builder wicket-master while
> > building wicket. Full details are available at:
> > https://ci.apache.org/builders/wicket-master/builds/933
> > 
> > Buildbot URL: https://ci.apache.org/
> > 
> > Buildslave for this Build: bb_slave1_ubuntu
> > 
> > Build Reason: The SingleBranchScheduler scheduler named
> > 'on-wicket-master-commit' triggered this build Build Source Stamp: [branch
> > master] 024153133f79ef0bdd4ddbf0605c092fc9977e44 Blamelist: Emond
> > Papegaaij
> > 
> > 
> > BUILD FAILED: failed compile
> > 
> > Sincerely,
> > 
> >  -The Buildbot

Re: wicketstuff wicket15-tree

[Maxim Solodovnik]

Thanks Martin!

On Tue, May 22, 2018 at 2:57 PM, Martin Grigorov  wrote:
> I see that Wicket 8.0.0 is already at Maven Central, so I will make a
> release of wicket1.5-tree !
>
> On Tue, May 22, 2018 at 5:17 AM, Maxim Solodovnik 
> wrote:
>
>> Hello All,
>>
>> While preparing wicketstuff release I noticed inmethod-grid depends on
>> `wicket15-tree`
>> Can someone release `wicket15-tree` ?
>>
>> On Mon, May 21, 2018 at 5:14 PM, Martin Grigorov 
>> wrote:
>> > On Mon, May 21, 2018 at 1:12 PM, Sven Meier  wrote:
>> >
>> >> Hi,
>> >>
>> >> Martin moved the implementation to wicketstuff, so developers can still
>> >> use the old implementation in their project.
>> >>
>> >> I've fixed some things so it is still working with Wicket 8:
>> >>
>> >> https://github.com/wicketstuff/wicket1.5-tree/commits/master
>> >>
>> >> wicket1.5-tree isn't part of wicketstuff-code because - as its name
>> >> implies - it is legacy and people should move away from it.
>> >>
>> >
>> > Let's release a new version once Wicket 8.0.0 is at Maven Central.
>> > As Sven explained there is no reason to be part of wicketstuff/core and
>> to
>> > cut releases for it regularly.
>> >
>> >
>> >>
>> >> Have fun
>> >> Sven
>> >>
>> >>
>> >>
>> >> Am 21.05.2018 um 11:55 schrieb Maxim Solodovnik:
>> >>
>> >>> I can't see recent commits here:
>> >>> https://github.com/wicketstuff/core/commits/core-1.5.x 
>> >>>
>> >>> On Mon, May 21, 2018 at 3:26 PM, Andrea Del Bene > >
>> >>> wrote:
>> >>>
>>  hi,
>> 
>>  I've seen Sven lately did some work on this module, but I don't
>>  understand
>>  why its code is separated from the rest of WicketStuff project. In
>> this
>>  way
>>  it cannot be deployed to maven repository as part of WicketStuff
>> project.
>>  Is it like this on purpose?
>> 
>> >>>
>> >>>
>> >>>
>> >>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>



-- 
WBR
Maxim aka solomax

Re: wicketstuff wicket15-tree

[Martin Grigorov]

I see that Wicket 8.0.0 is already at Maven Central, so I will make a
release of wicket1.5-tree !

On Tue, May 22, 2018 at 5:17 AM, Maxim Solodovnik 
wrote:

> Hello All,
>
> While preparing wicketstuff release I noticed inmethod-grid depends on
> `wicket15-tree`
> Can someone release `wicket15-tree` ?
>
> On Mon, May 21, 2018 at 5:14 PM, Martin Grigorov 
> wrote:
> > On Mon, May 21, 2018 at 1:12 PM, Sven Meier  wrote:
> >
> >> Hi,
> >>
> >> Martin moved the implementation to wicketstuff, so developers can still
> >> use the old implementation in their project.
> >>
> >> I've fixed some things so it is still working with Wicket 8:
> >>
> >> https://github.com/wicketstuff/wicket1.5-tree/commits/master
> >>
> >> wicket1.5-tree isn't part of wicketstuff-code because - as its name
> >> implies - it is legacy and people should move away from it.
> >>
> >
> > Let's release a new version once Wicket 8.0.0 is at Maven Central.
> > As Sven explained there is no reason to be part of wicketstuff/core and
> to
> > cut releases for it regularly.
> >
> >
> >>
> >> Have fun
> >> Sven
> >>
> >>
> >>
> >> Am 21.05.2018 um 11:55 schrieb Maxim Solodovnik:
> >>
> >>> I can't see recent commits here:
> >>> https://github.com/wicketstuff/core/commits/core-1.5.x 
> >>>
> >>> On Mon, May 21, 2018 at 3:26 PM, Andrea Del Bene  >
> >>> wrote:
> >>>
>  hi,
> 
>  I've seen Sven lately did some work on this module, but I don't
>  understand
>  why its code is separated from the rest of WicketStuff project. In
> this
>  way
>  it cannot be deployed to maven repository as part of WicketStuff
> project.
>  Is it like this on purpose?
> 
> >>>
> >>>
> >>>
> >>
>
>
>
> --
> WBR
> Maxim aka solomax
>