[jbosstools-issues] [JBoss JIRA] Closed: (JBIDE-6612) Helios does not recognize JBoss 6.0 Runtime as JEE6 environment
Dominik Pospisil (JIRA)
jira-events at lists.jboss.org
Wed Aug 25 09:28:11 EDT 2010
[ https://jira.jboss.org/browse/JBIDE-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominik Pospisil closed JBIDE-6612.
-----------------------------------
> Helios does not recognize JBoss 6.0 Runtime as JEE6 environment
> ---------------------------------------------------------------
>
> Key: JBIDE-6612
> URL: https://jira.jboss.org/browse/JBIDE-6612
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS
> Affects Versions: 3.2.0.M1
> Environment: Helios 3.6.0 Linux x64
> All JBoss Tools - 3.2.0.v201007020601N-H408-M1
> Reporter: Thorsten Kunz
> Assignee: Dominik Pospisil
> Priority: Blocker
> Fix For: 3.2.0.M2
>
> Attachments: jbide6612.patch
>
>
> I installed JBoss Tools 3.2.0.v201007020601N-H408-M1 nightly build for Helios.
> Now when I try to create e.g. an EJB Project and set the "Target Runtime" to "JBoss 6.0 Runtime" based on a JBAS 6.0-M3 I loose the option to set the "EJB Module Version" to 3.1. Only 3.0 is available.
> Same is true for "Enterprise Application Projects". I can only set the the "EAR Version" to 5.0. No 6.0 is available.
> Now when I set the "Target Runtime" to my Glassfish 3 Runtime I have all the JEE6 options available.
> This is very unfortunate since it disabled lots of built in JEE6 functionality provided by the native Helios JEE distribution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list