[
https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi...
]
Mickael Istria edited comment on JBIDE-13869 at 10/7/13 8:35 AM:
-----------------------------------------------------------------
When
https://bugs.eclipse.org/bugs/show_bug.cgi?id=386988 gets fixed, it will be necessary
to apply
https://github.com/jbosstools/jbosstools-build/pull/111 if we want to be able to
run surefire plugin on existing application.
By the way, I'm not sure forcing the testApplication/testProduct to their default
values adds anything useful to the configuration. I guess it could be removed now.
was (Author: mickael_istria):
When
https://bugs.eclipse.org/bugs/show_bug.cgi?id=386988 gets fixed, it will be
necessary to apply
https://github.com/jbosstools/jbosstools-build/pull/108 if we want to
be able to run surefire plugin on existing application.
By the way, I'm not sure forcing the testApplication/testProduct to their default
values adds anything useful to the configuration. I guess it could be removed now.
Find a way to run testsuite against existing builds but with
different TP without requiring publishing
------------------------------------------------------------------------------------------------------
Key: JBIDE-13869
URL:
https://issues.jboss.org/browse/JBIDE-13869
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Reporter: Max Rydahl Andersen
Assignee: Mickael Istria
Priority: Critical
Fix For: 4.1.1.Final, 4.2.0.Alpha1
Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild
everything again.
Possible options:
1) Create new testsuite that depends on all other testsuites and run them in surefire
test.
2) use something else than surefire to run the already built testsuites.
--
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