[ https://issues.jboss.org/browse/JBIDE-13347?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-13347: ------------------------------------------- Max, this approach is used when testing swtbot deltaspike tests: 1. test is started (Eclipse is invoked) 2. test imports the test project into test workspace (via UI: Import Dialog (Import->General->Existing Projects into Workspace)) 3. test configures test project (setup runtime and ADD into its classpath deltaspike libraries) 4. test some deltaspike feature on test project The critical is #3. To add deltaspike libraries into project, they have to be somewhere. Note that test projects are not maven projects, because thus I would be test not only deltaspike but also the maven. I am trying to replicate the environment created only with UI in Eclipse/JBDS. Because test projects are not maven projects, your second question is not relevant anymore. Answer to your third question is: Because all our integration tests use shared settings.xml and in this settings.xml are defined only nexus repositories (releases/snapshots), I would have to add maven central repo into this shared settings.xml and I don't like it. Maybe another solution would be adding central nexus repo into pom.xml of the entire deltaspike swtbot tests but this is also not as clean solution as I want. All repos should be defined in settings.xml IMHO. -- 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