[
https://issues.apache.org/jira/browse/WICKET-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mat Johns updated WICKET-2536:
------------------------------
Attachment: guice-2.0.patch
groupId.patch
Two (rather simple) patch's;
groupId.patch; just moving the groupId over to com.google.inject
guice-2.0.patch; moving the groupId and bumping the version.
> Guice 2.0 and its maven2 repository groupId
> -------------------------------------------
>
> Key: WICKET-2536
> URL: https://issues.apache.org/jira/browse/WICKET-2536
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-guice
> Affects Versions: 1.4.3
> Reporter: Mat Johns
> Attachments: groupId.patch, guice-2.0.patch
>
>
> Guice 2.0 has now been released; I have been using it within my own projects
> and appears to be backwards compatible with 1.0 (certain as far as my usage
> of wicket-guice is concerned). However it seems that Guice has moved homes
> (well its groupId).
> com.google.code.guice => com.google.inject
> Firstly can this groupId be updated (the new groupId has both 1.0 and 2.0;
> whereas the previous one just features 1.0); this is a little bit of a faff
> due to having to list and exclusion for the old groupId to avoid depending on
> both.
> Secondly can the Guice dependency be bumped up to 2.0.
> The references in wicket-parent and wicket-guice pom's are the only changes
> required.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
