You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by robsonke <gi...@git.apache.org> on 2015/03/04 15:36:51 UTC

[GitHub] wicket pull request: Added the new KeyReplacingLocalizer

GitHub user robsonke opened a pull request:

    https://github.com/apache/wicket/pull/103

    Added the new KeyReplacingLocalizer

    See https://issues.apache.org/jira/browse/WICKET-5847

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robsonke/wicket master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/wicket/pull/103.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #103
    
----
commit 99649251a04ffd1a6243c8b2211fd9850d0a19ea
Author: Rob Sonke <r....@maxxton.com>
Date:   2015-03-04T14:35:22Z

    Added the new KeyReplacingLocalizer

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] wicket issue #103: Added the new KeyReplacingLocalizer

Posted by martin-g <gi...@git.apache.org>.
Github user martin-g commented on the issue:

    https://github.com/apache/wicket/pull/103
  
    @robsonke Please close this PR because we don't have the permissions to do it ourselves! Thank you!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] wicket issue #103: Added the new KeyReplacingLocalizer

Posted by martin-g <gi...@git.apache.org>.
Github user martin-g commented on the issue:

    https://github.com/apache/wicket/pull/103
  
    @robsonke Ping!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] wicket issue #103: Added the new KeyReplacingLocalizer

Posted by klopfdreh <gi...@git.apache.org>.
Github user klopfdreh commented on the issue:

    https://github.com/apache/wicket/pull/103
  
    Hi @robsonke - this ticket can be closed due to the implementation of: https://issues.apache.org/jira/browse/WICKET-6193
    
    It is a slightly different implementation as you suggested, but I think it covers your requirement.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] wicket pull request #103: Added the new KeyReplacingLocalizer

Posted by robsonke <gi...@git.apache.org>.
Github user robsonke closed the pull request at:

    https://github.com/apache/wicket/pull/103


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] wicket issue #103: Added the new KeyReplacingLocalizer

Posted by robsonke <gi...@git.apache.org>.
Github user robsonke commented on the issue:

    https://github.com/apache/wicket/pull/103
  
    Oops sorry, I will


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---