[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-12974 at 6/28/13 6:20 AM: ---------------------------------------------------------------- [~nickboldt] The title of this JIRA has long been outdated. At the end of the conversation I was asking why have a new tests site at all - why not just have everything aggregated on the good old coretests site. But... after discussing this with Max today, I forgot about one thing. Our integration tests don't have releases the way unit tests do (as part of JBT releases). We generally only have one branch per major release version (i.e. 4.0.x, 4.1.x...). So we cannot live together with unit tests. So how about this: coretests is setup in parent pom and contains unit tests integrationtests is not setup in parent pom and contains integration tests (but not unit tests) Likewise with soatests and soa integrations tests (aka jbtis integration tests) - JBIDE-13790 will be resolved soon. BTW, I just noticed that http://download.jboss.org/jbosstools/updates/nightly/integrationtests/trunk/ is outdated. Because the jenkins job is disabled. Because the build failed on unsatisfied dep on junit4: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... It very well may be ok now. was (Author: mmalina): [~nickboldt] The title of this JIRA has long been outdated. At the end of the conversation I was asking why have a new tests site at all - why not just have everything aggregated on the good old coretests site. So I'm in favor of removing coretests and renaming integrationtests to coretests. BTW, I just noticed that http://download.jboss.org/jbosstools/updates/nightly/integrationtests/trunk/ is outdated. Because the jenkins job is disabled. Because the build failed on unsatisfied dep on junit4: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Can I enable it and check if this is resolved now? It very well may be. -- 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