[ https://issues.jboss.org/browse/JBIDE-6317?page=com.atlassian.jira.plugin... ] Snjezana Peco updated JBIDE-6317: --------------------------------- Fix Version/s: 3.3.x (was: 3.2.x) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-6317?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-6317: -------------------------------------------- Talking with Aslak reminded me there is actually a more than one kind of "launch" to support. Need to consider what we would like/spend time on. Some of these might overlap/"be identical" in the implementation, more investigation needed. A. Run arquillian test with the default profile. (i.e. no customization, just what would happen if you do Run As > JUnit/Testng test B. Run arquillian test with specific named profile (i.e. pass in -Darquillian.launch=<name of profile in arq configuration> to the launch.) C. Run arquillian against one of the servers loaded in Eclipse (generate an arquillian.properties/xml and pass in via -Darquillian.properties|xml property + -Darquillian.launch=<unique name> or pass in enough -Darquillian.XXX properties to redefine a server and select it for the launch). Link from Alsak that "documents" these options https://github.com/arquillian/arquillian-core/commit/9d3b82f736b7ab540793... One problem no matter what option here is that the classpath is fully controlled by maven - not sure we can fix that. For now just rely on user to manually select the right maven profile before hand. Down the road (this might need its own launch config type) we could do the proper classpath resolution at test launch time instead of project wide. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-6317?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-6317: -------------------------------------------- My current thinking is that A+B would be a great start. A: already supported - just normal junit launch. B: add an Arquillian tab to testng/junit launches that adds -Darquillian.launch=<name> based on selection on the launch, if possible maybe pop up some UI to let user select which profile if nothing specified ? Maybe, Make a Run As > Run Arquillian launch detector which will figure out if its a junit or testng launch that is relavant and show which profile names that are relevant. C: could probably be done similar to B, just more options to fill in. WDYT? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira