[
https://issues.jboss.org/browse/JBIDE-11663?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11663:
----------------------------------------
Fix Version/s: 3.3.0.CR1
(was: 3.3.0.Beta3)
sorry for some reason I completely missed this one.
Why is the swtbot tests not using their own profile instead of system property ?
Both nightly-staging-composite and staging-aggregate profiles
activated automatically for swtbot tests
------------------------------------------------------------------------------------------------------
Key: JBIDE-11663
URL:
https://issues.jboss.org/browse/JBIDE-11663
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta3
Reporter: Lucia Jelinkova
Assignee: Max Rydahl Andersen
Fix For: 3.3.0.CR1
With addition of staging-aggregate profiles there are 4 profiles activated by default
when swtbot.test.skip property is set to "false" (as is used for all swtbot
tests).
As a result, both the nightly and aggregation repositories are added for resolving target
platform.
{code}
[INFO] Adding repository
http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.S...
[INFO] Adding repository
http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/
[INFO] Adding repository
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
[INFO] Adding repository
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli...
[INFO] Adding repository
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/
{code}
Please, remove automatic activation of those profiles when swtbot.test.skip=false. QE
would prefer to specify those profiles on the command line.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira