Duplicated portlet-api dependency with false scope in tapestry-portlet.pom
--------------------------------------------------------------------------
Key: TAPESTRY-1734
URL: https://issues.apache.org/jira/browse/TAPESTRY-1734
Project: Tapestry
Issue Type: Bug
Components: Portlet
Affects Versions: 4.1.2
Reporter: Holger Stolzenberg
Regarding the POM for tapestry-portlet on ibiblio, you can see that there are 2
dependencies referencing the portlet api, one with the old group id
"portlet-api" and one with the new "jawax.portlet". That problem is that the
dependency with the group id "portlet-api" is missing the scope.
So if someone packages a jar/war (mvn package) the portlet-api.jar gets package
into the archive because the "provided" scope of jawax.portlet -> portlet-api
gets overriden.
For me that caused issues when deploying the WAR the Liferay.
A quick fix is to exclude the one "portlet-api -> portlet-api" dependency from
tapestry-portlet dep in your project as shown belown.
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-portlet</artifactId>
<version>4.1.2</version>
<exclusions>
<exclusion>
<groupId>portlet-api</groupId>
<artifactId>portlet-api</artifactId>
</exclusion>
</exclusions>
</dependency>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
