[jbosstools-issues] [JBoss JIRA] (JBDS-2847) Java EE 7 Tech Preview

[Xavier Coulon (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990044#comment-12990044 ] 

Xavier Coulon edited comment on JBDS-2847 at 8/5/14 8:17 AM:
-------------------------------------------------------------

hello [~mmalina],

You should be able to start working on this issue right now. 
Please note that the javaee7 samples on github use Groovy for some tests with Spock (as declared in the parent pom.xml), so you may have issues with Eclipse out-of-the-box. You have two options:
- install the Groovy/JDT plugin
- comment out the maven-compiler-plugin that uses the groovy-eclipse-compiler, so you don't need to install anything on your JBDS  
- the parent pom.xml needs to be updated manually, by adding the following line
{quote}
@@ -264,6 +264,7 @@
                         <groupId>org.codehaus.groovy</groupId>
                         <artifactId>groovy-eclipse-compiler</artifactId>
                         <version>2.8.0-01</version>
+                       <extensions>true</extensions>
{quote}
- then import the projects you want to test using {{File>Import>Existing Maven Projects}}.
If you have errors during the import, such as:
{quote}
- Plugin execution not covered by lifecycle configuration: 
	 org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile (execution: 
	 default-testCompile, phase: test-compile)
- Plugin execution not covered by lifecycle configuration: 
	 org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (execution: default-
	 compile, phase: compile)
{quote}
then just mark them as permanently ignored.

If the projects import ends up with misconfigured build paths, then remove the projects, then from the command line, remove the .project and .classpath files, along with the .settings folder in *each* project, then import the projects again. This _should_ work fine.



[~maxandersen] also asked that we should test against Wildfly 8.1 using Java 8 (as mentionned in JBDS-2919).




was (Author: xcoulon):
hello [~mmalina],

You should be able to start working on this issue right now. 
Please note that the javaee7 samples on github use Groovy for some tests with Spock (as declared in the parent pom.xml), so you may have issues with Eclipse out-of-the-box. You have two options:
- install the Groovy/JDT plugin
- comment out the maven-compiler-plugin that uses the groovy-eclipse-compiler, so you don't need to install anything on your JBDS  

[~maxandersen] also asked that we should test against Wildfly 8.1 using Java 8 (as mentionned in JBDS-2919).



> Java EE 7 Tech Preview
> ----------------------
>
>                 Key: JBDS-2847
>                 URL: https://issues.jboss.org/browse/JBDS-2847
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: requirements
>            Reporter: Burr Sutter
>            Assignee: Xavier Coulon
>              Labels: JBDS80_Approved_Scope
>             Fix For: 8.0.0.CR1
>
>
> Successfully/cleanly import the Java EE 7 Samples that have been migrated/ported to Wildfly
> https://github.com/javaee-samples/javaee7-samples
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)