Have you checked out the entire wicket source tree - that contains
jdk14, jdk15 etc? If not then maybe the individual poms cannot find
the parent pom that defines those version variables.
On 11 Oct 2007, at 22:46, Tauren Mills wrote:
I just updated wicket, wicket-extensions and wicket-examples from
trunk. When I tried to run mvn install eclipse:eclpise, I got errors
stating that there were dependencies missing versions. So I added
versions to the pom.xml for wicket and wicket-examples. Now mvn runs.
Am I doing something wrong, or do the pom.xml files in trunk need
versions? Changing them to contain version params did the trick, but
should it work without them?
wicket/pom.xml:
<dependency>
<groupId>javax.portlet</groupId>
<artifactId>portlet-api</artifactId>
<version>1.0</version>
<scope>provided</scope>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.apache.portals.bridges</groupId>
<artifactId>portals-bridges-common</artifactId>
<version>1.0.3</version>
<scope>provided</scope>
<optional>true</optional>
</dependency>
wicket-examples/pom.xml:
<dependency>
<groupId>javax.portlet</groupId>
<artifactId>portlet-api</artifactId>
<version>1.0</version>
<scope>provided</scope>
</dependency>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
