[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22305:
-------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.2.Final)
> automate process for fetching latest target platform mirrors
> ------------------------------------------------------------
>
> Key: JBIDE-22305
> URL: https://issues.jboss.org/browse/JBIDE-22305
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, updatesite, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 4.4.3.AM1
>
> Attachments: git.diff.txt
>
>
> Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names.
> Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace.
> Thus for webtools we might simply define:
> webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do...
> and we'd end up with:
> http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8....
> * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr
> 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p...
> 2. when all children are done, a downstream job can runs TP update & validation against new .target files
> * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> * parse that into a list of URLs
> * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files
> * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs
> * resulting edited .target files will remain in the workspace, and we can then run
> * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u...
> * when done if success:
> * ideally, generate a PR and attach link in email to jbosstools-dev@
> * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR
> * email should includes boilerplate text to send mail to list announcing new change for review
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4096) profile self is not registered?
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-4096?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-4096:
------------------------------
Fix Version/s: 10.3.0.AM1
(was: 10.2.0.GA)
> profile self is not registered?
> -------------------------------
>
> Key: JBDS-4096
> URL: https://issues.jboss.org/browse/JBDS-4096
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 10.2.0.AM1
> Environment: {code}
> Red Hat JBoss Developer Studio
> Version: 10.2.0.AM1
> Build id: AM1-v20160923-1714-B6096
> Build date: 20160923-1714
> $➔ uname -a
> Linux t540p-f24-vm01 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> [14:00:12] nboldt@t540p-f24-vm01:~/devstudio-10.2.0.AM1
> $➔ java -version
> openjdk version "1.8.0_65"
> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> {code}
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Fix For: 10.3.0.AM1
>
> Attachments: profile-self-is-not-registered.png
>
>
> Tried to install the m2e-wtp-jsf connector from Central and got this:
> {code}Profile id _SELF_ is not registered.
> java.lang.IllegalArgumentException: Profile id _SELF_ is not registered.
> at org.eclipse.equinox.internal.p2.director.ProfileChangeRequest.createByProfileId(ProfileChangeRequest.java:46)
> at org.eclipse.equinox.p2.operations.InstallOperation.computeProfileChangeRequest(InstallOperation.java:74)
> at org.eclipse.equinox.p2.operations.ProfileChangeOperation.makeResolveJob(ProfileChangeOperation.java:165)
> at org.eclipse.equinox.p2.operations.ProfileChangeOperation.resolveModal(ProfileChangeOperation.java:113)
> at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.resolveInstall(PrepareInstallProfileJob.java:268)
> at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:120)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> eclipse.buildId=unknown
> java.version=1.8.0_65
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product -debug -console -consolelog
> {code}
> !profile-self-is-not-registered.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4096) profile self is not registered?
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-4096?page=com.atlassian.jira.plugin.... ]
Fred Bricon reassigned JBDS-4096:
---------------------------------
Assignee: Nick Boldt (was: Fred Bricon)
> profile self is not registered?
> -------------------------------
>
> Key: JBDS-4096
> URL: https://issues.jboss.org/browse/JBDS-4096
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 10.2.0.AM1
> Environment: {code}
> Red Hat JBoss Developer Studio
> Version: 10.2.0.AM1
> Build id: AM1-v20160923-1714-B6096
> Build date: 20160923-1714
> $➔ uname -a
> Linux t540p-f24-vm01 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> [14:00:12] nboldt@t540p-f24-vm01:~/devstudio-10.2.0.AM1
> $➔ java -version
> openjdk version "1.8.0_65"
> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> {code}
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.3.0.AM1
>
> Attachments: profile-self-is-not-registered.png
>
>
> Tried to install the m2e-wtp-jsf connector from Central and got this:
> {code}Profile id _SELF_ is not registered.
> java.lang.IllegalArgumentException: Profile id _SELF_ is not registered.
> at org.eclipse.equinox.internal.p2.director.ProfileChangeRequest.createByProfileId(ProfileChangeRequest.java:46)
> at org.eclipse.equinox.p2.operations.InstallOperation.computeProfileChangeRequest(InstallOperation.java:74)
> at org.eclipse.equinox.p2.operations.ProfileChangeOperation.makeResolveJob(ProfileChangeOperation.java:165)
> at org.eclipse.equinox.p2.operations.ProfileChangeOperation.resolveModal(ProfileChangeOperation.java:113)
> at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.resolveInstall(PrepareInstallProfileJob.java:268)
> at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:120)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> eclipse.buildId=unknown
> java.version=1.8.0_65
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product -debug -console -consolelog
> {code}
> !profile-self-is-not-registered.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23624) clean up skipTests / swtbot.tests.skip references in integration tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23624?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23624 at 12/1/16 3:09 PM:
-------------------------------------------------------------------
big +1 for this! I didnt test it though. But running tests by default is definitely how it should be, there's no doubt about it IMO.
[~nickboldt] big thanks!
was (Author: adietish):
big +1 for this! I didnt test it though. But running tests by default should definitely be how it is, there's no doubt IMO.
[~nickboldt] big thanks!
> clean up skipTests / swtbot.tests.skip references in integration tests
> ----------------------------------------------------------------------
>
> Key: JBIDE-23624
> URL: https://issues.jboss.org/browse/JBIDE-23624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1
>
>
> Rob said:
> {quote}
> swtbot.test.skip is old and shouldnt exist anymore {quote}
> {code}
> $➔ find.sh . "pom.xml" swtbot.test.skip
> ** [1] ./tests/org.jboss.tools.easymport.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <swtbot.test.skip>false</swtbot.test.skip>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> {code}
> Andre said:
> {quote}
> this seems to make no sense at all. These are tests. Why would you want to skip them by default?{quote}
> {code}
> ** [1] ./tests/org.jboss.tools.ui.bot.ext.test/pom.xml **
> 13-
> 14- <properties>
> 15: <skipTests>true</skipTests>
> 16- </properties>
> 17-</project>
> ** [2] ./tests/pom.xml **
> 22- <junitExtensionsProperties>-Dreddeer.close.shells=${reddeer.close.shells} -Dreddeer.close.welcome.screen=${reddeer.close.welcome.screen} -Dreddeer.disable.maven.download.repo.index.on.startup=${reddeer.disable.maven.download.repo.index.on.startup}</junitExtensionsProperties>
> 23- <integrationTestsSystemProperties>-Dswt.bot.test.record.screencast=${swt.bot.test.record.screencast} -Dorg.eclipse.swtbot.screenshots.dir=${project.build.directory}/screenshots -Dusage_reporting_enabled=false -Dcom.atlassian.connector.eclipse.monitor.usage.first.time=false -Dcom.atlassian.connector.eclipse.monitor.usage.enabled=false ${junitExtensionsProperties}</integrationTestsSystemProperties>
> 24: <skipTests>true</skipTests>
> 25- <test.installPath.OSX></test.installPath.OSX>
> 26- <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository>
> {code}
> There are also three examples of hardcoding skipTests to false, for no obvious reason:
> {code}
> $➔ find.sh . "pom.xml" \<skipTests\>false
> ** [1] ./tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml **
> 19- -->
> 20- <properties>
> 21: <skipTests>false</skipTests>
> 22- <usage_reporting_enabled>false</usage_reporting_enabled>
> 23- <!-- Maven configuration -->
> ** [2] ./tests/org.jboss.tools.arquillian.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <skipTests>false</skipTests>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> ** [3] ./tests/org.jboss.tools.examples.ui.bot.test/pom.xml **
> 30- <jbosstools.test.jboss-eap-7.x.url>http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.0/jboss-eap-7.0.0...</jbosstools.test.jboss-eap-7.x.url>
> 31- <surefire.timeout>18000</surefire.timeout>
> 32: <skipTests>false</skipTests>
> 33- <deployOnServer>true</deployOnServer>
> 34- </properties>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23624) clean up skipTests / swtbot.tests.skip references in integration tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23624?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23624:
------------------------------------------
big +1 for this! I didnt test it though. But running tests by default should definitely be how it is, there's no doubt IMO.
> clean up skipTests / swtbot.tests.skip references in integration tests
> ----------------------------------------------------------------------
>
> Key: JBIDE-23624
> URL: https://issues.jboss.org/browse/JBIDE-23624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1
>
>
> Rob said:
> {quote}
> swtbot.test.skip is old and shouldnt exist anymore {quote}
> {code}
> $➔ find.sh . "pom.xml" swtbot.test.skip
> ** [1] ./tests/org.jboss.tools.easymport.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <swtbot.test.skip>false</swtbot.test.skip>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> {code}
> Andre said:
> {quote}
> this seems to make no sense at all. These are tests. Why would you want to skip them by default?{quote}
> {code}
> ** [1] ./tests/org.jboss.tools.ui.bot.ext.test/pom.xml **
> 13-
> 14- <properties>
> 15: <skipTests>true</skipTests>
> 16- </properties>
> 17-</project>
> ** [2] ./tests/pom.xml **
> 22- <junitExtensionsProperties>-Dreddeer.close.shells=${reddeer.close.shells} -Dreddeer.close.welcome.screen=${reddeer.close.welcome.screen} -Dreddeer.disable.maven.download.repo.index.on.startup=${reddeer.disable.maven.download.repo.index.on.startup}</junitExtensionsProperties>
> 23- <integrationTestsSystemProperties>-Dswt.bot.test.record.screencast=${swt.bot.test.record.screencast} -Dorg.eclipse.swtbot.screenshots.dir=${project.build.directory}/screenshots -Dusage_reporting_enabled=false -Dcom.atlassian.connector.eclipse.monitor.usage.first.time=false -Dcom.atlassian.connector.eclipse.monitor.usage.enabled=false ${junitExtensionsProperties}</integrationTestsSystemProperties>
> 24: <skipTests>true</skipTests>
> 25- <test.installPath.OSX></test.installPath.OSX>
> 26- <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository>
> {code}
> There are also three examples of hardcoding skipTests to false, for no obvious reason:
> {code}
> $➔ find.sh . "pom.xml" \<skipTests\>false
> ** [1] ./tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml **
> 19- -->
> 20- <properties>
> 21: <skipTests>false</skipTests>
> 22- <usage_reporting_enabled>false</usage_reporting_enabled>
> 23- <!-- Maven configuration -->
> ** [2] ./tests/org.jboss.tools.arquillian.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <skipTests>false</skipTests>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> ** [3] ./tests/org.jboss.tools.examples.ui.bot.test/pom.xml **
> 30- <jbosstools.test.jboss-eap-7.x.url>http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.0/jboss-eap-7.0.0...</jbosstools.test.jboss-eap-7.x.url>
> 31- <surefire.timeout>18000</surefire.timeout>
> 32: <skipTests>false</skipTests>
> 33- <deployOnServer>true</deployOnServer>
> 34- </properties>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23624) clean up skipTests / swtbot.tests.skip references in integration tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23624?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23624 at 12/1/16 3:06 PM:
-------------------------------------------------------------------
big +1 for this! I didnt test it though. But running tests by default should definitely be how it is, there's no doubt IMO.
[~nickboldt] big thanks!
was (Author: adietish):
big +1 for this! I didnt test it though. But running tests by default should definitely be how it is, there's no doubt IMO.
> clean up skipTests / swtbot.tests.skip references in integration tests
> ----------------------------------------------------------------------
>
> Key: JBIDE-23624
> URL: https://issues.jboss.org/browse/JBIDE-23624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1
>
>
> Rob said:
> {quote}
> swtbot.test.skip is old and shouldnt exist anymore {quote}
> {code}
> $➔ find.sh . "pom.xml" swtbot.test.skip
> ** [1] ./tests/org.jboss.tools.easymport.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <swtbot.test.skip>false</swtbot.test.skip>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> {code}
> Andre said:
> {quote}
> this seems to make no sense at all. These are tests. Why would you want to skip them by default?{quote}
> {code}
> ** [1] ./tests/org.jboss.tools.ui.bot.ext.test/pom.xml **
> 13-
> 14- <properties>
> 15: <skipTests>true</skipTests>
> 16- </properties>
> 17-</project>
> ** [2] ./tests/pom.xml **
> 22- <junitExtensionsProperties>-Dreddeer.close.shells=${reddeer.close.shells} -Dreddeer.close.welcome.screen=${reddeer.close.welcome.screen} -Dreddeer.disable.maven.download.repo.index.on.startup=${reddeer.disable.maven.download.repo.index.on.startup}</junitExtensionsProperties>
> 23- <integrationTestsSystemProperties>-Dswt.bot.test.record.screencast=${swt.bot.test.record.screencast} -Dorg.eclipse.swtbot.screenshots.dir=${project.build.directory}/screenshots -Dusage_reporting_enabled=false -Dcom.atlassian.connector.eclipse.monitor.usage.first.time=false -Dcom.atlassian.connector.eclipse.monitor.usage.enabled=false ${junitExtensionsProperties}</integrationTestsSystemProperties>
> 24: <skipTests>true</skipTests>
> 25- <test.installPath.OSX></test.installPath.OSX>
> 26- <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository>
> {code}
> There are also three examples of hardcoding skipTests to false, for no obvious reason:
> {code}
> $➔ find.sh . "pom.xml" \<skipTests\>false
> ** [1] ./tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml **
> 19- -->
> 20- <properties>
> 21: <skipTests>false</skipTests>
> 22- <usage_reporting_enabled>false</usage_reporting_enabled>
> 23- <!-- Maven configuration -->
> ** [2] ./tests/org.jboss.tools.arquillian.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <skipTests>false</skipTests>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> ** [3] ./tests/org.jboss.tools.examples.ui.bot.test/pom.xml **
> 30- <jbosstools.test.jboss-eap-7.x.url>http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.0/jboss-eap-7.0.0...</jbosstools.test.jboss-eap-7.x.url>
> 31- <surefire.timeout>18000</surefire.timeout>
> 32: <skipTests>false</skipTests>
> 33- <deployOnServer>true</deployOnServer>
> 34- </properties>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23624) clean up skipTests / swtbot.tests.skip references in integration tests
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23624?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23624:
-------------------------------
Fix Version/s: 4.4.3.AM1
> clean up skipTests / swtbot.tests.skip references in integration tests
> ----------------------------------------------------------------------
>
> Key: JBIDE-23624
> URL: https://issues.jboss.org/browse/JBIDE-23624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Fix For: 4.4.3.AM1
>
>
> Rob said:
> {quote}
> swtbot.test.skip is old and shouldnt exist anymore {quote}
> {code}
> $➔ find.sh . "pom.xml" swtbot.test.skip
> ** [1] ./tests/org.jboss.tools.easymport.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <swtbot.test.skip>false</swtbot.test.skip>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> {code}
> Andre said:
> {quote}
> this seems to make no sense at all. These are tests. Why would you want to skip them by default?{quote}
> {code}
> ** [1] ./tests/org.jboss.tools.ui.bot.ext.test/pom.xml **
> 13-
> 14- <properties>
> 15: <skipTests>true</skipTests>
> 16- </properties>
> 17-</project>
> ** [2] ./tests/pom.xml **
> 22- <junitExtensionsProperties>-Dreddeer.close.shells=${reddeer.close.shells} -Dreddeer.close.welcome.screen=${reddeer.close.welcome.screen} -Dreddeer.disable.maven.download.repo.index.on.startup=${reddeer.disable.maven.download.repo.index.on.startup}</junitExtensionsProperties>
> 23- <integrationTestsSystemProperties>-Dswt.bot.test.record.screencast=${swt.bot.test.record.screencast} -Dorg.eclipse.swtbot.screenshots.dir=${project.build.directory}/screenshots -Dusage_reporting_enabled=false -Dcom.atlassian.connector.eclipse.monitor.usage.first.time=false -Dcom.atlassian.connector.eclipse.monitor.usage.enabled=false ${junitExtensionsProperties}</integrationTestsSystemProperties>
> 24: <skipTests>true</skipTests>
> 25- <test.installPath.OSX></test.installPath.OSX>
> 26- <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository>
> {code}
> There are also three examples of hardcoding skipTests to false, for no obvious reason:
> {code}
> $➔ find.sh . "pom.xml" \<skipTests\>false
> ** [1] ./tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml **
> 19- -->
> 20- <properties>
> 21: <skipTests>false</skipTests>
> 22- <usage_reporting_enabled>false</usage_reporting_enabled>
> 23- <!-- Maven configuration -->
> ** [2] ./tests/org.jboss.tools.arquillian.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <skipTests>false</skipTests>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> ** [3] ./tests/org.jboss.tools.examples.ui.bot.test/pom.xml **
> 30- <jbosstools.test.jboss-eap-7.x.url>http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.0/jboss-eap-7.0.0...</jbosstools.test.jboss-eap-7.x.url>
> 31- <surefire.timeout>18000</surefire.timeout>
> 32: <skipTests>false</skipTests>
> 33- <deployOnServer>true</deployOnServer>
> 34- </properties>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months