[
https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13869:
----------------------------------------
[~jpeterka] [~vpakan] [~psrna] [~rhopp] [~rawagner]... Guys, this change is for you. Can
you please review the PR and give a try on your favourite use-case?
You'll need to:
* Fetch code from PR
* "mvn install" parent pom
* Use a version of JBDS that matches the stream of the test module (JBDS 8.0.0.Alpha1 for
master, JBDS 7.1.0.Beta1 for 4.1.1 branch).
and run the command as described above. You can also run it on an Eclipse instance
(instead of JBDS), but you'll need to override the
"tycho.surefire.profileName" property to match the right profile.
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