[
https://jira.jboss.org/jira/browse/CDITCK-85?page=com.atlassian.jira.plug...
]
Pete Muir updated CDITCK-85:
----------------------------
Summary: CDI TCK should have support for Java EE Web Profile via groups (was: CDI TCK
should have support for non (full) Java EE Impls via groups)
We won't (can't) target undefined profiles/environments :-) Therefore the TCK will
target EE full profile and EE web profile until other profiles are defined.
Note that although we define a "standalone" mode today (only testing the 299
impl with no tests which require an environment) this is only a developer convenience, as
299 is not currently *defined* as a standalone *spec*.
CDI TCK should have support for Java EE Web Profile via groups
--------------------------------------------------------------
Key: CDITCK-85
URL:
https://jira.jboss.org/jira/browse/CDITCK-85
Project: CDI TCK
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Tests
Affects Versions: 1.0.0.GA
Environment: All
Reporter: Kyle Grucci
Fix For: 1.0.1.CR1, 1.1.0.CR1
The Web Profile spec falls under the Java EE 6 JSR which just went final. Since CDI is a
requirement of the EE Web Profile, the CDI TCK must be able to run against it (ie it
can't assume full EE and thus ear support). This is currently not the case since the
TCK contains some ear files and some tests which rely upon them. At the very least it
probably makes sense to have a second testsuite XML file which doesn't assume full EE.
Otherwise impls of CDI which are not Full EE impls cannot run and pass the CDI TCK since
the current testsuite xml file contains some ears.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira