Fórum
Cannot add the same component twice: vlsequ12-retrieve-update
Hagen K, modificado 10 Anos atrás.
Cannot add the same component twice: vlsequ12-retrieve-update
New Member Postagens: 15 Data de Entrada: 05/09/12 Postagens Recentes
I'm not sure if this is the correct category but here it goes.
I'm trying to build an JSF ICEfaces portlet (Liferay 6.2) but happen to encounter a problem/ error with the portlet before even customizing it.
Sequence of steps:
1. Create a new portlet by using Liferay IDE Eclipse Plugin. Selected "Portlet", "JSF 2.x" and then "ICEfaces".
2. After the creation I modified the "ivy.xml" in order to point to a valid "3.2.4-ga5" location
3. Drag the portlet project to the Tomcat server to deploy it
4. Open the browser and access the Liferay portal and add the newly created portlet onto the page
-> Observe that the portlet is displayed correctly.
5. While the Tomcat server is still running, make a right click on the portlet project and select "Liferay" -> "SDK" -> "All"
-> Observe that the build appears to go through fine
6. Refresh the Liferay page
-> Observe that the portlet now shows the error "Cannot add the same component twice: vlsequ12-retrieve-update"
Note: As of testing it appears that the error is not encountered if the Tomcat server is stopped prior to running "Liferay" -> "SDK" -> "All".
Correction: Actually it doesn't matter whether Tomcat is running or not.
Additional information:
I have attached the page with the error message to this post. The file name is "localhost.htm".
Furthermore you can watch this YouTube video which shows how the problem can be reproduced.
Questions:
1. Does anybody else encounter this problem too?
2. How can this problem be overcome once the error occured?
I'm trying to build an JSF ICEfaces portlet (Liferay 6.2) but happen to encounter a problem/ error with the portlet before even customizing it.
Sequence of steps:
1. Create a new portlet by using Liferay IDE Eclipse Plugin. Selected "Portlet", "JSF 2.x" and then "ICEfaces".
2. After the creation I modified the "ivy.xml" in order to point to a valid "3.2.4-ga5" location
3. Drag the portlet project to the Tomcat server to deploy it
4. Open the browser and access the Liferay portal and add the newly created portlet onto the page
-> Observe that the portlet is displayed correctly.
5. While the Tomcat server is still running, make a right click on the portlet project and select "Liferay" -> "SDK" -> "All"
-> Observe that the build appears to go through fine
6. Refresh the Liferay page
-> Observe that the portlet now shows the error "Cannot add the same component twice: vlsequ12-retrieve-update"
Correction: Actually it doesn't matter whether Tomcat is running or not.
Additional information:
I have attached the page with the error message to this post. The file name is "localhost.htm".
Furthermore you can watch this YouTube video which shows how the problem can be reproduced.
Questions:
1. Does anybody else encounter this problem too?
2. How can this problem be overcome once the error occured?
Anexos:
Neil Griffin, modificado 10 Anos atrás.
RE: Cannot add the same component twice: vlsequ12-retrieve-update
Liferay Legend Postagens: 2655 Data de Entrada: 27/07/05 Postagens Recentes
Hi Hagen,
All I can say is WOW!
That is the most comprehensive bug report I have ever seen in my life. The YouTube video was extremely helpful!
Thanks so much for using Liferay Portal 6.2 and being willing to try Liferay Faces 3.2.4-ga5-SNAPSHOT. We will try and reproduce the problem and report back to you here in this message thread with the results.
Kind Regards,
Neil
All I can say is WOW!
That is the most comprehensive bug report I have ever seen in my life. The YouTube video was extremely helpful!
Thanks so much for using Liferay Portal 6.2 and being willing to try Liferay Faces 3.2.4-ga5-SNAPSHOT. We will try and reproduce the problem and report back to you here in this message thread with the results.
Kind Regards,
Neil
Neil Griffin, modificado 10 Anos atrás.
RE: Cannot add the same component twice: vlsequ12-retrieve-update
Liferay Legend Postagens: 2655 Data de Entrada: 27/07/05 Postagens Recentes
When you get a chance, please upgrade to the new Liferay IDE 2.0 M2 version and let us know if you still have the problem. BTW, it will let you create projects for Ant+Ivy or Maven.
Hagen K, modificado 10 Anos atrás.
RE: Cannot add the same component twice: vlsequ12-retrieve-update
New Member Postagens: 15 Data de Entrada: 05/09/12 Postagens RecentesNeil Griffin:
When you get a chance, please upgrade to the new Liferay IDE 2.0 M2 version and let us know if you still have the problem. BTW, it will let you create projects for Ant+Ivy or Maven.
Hi Neil,
I did what you suggested but the problem remained the same. Please see this video as evidence.
Furthermore, I then tried to create an ICEFaces Portlet by using the Maven option but that failed right away as shown with this video.
Since the Eclipse error referred to "maven.archetypes:liferay-portlet-icefaces-archetype:6.2.0-RC5" I had then the feeling that Eclipse might mashup my existing workspaces (i.e. I have one 6.2.0-RC5 workspace as well). In the light of this, I then created a new Eclipse instance with only one workspace for Liferay 6.2. However the issue remained unchanged despite of using this vanilla instance of Eclipse.
Thank you,
Hagen
Vernon Singleton, modificado 10 Anos atrás.
RE: Cannot add the same component twice: vlsequ12-retrieve-update
Expert Postagens: 315 Data de Entrada: 14/01/13 Postagens Recentes
Hi Hagen,
You can click the "watch" link on this issue
to get a notification when this is resolved.
- Vernon
You can click the "watch" link on this issue
to get a notification when this is resolved.
- Vernon
Hagen K, modificado 10 Anos atrás.
RE: Cannot add the same component twice: vlsequ12-retrieve-update
New Member Postagens: 15 Data de Entrada: 05/09/12 Postagens Recentes
Thank you Vernon for following this up and creating the bug.
Vernon Singleton, modificado 8 Anos atrás.
Re: [Liferay Forums][Liferay Faces - English] RE: Cannot add the same compo
Expert Postagens: 315 Data de Entrada: 14/01/13 Postagens Recentes
Hi Neil,
I think I was able to reproduce his error.
The second time that the build occurs in eclipse when he choses RIght
click Test-portlet -> Liferay -> SDK -> all
I get this in the WEB-INF/lib of the deployed portlet:
$ ls ./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/*.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/FastInfoset-1.2.12.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/activation-1.1.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-beanutils.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-collections.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-digester.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-lang.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-logging.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/el-api-1.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-ace-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-ace.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icepush-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/javax.faces-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jboss-el-2.0.1.GA.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jboss-el.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-api-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-api.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-impl-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-impl.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsp-api-2.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-api-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-api.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-impl-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-impl.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-portal-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-portal.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-util-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-util.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/log4j-extras.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/log4j.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/mail-1.4.1.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-bridges.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-java.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-taglib.jar
Notice how there is now an icefaces.jar AND an icefaces-3.3.0.jar?
I'm pretty sure that this is the problem. Just wanted to let you know
this, in case it is obvious to you why the second build invoked from
within eclipse that way might cause the icefaces.jar to get deployed
instead of the icesfaces-3.3.0.jar.
Anyway, I will be investigating further to figure out why, but I was
hoping you might already know the answer as you often do :-D
- Vernon
On Thu, Nov 7, 2013 at 1:06 PM, Neil Griffin from liferay.com
<forums@liferay.com> wrote:
> When you get a chance, please upgrade to the new Liferay IDE 2.0 M2 version
> and let us know if you still have the problem. BTW, it will let you create
> projects for Ant+Ivy or Maven.
>
>
> To view the thread, follow the link below:
> https://www.liferay.com/community/forums/-/message_boards/view_message/31235974
> --
> Liferay.com
I think I was able to reproduce his error.
The second time that the build occurs in eclipse when he choses RIght
click Test-portlet -> Liferay -> SDK -> all
I get this in the WEB-INF/lib of the deployed portlet:
$ ls ./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/*.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/FastInfoset-1.2.12.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/activation-1.1.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-beanutils.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-collections.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-digester.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-lang.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-logging.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/el-api-1.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-ace-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-ace.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icepush-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/javax.faces-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jboss-el-2.0.1.GA.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jboss-el.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-api-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-api.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-impl-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-impl.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsp-api-2.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-api-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-api.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-impl-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-impl.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-portal-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-portal.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-util-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-util.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/log4j-extras.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/log4j.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/mail-1.4.1.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-bridges.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-java.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-taglib.jar
Notice how there is now an icefaces.jar AND an icefaces-3.3.0.jar?
I'm pretty sure that this is the problem. Just wanted to let you know
this, in case it is obvious to you why the second build invoked from
within eclipse that way might cause the icefaces.jar to get deployed
instead of the icesfaces-3.3.0.jar.
Anyway, I will be investigating further to figure out why, but I was
hoping you might already know the answer as you often do :-D
- Vernon
On Thu, Nov 7, 2013 at 1:06 PM, Neil Griffin from liferay.com
<forums@liferay.com> wrote:
> When you get a chance, please upgrade to the new Liferay IDE 2.0 M2 version
> and let us know if you still have the problem. BTW, it will let you create
> projects for Ant+Ivy or Maven.
>
>
> To view the thread, follow the link below:
> https://www.liferay.com/community/forums/-/message_boards/view_message/31235974
> --
> Liferay.com
Vernon Singleton, modificado 8 Anos atrás.
Re: [Liferay Forums][Liferay Faces - English] RE: Cannot add the same compo
Expert Postagens: 315 Data de Entrada: 14/01/13 Postagens Recentes
Hi Neil,
I think I was able to reproduce his error.
The second time that the build occurs in eclipse when he choses RIght
click Test-portlet -> Liferay -> SDK -> all
I get this in the WEB-INF/lib of the deployed portlet:
$ ls ./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/*.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/FastInfoset-1.2.12.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/activation-1.1.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-beanutils.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-collections.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-digester.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-lang.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-logging.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/el-api-1.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-ace-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-ace.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icepush-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/javax.faces-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jboss-el-2.0.1.GA.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jboss-el.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-api-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-api.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-impl-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-impl.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsp-api-2.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-api-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-api.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-impl-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-impl.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-portal-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-portal.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-util-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-util.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/log4j-extras.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/log4j.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/mail-1.4.1.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-bridges.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-java.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-taglib.jar
Notice how there is now an icefaces.jar AND an icefaces-3.3.0.jar?
I'm pretty sure that this is the problem. Just wanted to let you know
this, in case it is obvious to you why the second build invoked from
within eclipse that way might cause the icefaces.jar to get deployed
instead of the icesfaces-3.3.0.jar.
Anyway, I will be investigating further to figure out why, but I was
hoping you might already know the answer as you often do :-D
- Vernon
On Thu, Nov 7, 2013 at 1:06 PM, Neil Griffin from liferay.com
<forums@liferay.com> wrote:
> When you get a chance, please upgrade to the new Liferay IDE 2.0 M2 version
> and let us know if you still have the problem. BTW, it will let you create
> projects for Ant+Ivy or Maven.
>
>
> To view the thread, follow the link below:
> https://www.liferay.com/community/forums/-/message_boards/view_message/31235974
> --
> Liferay.com
I think I was able to reproduce his error.
The second time that the build occurs in eclipse when he choses RIght
click Test-portlet -> Liferay -> SDK -> all
I get this in the WEB-INF/lib of the deployed portlet:
$ ls ./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/*.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/FastInfoset-1.2.12.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/activation-1.1.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-beanutils.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-collections.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-digester.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-lang.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-logging.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/el-api-1.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-ace-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-ace.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icepush-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/javax.faces-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jboss-el-2.0.1.GA.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jboss-el.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-api-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-api.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-impl-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-impl.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsp-api-2.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-api-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-api.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-impl-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-impl.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-portal-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-portal.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-util-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-util.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/log4j-extras.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/log4j.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/mail-1.4.1.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-bridges.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-java.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-taglib.jar
Notice how there is now an icefaces.jar AND an icefaces-3.3.0.jar?
I'm pretty sure that this is the problem. Just wanted to let you know
this, in case it is obvious to you why the second build invoked from
within eclipse that way might cause the icefaces.jar to get deployed
instead of the icesfaces-3.3.0.jar.
Anyway, I will be investigating further to figure out why, but I was
hoping you might already know the answer as you often do :-D
- Vernon
On Thu, Nov 7, 2013 at 1:06 PM, Neil Griffin from liferay.com
<forums@liferay.com> wrote:
> When you get a chance, please upgrade to the new Liferay IDE 2.0 M2 version
> and let us know if you still have the problem. BTW, it will let you create
> projects for Ant+Ivy or Maven.
>
>
> To view the thread, follow the link below:
> https://www.liferay.com/community/forums/-/message_boards/view_message/31235974
> --
> Liferay.com
Vernon Singleton, modificado 8 Anos atrás.
Re: [Liferay Forums][Liferay Faces - English] RE: Cannot add the same compo
Expert Postagens: 315 Data de Entrada: 14/01/13 Postagens Recentes
Hi Neil,
I think I was able to reproduce his error.
The second time that the build occurs in eclipse when he choses RIght
click Test-portlet -> Liferay -> SDK -> all
I get this in the WEB-INF/lib of the deployed portlet:
$ ls ./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/*.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/FastInfoset-1.2.12.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/activation-1.1.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-beanutils.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-collections.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-digester.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-lang.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-logging.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/el-api-1.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-ace-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-ace.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icepush-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/javax.faces-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jboss-el-2.0.1.GA.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jboss-el.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-api-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-api.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-impl-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-impl.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsp-api-2.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-api-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-api.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-impl-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-impl.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-portal-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-portal.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-util-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-util.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/log4j-extras.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/log4j.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/mail-1.4.1.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-bridges.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-java.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-taglib.jar
Notice how there is now an icefaces.jar AND an icefaces-3.3.0.jar?
I'm pretty sure that this is the problem. Just wanted to let you know
this, in case it is obvious to you why the second build invoked from
within eclipse that way might cause the icefaces.jar to get deployed
instead of the icesfaces-3.3.0.jar.
Anyway, I will be investigating further to figure out why, but I was
hoping you might already know the answer as you often do :-D
- Vernon
On Thu, Nov 7, 2013 at 1:06 PM, Neil Griffin from liferay.com
<forums@liferay.com> wrote:
> When you get a chance, please upgrade to the new Liferay IDE 2.0 M2 version
> and let us know if you still have the problem. BTW, it will let you create
> projects for Ant+Ivy or Maven.
>
>
> To view the thread, follow the link below:
> https://www.liferay.com/community/forums/-/message_boards/view_message/31235974
> --
> Liferay.com
I think I was able to reproduce his error.
The second time that the build occurs in eclipse when he choses RIght
click Test-portlet -> Liferay -> SDK -> all
I get this in the WEB-INF/lib of the deployed portlet:
$ ls ./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/*.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/FastInfoset-1.2.12.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/activation-1.1.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-beanutils.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-collections.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-digester.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-lang.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/commons-logging.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/el-api-1.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-ace-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces-ace.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icefaces.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/icepush-3.3.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/javax.faces-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jboss-el-2.0.1.GA.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jboss-el.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-api-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-api.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-impl-2.1.21.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsf-impl.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/jsp-api-2.0.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-api-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-api.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-impl-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-bridge-impl.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-portal-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-portal.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-util-3.2.4-ga5-SNAPSHOT.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/liferay-faces-util.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/log4j-extras.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/log4j.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/mail-1.4.1.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-bridges.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-java.jar
./liferay-portal-6.2.0-jsf-2.1/tomcat-7.0.42/webapps/Test-portlet/WEB-INF/lib/util-taglib.jar
Notice how there is now an icefaces.jar AND an icefaces-3.3.0.jar?
I'm pretty sure that this is the problem. Just wanted to let you know
this, in case it is obvious to you why the second build invoked from
within eclipse that way might cause the icefaces.jar to get deployed
instead of the icesfaces-3.3.0.jar.
Anyway, I will be investigating further to figure out why, but I was
hoping you might already know the answer as you often do :-D
- Vernon
On Thu, Nov 7, 2013 at 1:06 PM, Neil Griffin from liferay.com
<forums@liferay.com> wrote:
> When you get a chance, please upgrade to the new Liferay IDE 2.0 M2 version
> and let us know if you still have the problem. BTW, it will let you create
> projects for Ant+Ivy or Maven.
>
>
> To view the thread, follow the link below:
> https://www.liferay.com/community/forums/-/message_boards/view_message/31235974
> --
> Liferay.com