[
https://issues.jboss.org/browse/JBIDE-14525?page=com.atlassian.jira.plugi...
]
Aslak Knutsen commented on JBIDE-14525:
---------------------------------------
This looks really nice..
A little suggestion, I'll open a new case if needed, but..
How about grouping each dependent class for the same package in a addClasses(X, Y) instead
of using addClass on all individually. Just makes the Deployment a bit more visually
'appealing'. In theory addClasses could be more optimized when adding multiple in
one call.
{code}
org.test.a.X
org.test.a.Y
org.test.b.Z
.addClasses(X, Y)
.addClass(Z)
{code}
?
"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
Labels: new_and_noteworthy
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 was sent by Atlassian JIRA
(v6.3.1#6329)