Every release notes has the following in it:
To use in Maven:
<dependency>
<groupId>org.apache.wicket</groupId>
<artifactId>wicket-core</artifactId>
<version>1.5-RC4.2</version>
</dependency>
Depending on a pom is a fringe feature of Maven, I'm -1 on that.
Especially if that doesn't work in maven 2.
Martijn
On Tue, Jun 14, 2011 at 5:21 PM, Martin Grigorov <[email protected]> wrote:
> No. We tell them to use wicket:pom as we agreed few months ago (after
> the OSGi discussions)
> https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+1.5#MigrationtoWicket1.5-Mavenusersarerecommendedtodependonorg.apache.wicket%3Awicket%3Apomfromnowon
>
> It seems Maven 2 has problems...
> With Maven 3 I didn't have any problems so far.
>
> On Tue, Jun 14, 2011 at 6:15 PM, Martijn Dashorst
> <[email protected]> wrote:
>> On Tue, Jun 14, 2011 at 4:47 PM, Martin Grigorov <[email protected]>
>> wrote:
>>> Either use org.apache.wicket:wicket:pom or org.apache.wicket:wicket-core:jar
>>>
>>> I think we agreed to use :pom few months ago.
>>
>> That is broken... we tell folks to use wicket-core as their
>> dependency, we should do the same. Depending on wicket.pom is really
>> bad conceptually.
>>
>> Martijn
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
