You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martijn Dashorst (JIRA)" <ji...@apache.org> on 2011/01/24 10:19:43 UTC
[jira] Commented: (WICKET-3353) 'wicket' Maven module brings the
other three wicket modules as transitive dependencies
[ https://issues.apache.org/jira/browse/WICKET-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985579#action_12985579 ]
Martijn Dashorst commented on WICKET-3353:
------------------------------------------
This doesn't fix the problem when someone depends on wicket *and* wicket-extensions.
> 'wicket' Maven module brings the other three wicket modules as transitive dependencies
> --------------------------------------------------------------------------------------
>
> Key: WICKET-3353
> URL: https://issues.apache.org/jira/browse/WICKET-3353
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5-M3
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 1.5-RC2
>
>
> The new three-in-one Maven module 'wicket' brings -core, -util and -request as transitive dependencies.
> This way if the user app depends on 'wicket' then it will get wicket.jar, wicket-util.jar, wicket-request.jar and wicket-core.jar in its WEB-INF/lib/ folder.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.