[
https://issues.jboss.org/browse/JBIDE-16695?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-16695:
---------------------------------------
The issue has been fixed in the master branch.
Could you upgrade to Arquillian 1.1 using the
http://download.jboss.org/jbosstools/updates/nightly/core/master/ update site? That
version is compatible with Eclipse Kepler/Luna and includes a lot of fixes/enhancements.
It isn't necessary to upgrade other parts of Eclipse/JBoss Tools.
{quote}
I just discovered that this behavior also occurs if the @Deployment method is non-static.
{quote}
An Arquillian deployment method must be static. See
https://docs.jboss.org/author/display/ARQ/Deployment+archives
We could add a new problem marker (with a quick fix):
"The method annotated with org.jboss.arquillian.container.test.api.Deployment is not
static"
or something similar that.
Arquillian deployment method detection does not consider Archive
subclasses
---------------------------------------------------------------------------
Key: JBIDE-16695
URL:
https://issues.jboss.org/browse/JBIDE-16695
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing-tools
Affects Versions: 4.1.1.Final
Reporter: Rich DiCroce
Assignee: Snjezana Peco
Fix For: 4.2.0.Beta1
In an Arquillian test class, any method marked @Deployment that returns something other
than Archive is not being detected. For example, this method is not detected by the
tooling, despite the fact that WebArchive extends Archive:
{code}
@Deployment
public static WebArchive createDeployment() {
...code to create deployment here...
}
{code}
As a result, the deployment validation features do not work, and the Arquillian Cruiser
view does not allow the archive to be browsed. Curiously, however, there is no warning
about a missing @Deployment method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira