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/464 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The SingleBra

buildbot failure in on wicket-master

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/877 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The SingleBranchSched

wicket git commit: WICKET-6484 Wicket.Cookie.set does not set 'secure' flag

Repository: wicket Updated Branches: refs/heads/wicket-7.x 1b9f810f3 -> 5452f734c WICKET-6484 Wicket.Cookie.set does not set 'secure' flag (cherry picked from commit 8403c3725d71c33b87b3c4e196cf078e7762840d) Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit: http://git-wip-u

[jira] [Commented] (WICKET-6484) Wicket.Cookie.set does not set 'secure' flag

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

[jira] [Commented] (WICKET-6484) Wicket.Cookie.set does not set 'secure' flag

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

[jira] [Resolved] (WICKET-6484) Wicket.Cookie.set does not set 'secure' flag

[ https://issues.apache.org/jira/browse/WICKET-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov resolved WICKET-6484. - Resolution: Fixed Assignee: Martin Grigorov Fix Version/s: 6.29.0

[jira] [Commented] (WICKET-6484) Wicket.Cookie.set does not set 'secure' flag

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

wicket git commit: WICKET-6484 Wicket.Cookie.set does not set 'secure' flag

Repository: wicket Updated Branches: refs/heads/wicket-6.x e5ddaaaf5 -> d0967b231 WICKET-6484 Wicket.Cookie.set does not set 'secure' flag (cherry picked from commit 8403c3725d71c33b87b3c4e196cf078e7762840d) Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit: http://git-wip-u

wicket git commit: WICKET-6484 Wicket.Cookie.set does not set 'secure' flag

Repository: wicket Updated Branches: refs/heads/master 02808f7d0 -> 8403c3725 WICKET-6484 Wicket.Cookie.set does not set 'secure' flag Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit: http://git-wip-us.apache.org/repos/asf/wicket/commit/8403c372 Tree: http://git-wip-us.apac

[jira] [Commented] (WICKET-6483) JavaxUpgradeHttpRequest can cause NullPointerException

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

wicket git commit: WICKET-6483 JavaxUpgradeHttpRequest can cause NullPointerException

Repository: wicket Updated Branches: refs/heads/wicket-7.x 2acd52de0 -> 1b9f810f3 WICKET-6483 JavaxUpgradeHttpRequest can cause NullPointerException WICKET-6493 WebSocket SessionIds are wrong (HttpSession one used instead of Websocket one) + NPE if no HttpSession is found during Handshake Req

[jira] [Commented] (WICKET-6493) WebSocket SessionIds are wrong (HttpSession one used instead of Websocket one) + NPE if no HttpSession is found during Handshake Request

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

[jira] [Commented] (WICKET-6493) WebSocket SessionIds are wrong (HttpSession one used instead of Websocket one) + NPE if no HttpSession is found during Handshake Request

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

[jira] [Commented] (WICKET-6483) JavaxUpgradeHttpRequest can cause NullPointerException

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

wicket git commit: WICKET-6483 JavaxUpgradeHttpRequest can cause NullPointerException

Repository: wicket Updated Branches: refs/heads/master e4ee449e5 -> 02808f7d0 WICKET-6483 JavaxUpgradeHttpRequest can cause NullPointerException WICKET-6493 WebSocket SessionIds are wrong (HttpSession one used instead of Websocket one) + NPE if no HttpSession is found during Handshake Request

[jira] [Resolved] (WICKET-6483) JavaxUpgradeHttpRequest can cause NullPointerException

[ https://issues.apache.org/jira/browse/WICKET-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov resolved WICKET-6483. - Resolution: Duplicate > JavaxUpgradeHttpRequest can cause NullPointerException >

[jira] [Commented] (WICKET-6477) Component.getDefaultModelObject() wraps in RuntimeException instead of WicketRuntimeException

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

[jira] [Resolved] (WICKET-6477) Component.getDefaultModelObject() wraps in RuntimeException instead of WicketRuntimeException

[ https://issues.apache.org/jira/browse/WICKET-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov resolved WICKET-6477. - Resolution: Fixed Fix Version/s: 7.10.0 8.0.0 > Component.getDe

[jira] [Commented] (WICKET-6477) Component.getDefaultModelObject() wraps in RuntimeException instead of WicketRuntimeException

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

wicket git commit: WICKET-6477 Component.getDefaultModelObject() wraps in RuntimeException instead of WicketRuntimeException

Repository: wicket Updated Branches: refs/heads/wicket-7.x 5324ae3fa -> 2acd52de0 WICKET-6477 Component.getDefaultModelObject() wraps in RuntimeException instead of WicketRuntimeException (cherry picked from commit e4ee449e54df86664e132c60892fffcc7aa0fac5) Project: http://git-wip-us.apache.

wicket git commit: WICKET-6477 Component.getDefaultModelObject() wraps in RuntimeException instead of WicketRuntimeException

Repository: wicket Updated Branches: refs/heads/master e6e0f0ef9 -> e4ee449e5 WICKET-6477 Component.getDefaultModelObject() wraps in RuntimeException instead of WicketRuntimeException Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit: http://git-wip-us.apache.org/repos/asf/w

[jira] [Assigned] (WICKET-6477) Component.getDefaultModelObject() wraps in RuntimeException instead of WicketRuntimeException

[ https://issues.apache.org/jira/browse/WICKET-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov reassigned WICKET-6477: --- Assignee: Martin Grigorov > Component.getDefaultModelObject() wraps in RuntimeExcept

[jira] [Commented] (WICKET-6441) MockHttpSession and MockSessionStore don't call onInvalidate() on invalidate()

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

wicket git commit: WICKET-6441 MockHttpSession and MockSessionStore don't call onInvalidate() on invalidate()

Repository: wicket Updated Branches: refs/heads/wicket-7.x 92fe4c3e6 -> 5324ae3fa WICKET-6441 MockHttpSession and MockSessionStore don't call onInvalidate() on invalidate() (cherry picked from commit e6e0f0ef908dc99a924f6b1358ec5b7f3791e1f3) Project: http://git-wip-us.apache.org/repos/asf/w

[jira] [Updated] (WICKET-6441) MockHttpSession and MockSessionStore don't call onInvalidate() on invalidate()

[ https://issues.apache.org/jira/browse/WICKET-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov updated WICKET-6441: Summary: MockHttpSession and MockSessionStore don't call onInvalidate() on invalidate() (w

[jira] [Commented] (WICKET-6441) MockHttpSession and MockSessionStore don't call onInvalidate() on invalidate()

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

wicket git commit: WICKET-6441 MockHttpSession and MockSessionStore don't call onInvalidate() on invalidate()

Repository: wicket Updated Branches: refs/heads/master 5cabbb68e -> e6e0f0ef9 WICKET-6441 MockHttpSession and MockSessionStore don't call onInvalidate() on invalidate() Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit: http://git-wip-us.apache.org/repos/asf/wicket/commit/e6

buildbot success in on wicket-branch-7.x

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

buildbot success in on wicket-master

The Buildbot has detected a restored build on builder wicket-master while building wicket. Full details are available at: https://ci.apache.org/builders/wicket-master/builds/875 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The SingleBranchSc

[jira] [Commented] (WICKET-6441) MockSessionStore doesn't call onInvalidate() on invalidate()

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

[jira] [Resolved] (WICKET-6441) MockSessionStore doesn't call onInvalidate() on invalidate()

[ https://issues.apache.org/jira/browse/WICKET-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov resolved WICKET-6441. - Resolution: Fixed Assignee: Martin Grigorov Fix Version/s: 7.10.0

[jira] [Commented] (WICKET-6441) MockSessionStore doesn't call onInvalidate() on invalidate()

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

[jira] [Updated] (WICKET-6441) MockSessionStore doesn't call onInvalidate() on invalidate()

[ https://issues.apache.org/jira/browse/WICKET-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov updated WICKET-6441: Summary: MockSessionStore doesn't call onInvalidate() on invalidate() (was: MockHttpSessio

wicket git commit: WICKET-6441 MockSessionStore doesn't call onInvalidate() on invalidate()

Repository: wicket Updated Branches: refs/heads/master 54f4db03a -> 5cabbb68e WICKET-6441 MockSessionStore doesn't call onInvalidate() on invalidate() Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit: http://git-wip-us.apache.org/repos/asf/wicket/commit/5cabbb68 Tree: http:/

wicket git commit: WICKET-6441 MockSessionStore doesn't call onInvalidate() on invalidate()

Repository: wicket Updated Branches: refs/heads/wicket-7.x bce8b05bc -> 92fe4c3e6 WICKET-6441 MockSessionStore doesn't call onInvalidate() on invalidate() (cherry picked from commit 5cabbb68effd82e7d195d39c16e3e700d53eb9cc) Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit:

wicket git commit: Update Node.js to 8.9.0 and npm to 5.6.0

Repository: wicket Updated Branches: refs/heads/master 588408a19 -> 54f4db03a Update Node.js to 8.9.0 and npm to 5.6.0 Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit: http://git-wip-us.apache.org/repos/asf/wicket/commit/54f4db03 Tree: http://git-wip-us.apache.org/repos/asf

[jira] [Commented] (WICKET-6489) Exception when "identifier|code" javascript is not start on PrependJavaScript

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

[jira] [Resolved] (WICKET-6489) Exception when "identifier|code" javascript is not start on PrependJavaScript

[ https://issues.apache.org/jira/browse/WICKET-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov resolved WICKET-6489. - Resolution: Fixed Assignee: Martin Grigorov Fix Version/s: 7.10.0

[jira] [Commented] (WICKET-6489) Exception when "identifier|code" javascript is not start on PrependJavaScript

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

wicket git commit: WICKET-6489 Exception when "identifier|code" javascript is not start on PrependJavaScript

Repository: wicket Updated Branches: refs/heads/master 922d56236 -> 588408a19 WICKET-6489 Exception when "identifier|code" javascript is not start on PrependJavaScript Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit: http://git-wip-us.apache.org/repos/asf/wicket/commit/588

wicket git commit: WICKET-6489 Exception when "identifier|code" javascript is not start on PrependJavaScript

Repository: wicket Updated Branches: refs/heads/wicket-7.x 68f23440c -> bce8b05bc WICKET-6489 Exception when "identifier|code" javascript is not start on PrependJavaScript Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit: http://git-wip-us.apache.org/repos/asf/wicket/commit

[jira] [Resolved] (WICKET-6493) WebSocket SessionIds are wrong (HttpSession one used instead of Websocket one) + NPE if no HttpSession is found during Handshake Request

[ https://issues.apache.org/jira/browse/WICKET-6493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov resolved WICKET-6493. - Resolution: Fixed Fix Version/s: 7.10.0 8.0.0 > WebSocket Sessi

[jira] [Commented] (WICKET-6493) WebSocket SessionIds are wrong (HttpSession one used instead of Websocket one) + NPE if no HttpSession is found during Handshake Request

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

wicket git commit: WICKET-6493 WebSocket SessionIds are wrong (HttpSession one used instead of Websocket one) + NPE if no HttpSession is found during Handshake Request

Repository: wicket Updated Branches: refs/heads/wicket-7.x 8c7f583a3 -> 68f23440c WICKET-6493 WebSocket SessionIds are wrong (HttpSession one used instead of Websocket one) + NPE if no HttpSession is found during Handshake Request (cherry picked from commit 922d56236157b3356c9eba7a43aed8c838b

[jira] [Commented] (WICKET-6493) WebSocket SessionIds are wrong (HttpSession one used instead of Websocket one) + NPE if no HttpSession is found during Handshake Request

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

wicket git commit: WICKET-6493 WebSocket SessionIds are wrong (HttpSession one used instead of Websocket one) + NPE if no HttpSession is found during Handshake Request

Repository: wicket Updated Branches: refs/heads/master 869ff9265 -> 922d56236 WICKET-6493 WebSocket SessionIds are wrong (HttpSession one used instead of Websocket one) + NPE if no HttpSession is found during Handshake Request Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commi

[jira] [Updated] (WICKET-6510) Provide unified "click" and "submit" mechanism in WicketTester/FormTester

[ https://issues.apache.org/jira/browse/WICKET-6510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov updated WICKET-6510: Priority: Minor (was: Major) > Provide unified "click" and "submit" mechanism in WicketTes

[jira] [Commented] (WICKET-6513) NullPointerException at PageStoreManager$SessionEntry after login

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

[jira] [Commented] (WICKET-6513) NullPointerException at PageStoreManager$SessionEntry after login

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

[jira] [Resolved] (WICKET-6513) NullPointerException at PageStoreManager$SessionEntry after login

[ https://issues.apache.org/jira/browse/WICKET-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov resolved WICKET-6513. - Resolution: Fixed Fix Version/s: 7.10.0 8.0.0 > NullPointerExce

wicket git commit: WICKET-6513 NullPointerException at PageStoreManager$SessionEntry after login

Repository: wicket Updated Branches: refs/heads/wicket-7.x a352fe2be -> 8c7f583a3 WICKET-6513 NullPointerException at PageStoreManager$SessionEntry after login Check for storeTouchedPages == null before trying to use it. It might be null in case an alternative serialization library is used (c

wicket git commit: WICKET-6513 NullPointerException at PageStoreManager$SessionEntry after login

Repository: wicket Updated Branches: refs/heads/master 37a91e459 -> 869ff9265 WICKET-6513 NullPointerException at PageStoreManager$SessionEntry after login Check for storeTouchedPages == null before trying to use it. It might be null in case an alternative serialization library is used Proje

buildbot failure in on wicket-master

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/874 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The SingleBranchSched

[jira] [Assigned] (WICKET-6513) NullPointerException at PageStoreManager$SessionEntry after login

[ https://issues.apache.org/jira/browse/WICKET-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov reassigned WICKET-6513: --- Assignee: Martin Grigorov > NullPointerException at PageStoreManager$SessionEntry af

[jira] [Commented] (WICKET-6511) AbstractColumn should be subject of IAuthorizationStrategy

[ https://issues.apache.org/jira/browse/WICKET-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16306963#comment-16306963 ] Martin Grigorov commented on WICKET-6511: - I am not sure what you suggest exactly

[jira] [Updated] (WICKET-6511) AbstractColumn should be subject of IAuthorizationStrategy

[ https://issues.apache.org/jira/browse/WICKET-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov updated WICKET-6511: Priority: Minor (was: Major) > AbstractColumn should be subject of IAuthorizationStrategy

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

[ https://issues.apache.org/jira/browse/WICKET-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov resolved WICKET-6509. - Resolution: Fixed Fix Version/s: 8.0.0 I've applied both suggestions. I hope they

[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=16306957#comment-16306957 ] ASF subversion and git services commented on WICKET-6509: - Commit

[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=16306956#comment-16306956 ] Martin Grigorov commented on WICKET-6509: - Yet another "solution" from an OSGi "e

wicket git commit: WICKET-6509 Import junit packages as optional

Repository: wicket Updated Branches: refs/heads/master cbf458380 -> 37a91e459 WICKET-6509 Import junit packages as optional Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit: http://git-wip-us.apache.org/repos/asf/wicket/commit/37a91e45 Tree: http://git-wip-us.apache.org/repo

[jira] [Commented] (WICKET-6504) Using a serializable model for FileSystemResource's path

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

[jira] [Updated] (WICKET-6504) Use a serializable model for FileSystemResource's path

[ https://issues.apache.org/jira/browse/WICKET-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov updated WICKET-6504: Summary: Use a serializable model for FileSystemResource's path (was: Using a serializable

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

[ https://issues.apache.org/jira/browse/WICKET-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov reassigned WICKET-6509: --- Assignee: Martin Grigorov > Import junit packages as optional >

[jira] [Resolved] (WICKET-6504) Use a serializable model for FileSystemResource's path

[ https://issues.apache.org/jira/browse/WICKET-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov resolved WICKET-6504. - Resolution: Fixed Fix Version/s: 8.0.0 > Use a serializable model for FileSystemRe

wicket git commit: WICKET-6504 Use a serializable model for FileSystemResource's path

Repository: wicket Updated Branches: refs/heads/master 63a3296c7 -> cbf458380 WICKET-6504 Use a serializable model for FileSystemResource's path Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit: http://git-wip-us.apache.org/repos/asf/wicket/commit/cbf45838 Tree: http://git-w

[jira] [Updated] (WICKET-6504) Using a serializable model for FileSystemResource

[ https://issues.apache.org/jira/browse/WICKET-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov updated WICKET-6504: Summary: Using a serializable model for FileSystemResource (was: Using a Model for FileSys

[jira] [Updated] (WICKET-6504) Using a serializable model for FileSystemResource's path

[ https://issues.apache.org/jira/browse/WICKET-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov updated WICKET-6504: Summary: Using a serializable model for FileSystemResource's path (was: Using a serializab

[jira] [Assigned] (WICKET-6504) Using a Model for FileSystemResource

[ https://issues.apache.org/jira/browse/WICKET-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov reassigned WICKET-6504: --- Assignee: Martin Grigorov > Using a Model for FileSystemResource > -

[jira] [Resolved] (WICKET-6514) FeedbackCollector(Component) should not collect session-scoped feedback messages

[ https://issues.apache.org/jira/browse/WICKET-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov resolved WICKET-6514. - Resolution: Fixed Fix Version/s: 8.0.0 > FeedbackCollector(Component) should not c

[jira] [Commented] (WICKET-6514) FeedbackCollector(Component) should not collect session-scoped feedback messages

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

wicket git commit: WICKET-6514 FeedbackCollector(Component) should not collect session-scoped feedback messages

Repository: wicket Updated Branches: refs/heads/master db2317bf4 -> 63a3296c7 WICKET-6514 FeedbackCollector(Component) should not collect session-scoped feedback messages Project: http://git-wip-us.apache.org/repos/asf/wicket/repo Commit: http://git-wip-us.apache.org/repos/asf/wicket/commit/

[jira] [Updated] (WICKET-6514) FeedbackCollector(Component) should not collect session-scoped feedback messages

[ https://issues.apache.org/jira/browse/WICKET-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov updated WICKET-6514: Summary: FeedbackCollector(Component) should not collect session-scoped feedback messages

[jira] [Assigned] (WICKET-6514) Change behavior of FeedbackCollector [Breaking change]

[ https://issues.apache.org/jira/browse/WICKET-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov reassigned WICKET-6514: --- Assignee: Martin Grigorov > Change behavior of FeedbackCollector [Breaking change] >

[jira] [Updated] (WICKET-6515) Function 'submitMultipartForm' doesn't work correctly in FF

[ https://issues.apache.org/jira/browse/WICKET-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov updated WICKET-6515: Priority: Minor (was: Major) > Function 'submitMultipartForm' doesn't work correctly in FF