Yes I had success.
I obtained the jar wicket-portlet-1.5.7.2.jar and added it to my local repo.
$MVN_CMD install:install-file \
-DgroupId=org.apache.wicket.portlet \
-DgeneratePom=true \
-DartifactId=wicket-portlet \
-Dversion=1.5.7.2 \
-Dpackaging=jar \
-Dfile=wicket-portlet-1.5.7.2.jar
Make sure your pom has the following entries:
<properties>
<wicket.version>1.5.7</wicket.version>
<jetty.version>7.5.0.v20110901</jetty.version>
</properties>
<dependency>
<groupId>javax.portlet</groupId>
<artifactId>portlet-api</artifactId>
<version>2.0</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.apache.wicket</groupId>
<artifactId>wicket-core</artifactId>
<version>${wicket.version}</version>
</dependency>
<dependency>
<groupId>org.apache.wicket</groupId>
<artifactId>wicket-extensions</artifactId>
<version>${wicket.version}</version>
</dependency>
<dependency>
<groupId>org.apache.portals.bridges</groupId>
<artifactId>portals-bridges-common</artifactId>
<version>2.0</version>
</dependency>
<dependency>
<groupId>org.apache.wicket.portlet</groupId>
<artifactId>wicket-portlet</artifactId>
<version>1.5.7.2</version>
</dependency>
I followed the naming convention of naming convention outlined on the Wicket
Wiki.
With Liferay 6.1.1, I also had to include
WEB-INF/liferay-plugin-package.properties
and add liferay-web-xml-enabled=false
If need be I can send my quick start / test app so you can see.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-Liferay-help-tp4651140p4651289.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
