[ https://issues.jboss.org/browse/JBIDE-9318?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9318: -------------------------------------------- Did you also import the related server runtime your project depends on ? If that also happened then this for sure is a bug - could you provide a screenshot/error log of what you are seeing? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9318?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9318: -------------------------------------------- Gary, if you could add screenshot/error log outputs that would be good. Just so we know we are actually hunting/finding the same issue. Snejzana, are you able to reproduce this one ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9318?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-9318: -------------------------------------- I can't reproduce the case. I suppose you are talking about the JBoss Portlet Libraries container. It contains the following entry in the .classpath file: ... <classpathentry exported="true" kind="con" path="org.jboss.tools.portlet.core.internal.portletlibrarycontainer.runtime"/> ... that would have to be present when you import a project to a new workspace. The classpath container adds the portlet-api library from the Server Runtime and doesn't have any entry if you haven't added any EPP/GateIn runtime to the project. Check if there is the classpath container in the .classpath file or uncheck the "Empty library containers" filter in the Package Explorer view (click the Package Explorer menu and call Filters). If this container doesn't exist, you can add it by removing and adding Portlet facets again. We can also implement the org.eclipse.jdt.ui.classpathContainerPage ext. point for adding/changing some container entry if you want. If you have created the Portlet container using User Library, you have to create such a library in the new workspace. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9318?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-9318: -------------------------------------- Right. A portlet project requires EPP/GateIn/Portal runtime. The JBoss Portlet Libraries container finds the portlet API within this runtime. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9318?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-9318: -------------------------------------- I am not sure what facet settings you are referring about. I have tried the following: - selected the Package Explore view, clicked the view's menu, chose Filters... and checked the Empty Library Containers entry - created EPP 5.1 Runtime - created a new Seam Web Project - selected EPP 5.1 Runtime - added JBoss Core Portlet, JBoss JSF Portlet and JBoss Seam Portlet facets - finished the wizard - created a new Seam portlet - deployed the project The project includes the JBoss Portlet Libraries container containing the portlet-api-2.0.jar library. See jbide-9318a.png screenshot. - exported the project using the Eclipse Export action - restarted JBDS in a new workspace - selected the Package Explore view, clicked the view's menu, chose Filters... and checked the Empty Library Containers entry - imported the project The project contains errors. There is JBoss EAP Runtime container that is unbound and the JBoss Portlet Libraries container containing no entry. See jbide-9318b.png - created EPP 5.1 Runtime - added that runtime to the project's Build Path The project doesn't contain errors anymore and can be deployed to the server. The JBoss Portlet Libraries container contains the portlet-api-2.0.jar library. See jbide-9318c.png. Any Eclipse project that includes some classpath containers behaves in a similar way when importing in a new workspace. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9318?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9318: -------------------------------------------- Gary - agree with Snjezana - don't understand what facet settings you refer to since there aren't any. It's just about having a runtime selected for the project that has the portal stuff in it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9318?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-9318: -------------------------------------- Gary, Could you please provide us with more details? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9318?page=com.atlassian.jira.plugin... ] Pavol Srna commented on JBIDE-9318: ----------------------------------- I cannot reproduce the issue. Gary, if you still have problems please reopen and provide more details for us. Thanks. Closing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira