[
https://issues.jboss.org/browse/JBIDE-17112?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-17112:
-------------------------------------
So this JIRA will only focus on fixes required in m2e/portlet (don't break the build
if portlet constraints are not meant). The Portal/GateIn team needs to fix the projects
causing these errors, as per GTNPORTAL-3479
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)