[
https://issues.jboss.org/browse/JBIDE-14525?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-14525:
---------------------------------------
Since, the compiler doesn't detect all dependent classes, I have changed the way in
which the Arquillian plugin searches dependent classes.
Now Arquillian uses AST to search for all, direct and indirect dependencies.
This way, all dependent classes are found what fixes the issue described at
https://issues.jboss.org/browse/JBIDE-14518?focusedCommentId=12815477&...
The fix includes:
- the "Add Dependent Classes" button when generating a deployment method
- the validation of dependent classes is improved as well as the quickfix for 'type
not in deployment'(JBIDE-14528). I have created a checkbox that enables a user to add
all required dependent classes
- the DependentClassesTest test has been updated
See
http://screencast.com/t/WQfR5KVb.
"Create Arquillian Deployment Method" should scan for
depending classes on add
------------------------------------------------------------------------------
Key: JBIDE-14525
URL:
https://issues.jboss.org/browse/JBIDE-14525
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: testing-tools
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Fix For: 4.2.0.Alpha1
When you add 'classes' to the deployment, the wizard should scan the class for
depending types and suggest them to be added as well.
Example:
https://github.com/aslakknutsen/arquillian-plugin-test
Given the Deployment Wizard
When 'add class' TestHandler
Then suggest to also add SuperTestHandler(SuperClass) and Handler(Field)
--
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