FACES-2159 (REVERT) Enable Liferay IDE to identify Liferay Faces demo…

…/issue/test portlets as Liferay portlets
liferay · Mar 18, 2015 · 332b697 · 332b697
1 parent 6c611b3
commit 332b697
Show file tree

Hide file tree

Showing 8 changed files with 0 additions and 40 deletions.
diff --git a/demos/pom.xml b/demos/pom.xml
@@ -187,11 +187,6 @@
 	</profiles>
 	<build>
 		<plugins>
-			<!-- FACES-2159: Liferay IDE requires liferay-maven-plugin to be specified -->
-			<plugin>
-				<groupId>com.liferay.maven.plugins</groupId>
-				<artifactId>liferay-maven-plugin</artifactId>
-			</plugin>
 			<plugin>
 				<artifactId>maven-install-plugin</artifactId>
 				<configuration>

diff --git a/issues/pom.xml b/issues/pom.xml
@@ -19,11 +19,6 @@
 
 	<build>
 		<plugins>
-			<!-- FACES-2159: Liferay IDE requires liferay-maven-plugin to be specified -->
-			<plugin>
-				<groupId>com.liferay.maven.plugins</groupId>
-				<artifactId>liferay-maven-plugin</artifactId>
-			</plugin>
 			<plugin>
 				<groupId>org.apache.maven.plugins</groupId>
 				<artifactId>maven-deploy-plugin</artifactId>

diff --git a/test/bridge-tck/bridge-tck-lifecycle-set-portlet/pom.xml b/test/bridge-tck/bridge-tck-lifecycle-set-portlet/pom.xml
@@ -91,11 +91,6 @@
 	<!-- but the "unpack" approach found below meets our needs better than the maven-assembly-plugin -->
 	<build>
 		<plugins>
-			<!-- FACES-2159: Liferay IDE requires liferay-maven-plugin to be specified -->
-			<plugin>
-				<groupId>com.liferay.maven.plugins</groupId>
-				<artifactId>liferay-maven-plugin</artifactId>
-			</plugin>
 			<plugin>
 				<groupId>org.apache.maven.plugins</groupId>
 				<artifactId>maven-war-plugin</artifactId>

diff --git a/test/bridge-tck/bridge-tck-main-portlet/pom.xml b/test/bridge-tck/bridge-tck-main-portlet/pom.xml
@@ -277,11 +277,6 @@
 	<!-- but the "unpack" approach found below meets our needs better than the maven-assembly-plugin -->
 	<build>
 		<plugins>
-			<!-- FACES-2159: Liferay IDE requires liferay-maven-plugin to be specified -->
-			<plugin>
-				<groupId>com.liferay.maven.plugins</groupId>
-				<artifactId>liferay-maven-plugin</artifactId>
-			</plugin>
 			<plugin>
 				<groupId>org.appfuse.plugins</groupId>
 				<artifactId>maven-warpath-plugin</artifactId>

diff --git a/test/bridge-tck/bridge-tck-render-policy1-portlet/pom.xml b/test/bridge-tck/bridge-tck-render-policy1-portlet/pom.xml
@@ -91,11 +91,6 @@
 	<!-- but the "unpack" approach found below meets our needs better than the maven-assembly-plugin -->
 	<build>
 		<plugins>
-			<!-- FACES-2159: Liferay IDE requires liferay-maven-plugin to be specified -->
-			<plugin>
-				<groupId>com.liferay.maven.plugins</groupId>
-				<artifactId>liferay-maven-plugin</artifactId>
-			</plugin>
 			<plugin>
 				<groupId>org.apache.maven.plugins</groupId>
 				<artifactId>maven-war-plugin</artifactId>

diff --git a/test/bridge-tck/bridge-tck-render-policy2-portlet/pom.xml b/test/bridge-tck/bridge-tck-render-policy2-portlet/pom.xml
@@ -91,11 +91,6 @@
 	<!-- but the "unpack" approach found below meets our needs better than the maven-assembly-plugin -->
 	<build>
 		<plugins>
-			<!-- FACES-2159: Liferay IDE requires liferay-maven-plugin to be specified -->
-			<plugin>
-				<groupId>com.liferay.maven.plugins</groupId>
-				<artifactId>liferay-maven-plugin</artifactId>
-			</plugin>
 			<plugin>
 				<groupId>org.apache.maven.plugins</groupId>
 				<artifactId>maven-war-plugin</artifactId>

diff --git a/test/bridge-tck/bridge-tck-render-policy3-portlet/pom.xml b/test/bridge-tck/bridge-tck-render-policy3-portlet/pom.xml
@@ -91,11 +91,6 @@
 	<!-- but the "unpack" approach found below meets our needs better than the maven-assembly-plugin -->
 	<build>
 		<plugins>
-			<!-- FACES-2159: Liferay IDE requires liferay-maven-plugin to be specified -->
-			<plugin>
-				<groupId>com.liferay.maven.plugins</groupId>
-				<artifactId>liferay-maven-plugin</artifactId>
-			</plugin>
 			<plugin>
 				<groupId>org.apache.maven.plugins</groupId>
 				<artifactId>maven-war-plugin</artifactId>

diff --git a/test/bridge-tck/bridge-tck-response-wrapper-portlet/pom.xml b/test/bridge-tck/bridge-tck-response-wrapper-portlet/pom.xml
@@ -91,11 +91,6 @@
 	<!-- but the "unpack" approach found below meets our needs better than the maven-assembly-plugin -->
 	<build>
 		<plugins>
-			<!-- FACES-2159: Liferay IDE requires liferay-maven-plugin to be specified -->
-			<plugin>
-				<groupId>com.liferay.maven.plugins</groupId>
-				<artifactId>liferay-maven-plugin</artifactId>
-			</plugin>
 			<plugin>
 				<groupId>org.apache.maven.plugins</groupId>
 				<artifactId>maven-war-plugin</artifactId>