You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2009/10/23 18:00:59 UTC
[jira] Resolved: (WICKET-2536) Guice 2.0 and its maven2 repository
groupId
[ https://issues.apache.org/jira/browse/WICKET-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag resolved WICKET-2536.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-M1
1.4.4
Assignee: Juergen Donnerstag
thanks
> 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
> Assignee: Juergen Donnerstag
> Fix For: 1.4.4, 1.5-M1
>
> 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.