[
https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi...
]
Mickael Istria updated JBIDE-13869:
-----------------------------------
Assignee: Max Rydahl Andersen (was: Mickael Istria)
Here is another solution:
3) Set up jobs doing this
{code}
cd tests/
mvn clean verify -Punified
-Djbosstools-nightly=http://download.jboss.org/jbosstools/updates/stable/juno
(...TARGET_PLATFORM options...)
{code}
This will only re-build tests and run them. All other stuff will come from specified
sources.
Re-assigning it to you [~maxandersen] for feedback.
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/Releng
Reporter: Max Rydahl Andersen
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 4.0.2.Final, 4.1.0.Alpha2
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