this conversion doesn't distinguish between compile, test and provided dependencies.
you can edit your POM for 1.1.1 in your local repository to make the correct adjustments.
Martijn
On 3/3/06, Rob Dickens <[EMAIL PROTECTED]
> wrote:
To those using Maven 2 to build their Wicket projects,
The following appears to cause the Wicket jar, *together with all of
its dependencies* to be copied into the WEB-INF/lib/ of the target
war file:
<dependencies>
<dependency>
<groupId>wicket</groupId>
<artifactId>wicket</artifactId>
<version>1.1.1</version>
</dependency>
Jars copied to WEB-INF/lib/:
commons-logging-1.0.4.jar
junit-3.8.1.jar
log4j-1.2.11.jar
ognl-2.6.7.jar
servlet-api-2.3.jar
wicket-1.1.1.jar
I don't think this is ideal--e.g. the servlet-api jar does not belong
here.
Could anyone help out.
Thanks,
Rob
ps Is there a Wicket project architype available, does anyone know?
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
Living a wicket life...
Martijn Dashorst - http://www.jroller.com/page/dashorst
Wicket 1.1.1 is out: http://wicket.sourceforge.net/wicket-1.1
