buildbot failure in on wicket-branch-7.x

The Buildbot has detected a new failure on builder wicket-branch-7.x while building wicket. Full details are available at: https://ci.apache.org/builders/wicket-branch-7.x/builds/461 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The SingleBra

[jira] [Resolved] (WICKET-6506) Performance issue when large component isn't visible

[ https://issues.apache.org/jira/browse/WICKET-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij resolved WICKET-6506. - Resolution: Fixed Fix Version/s: 7.10.0 8.0.0 I've pushed the f

[jira] [Commented] (WICKET-6506) Performance issue when large component isn't visible

[ https://issues.apache.org/jira/browse/WICKET-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296770#comment-16296770 ] ASF subversion and git services commented on WICKET-6506: - Commit

[jira] [Commented] (WICKET-6506) Performance issue when large component isn't visible

[ https://issues.apache.org/jira/browse/WICKET-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296769#comment-16296769 ] ASF subversion and git services commented on WICKET-6506: - Commit

wicket git commit: WICKET-6506: Fix performance regression

Repository: wicket Updated Branches: refs/heads/wicket-7.x dd5449e2b -> a352fe2be WICKET-6506: Fix performance regression Due to the way modcount == 0 was handled, the iterator was reinitialized on every call to next. The fix is to no longer reset the modcount on detach but increment it. This

wicket git commit: WICKET-6506: Fix performance regression

Repository: wicket Updated Branches: refs/heads/master e7597f03f -> 0dc04e448 WICKET-6506: Fix performance regression Due to the way modcount == 0 was handled, the iterator was reinitialized on every call to next. The fix is to no longer reset the modcount on detach but increment it. This even

[jira] [Assigned] (WICKET-6506) Performance issue when large component isn't visible

[ https://issues.apache.org/jira/browse/WICKET-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij reassigned WICKET-6506: --- Assignee: Emond Papegaaij > Performance issue when large component isn't visible > -

[jira] [Commented] (WICKET-6509) Import junit packages as optional

[ https://issues.apache.org/jira/browse/WICKET-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296627#comment-16296627 ] Christoph Läubrich commented on WICKET-6509: You can simply add here: https:

[jira] [Comment Edited] (WICKET-6509) Import junit packages as optional

[ https://issues.apache.org/jira/browse/WICKET-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296614#comment-16296614 ] Martin Grigorov edited comment on WICKET-6509 at 12/19/17 10:34 AM: ---

[jira] [Commented] (WICKET-6509) Import junit packages as optional

[ https://issues.apache.org/jira/browse/WICKET-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296614#comment-16296614 ] Martin Grigorov commented on WICKET-6509: - It is marked as "provided" here: http

[jira] [Updated] (WICKET-6509) Import junit packages as optional

[ https://issues.apache.org/jira/browse/WICKET-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christoph Läubrich updated WICKET-6509: --- Issue Type: Improvement (was: Bug) > Import junit packages as optional > ---

[jira] [Commented] (WICKET-6509) Do not import junit packages

[ https://issues.apache.org/jira/browse/WICKET-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296521#comment-16296521 ] Christoph Läubrich commented on WICKET-6509: So in that case they should at l

[jira] [Updated] (WICKET-6509) Import junit packages as optional

[ https://issues.apache.org/jira/browse/WICKET-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christoph Läubrich updated WICKET-6509: --- Summary: Import junit packages as optional (was: Do not import junit packages) > Im

[jira] [Commented] (WICKET-6509) Do not import junit packages

[ https://issues.apache.org/jira/browse/WICKET-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296503#comment-16296503 ] Martijn Dashorst commented on WICKET-6509: -- They do depend on it, due to WicketT