On 8/27/07, Jan Kriesten <[EMAIL PROTECTED]> wrote:
> i didn't know that mvn is required for using wicket-beta-2.
Not for using, but for getting documentation it is really helpful.
That is part of the reason why we use maven.
> also, reading that output isn't really useful since it suggests many libs to
> be
> dependent on which it isn't.
Read the maven documentation and understand the pom. Then you see that only the
<project><dependencies>...</dependencies></project>
part is relevant at the top level. This gives the following list:
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
<version>2.3</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.4.2</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.4.2</version>
</dependency>
</dependencies>
> igor's reply was definitely more helpful.
Perhaps in the short term... However instead of giving a fish, I teach
how to fish.
Martijn
--
Wicket joins the Apache Software Foundation as Apache Wicket
Apache Wicket 1.3.0-beta2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
