[
https://issues.jboss.org/browse/JBIDE-17112?page=com.atlassian.jira.plugi...
]
Fred Bricon edited comment on JBIDE-17112 at 5/6/14 5:41 AM:
-------------------------------------------------------------
So basically, adding the Portlet Facet fails here because the Web Facet has not been
added.
There are multiple problems here, some on the gatein projects side, some on the
m2e/portlet integration side :
*m2e/portlet integration* :
* should not try to add the Portlet Facet if the Web Facet is not installed.
* errors should not pop up to the UI, but should be converted to error markers instead
*gatein projects* :
* Web Facet is not installed because projects use web.xml 3.0 AND maven-compiler-plugin
configuration is overridden to use 1.5. Since Web 3.0 requires 1.6, the constraint is not
met, the Facet can't be installed (which in turn prevents the Java facet to be
installed apparently). Why do you need to downgrade the java version in the first place?
If you *really* *really* do need to (remember even 1.6 is EOL'ed), then you should
also downgrade the web.xml version to 2.5
* I have several projects not compiling because of missing jdom:jdom:1.1.1 (jboss and exo
repositories are configured). Where is it supposed to come from?
* Some JSPs don't compile in eclipse, because dependencies have not been added to the
pom (jsp-api, exo apis...). I understand they're not required to compile the java
classes, but if you want to have your projects error-free in eclipse, you *need* to add
the required deps to your war projects.
was (Author: fbricon):
So basically, adding the Portlet Facet fails here because the Web Facet has not been
added.
There are multiple problems here, some on the gatein projects side, some on the
m2e/portlet integration side :
*m2e/portlet integration* :
* should not try to add the Portlet Facet if the Web Facet is not installed.
* errors should not pop up to the UI, but should be converted to error markers instead
*gatein projects* :
* Web Facet is not installed because projects use web.xml 3.0 AND maven-compiler-plugin
configuration is overridden to use 1.5. Since Web 3.0 requires 1.6, the constraint is not
met, the Facet can't be installed. Why do you need to downgrade the java version in
the first place? If you *really* *really* do need to (remember even 1.6 is EOL'ed),
then you should also downgrade the web.xml version to 2.5
* I have several projects not compiling because of missing jdom:jdom:1.1.1 (jboss and exo
repositories are configured). Where is it supposed to come from?
* Some JSPs don't compile in eclipse, because dependencies have not been added to the
pom (jsp-api, exo apis...). I understand they're not required to compile the java
classes, but if you want to have your projects error-free in eclipse, you *need* to add
the required deps to your war projects.
Errors on importing GateIn Portal as Maven project
---------------------------------------------------
Key: JBIDE-17112
URL:
https://issues.jboss.org/browse/JBIDE-17112
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven, portal-gatein
Environment: - Fedora 20
- OpenJDK 1.7.0_51 (latest from Fedora 20)
- JBoss Developer Studio 8.0.0.Beta1 (Beta1-v20140408-2350-B93)
Reporter: Juraci Paixão Kröhling
Assignee: Fred Bricon
Fix For: 4.2.0.Beta2
Attachments: jbosstools-diagnostics-20140415084349.zip
When trying to import "GateIn Portal" as an "Existing Maven Project"
in JBoss Developer Studio Beta with EAP, I see an error dialog with two messages:
- "JBoss Core Portlet 2.0 requires Java 1.5 or newer"
- "JBoss Core Portlet 2.0 requires Dynamic Web Module 2.5 or newer"
Steps to reproduce:
- Install JBoss Developer Studio with EAP
- Import "Existing Maven Project", selecting the root of the GateIn clone (ex:
https://github.com/jpkrohling/gatein-portal)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)