[
https://issues.jboss.org/browse/JBIDE-14528?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-14528:
---------------------------------------
{quote}
Would it be possible to continue the method chaining?
{quote}
I could try. Where would you like to continue the method chaining? After the last method
or after the last addClass/addClasses method?
{quote}
I wouldn't just 'randomly' add it to any addClass(s) method in there, as at
least personally I tend to group them based on 'something'.
Maybe something like, if there is a addClass that has classes from the same package as the
missing one then you could add it there.
{quote}
That is doable. I suppose you mean addClasses (we can change addClass to addClasses)
We can also add options to the "Add <class> to deployment" dialog so that
a user can
- select a separate method invocation (the current feature)
- method chaining
- use the current addClasses/addClass method(s) if possible
Do you have a larger example project that I can use to test different features?
{quote}
Would it be possible to scan the TestClass in this case for 'already' depending
classes and add them to the 'Classes' list in the Deployment Generator view? And
since you 'eventually' know that Manager is not enough, but you also need Resource
and SuperManager, could you add those by default as well?
I can create new issues if you want..
{quote}
I think you have already created a jira for that feature: JBIDE-14525
Add 'quick fix' to 'warning type not in deployment'
---------------------------------------------------
Key: JBIDE-14528
URL:
https://issues.jboss.org/browse/JBIDE-14528
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: testing-tools
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Fix For: 4.2.0.Alpha1
Attachments: dependentClasses.zip
Given a test case with a deployment method
When there is a missing Type reference from the TestClass that is not found in the
deployment
Then the Warning should provide a 'quick fix' option to add the missing type
--
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