October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-920) Create model editor actions test script

by Mario Majernik (JIRA)

Mario Majernik created JBTIS-920: ------------------------------------ Summary: Create model editor actions test script Key: JBTIS-920 URL: https://issues.jboss.org/browse/JBTIS-920 Project: JBoss Tools Integration Stack Issue Type: Enhancement Components: QE, teiid Affects Versions: 4.4.0.Alpha1 Reporter: Mario Majernik Assignee: Mario Majernik Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23286) Improve UI: avoid borders to have clean UI on Windows

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23286?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23286: --------------------------------------- Whiteboard is a field in bugzilla issue. ERT is Eclipse Release Train type of issues here in bugzilla which are created by a bot and their status is updated according to an upstream issue in the Eclipse bugzilla. > Improve UI: avoid borders to have clean UI on Windows > ----------------------------------------------------- > > Key: JBIDE-23286 > URL: https://issues.jboss.org/browse/JBIDE-23286 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Attachments: screenshot-1.png, screenshot-2.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3994) Local jbdevstudio-product build always fails to download sources

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3994?page=com.atlassian.jira.plugin.... ] Martin Malina edited comment on JBDS-3994 at 10/5/16 4:58 AM: -------------------------------------------------------------- I am seeing exactly this issue now: {code} C:\mmalina\git\jbdevstudio-product>mvn clean verify -DBUILD_ALIAS=GA ... [WARNING] No C:\mmalina\git\jbdevstudio-product\site\target\repository\web/site.css found; using default. [INFO] Building zip: C:\mmalina\git\jbdevstudio-product\site\target\com.jboss.devstudio.core.site-10.2.0-SNAPSHOT.zip [INFO] [INFO] --- repository-utils:0.26.0-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) @ com.jboss.devstudio.core.site --- [INFO] Downloaded: jbosstools-aerogear_fe29814b2c5dd2048b67fc566dcbcf2d4006fbf6_sources.zip (495,2 k) [INFO] Downloaded: jbosstools-base_5926ca34e1082a96d67845eca27c93625070f26c_sources.zip (23,6 M) [INFO] Downloaded: jbosstools-browsersim_33883469046757f08797e7cd704214b73c901c41_sources.zip (3,2 M) [INFO] Downloaded: jbosstools-central_34e5692bc2ec0fb3f4ac6561118dfe865f7980f7_sources.zip (8,2 M) [INFO] Downloaded: jbosstools-forge_924261a7241e33ce00dcf88ec0c4236a3ac76142_sources.zip (430,5 k) [INFO] Downloaded: jbosstools-freemarker_8efe69d44fff302cfe1dbd041e2b37a3011299be_sources.zip (381,1 k) [INFO] Downloaded: jbosstools-hibernate_ded2902cba0b08984c491e05e47585718477c042_sources.zip (26,9 M) [INFO] Downloaded: jbosstools-javaee_c16f94e47ef16b10f9e1eac9800f1e47a2f81aad_sources.zip (46,2 M) [INFO] Downloaded: jbosstools-jst_5dd5804049f216374c62e7949f2b80b90cb96c6b_sources.zip (6,3 M) [INFO] Downloaded: jbosstools-livereload_44af911aba916f0e4352a3c6a7961986bbb7d1db_sources.zip (261,2 k) [INFO] Downloaded: jbosstools-openshift_3bd8c0281b900e436c268a666beea022b66d7322_sources.zip (1,9 M) [INFO] Downloaded: jbosstools-server_e23edbfafcd1baa32f8bfe669ba725e487771b43_sources.zip (34,6 M) [INFO] Downloaded: jbosstools-vpe_aadd73ab8f05e6ff244a042c3044ed1099ac64b7_sources.zip (3,5 M) [INFO] Downloaded: jbosstools-webservices_b1a8548974eba2a21ad1415fa8757007d9e02a43_sources.zip (15,4 M) [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] devstudio - Product, Installers .................... SUCCESS [ 0.484 s] [INFO] devstudio - Product Plugins - Core ................. SUCCESS [ 0.031 s] [INFO] com.jboss.devstudio.core ........................... SUCCESS [ 32.332 s] [INFO] com.jboss.devstudio.core.project.examples .......... SUCCESS [ 4.110 s] [INFO] com.jboss.devstudio.core.usage.branding ............ SUCCESS [ 3.985 s] [INFO] com.jboss.devstudio.core.central ................... SUCCESS [ 1.765 s] [INFO] com.jboss.devstudio.core.capabilities .............. SUCCESS [ 3.423 s] [INFO] devstudio - Product Features - Core ................ SUCCESS [ 0.031 s] [INFO] com.jboss.devstudio.core.rpm.feature ............... SUCCESS [ 0.844 s] [INFO] com.jboss.devstudio.core.rpmdeps.feature ........... SUCCESS [ 1.937 s] [INFO] com.jboss.devstudio.core.feature ................... SUCCESS [ 1.001 s] [INFO] com.jboss.devstudio.core.feature.source ............ SUCCESS [ 1.015 s] [INFO] com.jboss.devstudio.core.capabilities.feature ...... SUCCESS [ 1.766 s] [INFO] com.jboss.devstudio.core.capabilities.feature.source SUCCESS [ 1.766 s] [INFO] com.jboss.devstudio.core.site ...................... FAILURE [03:27 min] [INFO] p2-director ........................................ SKIPPED [INFO] com.jboss.devstudio.core.p2.director ............... SKIPPED [INFO] p2-director ........................................ SKIPPED [INFO] installer .......................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 04:56 min [INFO] Finished at: 2016-10-05T10:18:40+02:00 [INFO] Final Memory: 172M/1610M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.26.0-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project com.jboss.devstudio.core.site: Problem occurred checking upstream buildinfo.json files! [ERROR] [ERROR] C:\mmalina\git\jbdevstudio-product\site\target\buildinfo\buildinfo_jbosstools-build-sites.json [ERROR] contains dab8d95f5d7aa20a128f82022e2949336fd41add, but upstream jbosstools-build-sites project's MANIFEST.MF has Eclipse-SourceReferences [ERROR] commitId 91249e8dd7f99e9b517cccf99b201dc263efe11a. [ERROR] [ERROR] If you have locally built projects which are being aggregated here, ensure [ERROR] they are built from the latest SHA from HEAD, not a local topic branch. [ERROR] [ERROR] It's also possible that some recent changes have not yet been built upstream. [ERROR] If that's the case, trigger a build for the jbosstools-build-sites project [ERROR] to ensure that the latest commits have been built and can be aggregated here. [ERROR] [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :com.jboss.devstudio.core.site {code} [~nickboldt], any suggestions what I should try? I was simply building master. Perhaps I should try 10.1.0.GA. Update: I tried to build from the 10.1.0.GA tag and same issue. was (Author: mmalina): I am seeing exactly this issue now: {code} C:\mmalina\git\jbdevstudio-product>mvn clean verify -DBUILD_ALIAS=GA ... [WARNING] No C:\mmalina\git\jbdevstudio-product\site\target\repository\web/site.css found; using default. [INFO] Building zip: C:\mmalina\git\jbdevstudio-product\site\target\com.jboss.devstudio.core.site-10.2.0-SNAPSHOT.zip [INFO] [INFO] --- repository-utils:0.26.0-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) @ com.jboss.devstudio.core.site --- [INFO] Downloaded: jbosstools-aerogear_fe29814b2c5dd2048b67fc566dcbcf2d4006fbf6_sources.zip (495,2 k) [INFO] Downloaded: jbosstools-base_5926ca34e1082a96d67845eca27c93625070f26c_sources.zip (23,6 M) [INFO] Downloaded: jbosstools-browsersim_33883469046757f08797e7cd704214b73c901c41_sources.zip (3,2 M) [INFO] Downloaded: jbosstools-central_34e5692bc2ec0fb3f4ac6561118dfe865f7980f7_sources.zip (8,2 M) [INFO] Downloaded: jbosstools-forge_924261a7241e33ce00dcf88ec0c4236a3ac76142_sources.zip (430,5 k) [INFO] Downloaded: jbosstools-freemarker_8efe69d44fff302cfe1dbd041e2b37a3011299be_sources.zip (381,1 k) [INFO] Downloaded: jbosstools-hibernate_ded2902cba0b08984c491e05e47585718477c042_sources.zip (26,9 M) [INFO] Downloaded: jbosstools-javaee_c16f94e47ef16b10f9e1eac9800f1e47a2f81aad_sources.zip (46,2 M) [INFO] Downloaded: jbosstools-jst_5dd5804049f216374c62e7949f2b80b90cb96c6b_sources.zip (6,3 M) [INFO] Downloaded: jbosstools-livereload_44af911aba916f0e4352a3c6a7961986bbb7d1db_sources.zip (261,2 k) [INFO] Downloaded: jbosstools-openshift_3bd8c0281b900e436c268a666beea022b66d7322_sources.zip (1,9 M) [INFO] Downloaded: jbosstools-server_e23edbfafcd1baa32f8bfe669ba725e487771b43_sources.zip (34,6 M) [INFO] Downloaded: jbosstools-vpe_aadd73ab8f05e6ff244a042c3044ed1099ac64b7_sources.zip (3,5 M) [INFO] Downloaded: jbosstools-webservices_b1a8548974eba2a21ad1415fa8757007d9e02a43_sources.zip (15,4 M) [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] devstudio - Product, Installers .................... SUCCESS [ 0.484 s] [INFO] devstudio - Product Plugins - Core ................. SUCCESS [ 0.031 s] [INFO] com.jboss.devstudio.core ........................... SUCCESS [ 32.332 s] [INFO] com.jboss.devstudio.core.project.examples .......... SUCCESS [ 4.110 s] [INFO] com.jboss.devstudio.core.usage.branding ............ SUCCESS [ 3.985 s] [INFO] com.jboss.devstudio.core.central ................... SUCCESS [ 1.765 s] [INFO] com.jboss.devstudio.core.capabilities .............. SUCCESS [ 3.423 s] [INFO] devstudio - Product Features - Core ................ SUCCESS [ 0.031 s] [INFO] com.jboss.devstudio.core.rpm.feature ............... SUCCESS [ 0.844 s] [INFO] com.jboss.devstudio.core.rpmdeps.feature ........... SUCCESS [ 1.937 s] [INFO] com.jboss.devstudio.core.feature ................... SUCCESS [ 1.001 s] [INFO] com.jboss.devstudio.core.feature.source ............ SUCCESS [ 1.015 s] [INFO] com.jboss.devstudio.core.capabilities.feature ...... SUCCESS [ 1.766 s] [INFO] com.jboss.devstudio.core.capabilities.feature.source SUCCESS [ 1.766 s] [INFO] com.jboss.devstudio.core.site ...................... FAILURE [03:27 min] [INFO] p2-director ........................................ SKIPPED [INFO] com.jboss.devstudio.core.p2.director ............... SKIPPED [INFO] p2-director ........................................ SKIPPED [INFO] installer .......................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 04:56 min [INFO] Finished at: 2016-10-05T10:18:40+02:00 [INFO] Final Memory: 172M/1610M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.26.0-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project com.jboss.devstudio.core.site: Problem occurred checking upstream buildinfo.json files! [ERROR] [ERROR] C:\mmalina\git\jbdevstudio-product\site\target\buildinfo\buildinfo_jbosstools-build-sites.json [ERROR] contains dab8d95f5d7aa20a128f82022e2949336fd41add, but upstream jbosstools-build-sites project's MANIFEST.MF has Eclipse-SourceReferences [ERROR] commitId 91249e8dd7f99e9b517cccf99b201dc263efe11a. [ERROR] [ERROR] If you have locally built projects which are being aggregated here, ensure [ERROR] they are built from the latest SHA from HEAD, not a local topic branch. [ERROR] [ERROR] It's also possible that some recent changes have not yet been built upstream. [ERROR] If that's the case, trigger a build for the jbosstools-build-sites project [ERROR] to ensure that the latest commits have been built and can be aggregated here. [ERROR] [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :com.jboss.devstudio.core.site {code} [~nickboldt], any suggestions what I should try? I was simply building master. Perhaps I should try 10.1.0.GA. > Local jbdevstudio-product build always fails to download sources > ---------------------------------------------------------------- > > Key: JBDS-3994 > URL: https://issues.jboss.org/browse/JBDS-3994 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build > Affects Versions: 10.1.0.AM3 > Environment: 1. No maven local repository; > 2. latest master; > 3. mvn clean install; > 4. Windows 10 Home. > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.x > > Attachments: src-zip-created.png, windows10-version-info.png > > > {code}[INFO] --- repository-utils:0.25.1-SNAPSHOT:generate-repository-facade (generate-facade) @ com.jboss.devstudio.core.site --- > [WARNING] No C:\p\rh\jbds-releng\jbdevstudio-product\site\target\repository\web/site.css found; using default. > [INFO] Building zip: C:\p\rh\jbds-releng\jbdevstudio-product\site\target\com.jboss.devstudio.core.site-10.1.0-SNAPSHOT.zip > [INFO] > [INFO] --- repository-utils:0.25.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) @ com.jboss.devstudio.core.site --- > [INFO] Downloaded: jbosstools-base_6ec1deba2610a94a14d160a7b54ae4f708c40044_sources.zip (23.6 M) > [INFO] Downloaded: jbosstools-browsersim_019a66b4cef24d489c5bad2c0324477e32871222_sources.zip (3.2 M) > [INFO] Downloaded: jbosstools-central_4cef5b7e1c70b213b372fcb5b7ba1c0834e5bff9_sources.zip (8.2 M) > [INFO] Downloaded: jbosstools-forge_6beb7d3b3218e8b02d0497d38915574f9eaf8c1f_sources.zip (430.3 k) > [INFO] Downloaded: jbosstools-freemarker_43ccb5369f1b9bdbd99466755af6158a3c39cea8_sources.zip (379.1 k) > [INFO] Downloaded: jbosstools-hibernate_3e9fb83570c5c7c521f92d3f05c77b67355477d0_sources.zip (26.9 M) > [INFO] Downloaded: jbosstools-javaee_a3e97d0495026b043ff151ac65412ba64bcfc1ff_sources.zip (46.2 M) > [INFO] Downloaded: jbosstools-openshift_810571f6aff04eb4a4b0b986e9ad4c0f16796b25_sources.zip (1.8 M) > [INFO] Downloaded: jbosstools-server_226292c9076be1a5e6f6779e6727fbc5d38af0be_sources.zip (34.6 M) > [INFO] Downloaded: jbosstools-vpe_bd95b9c63a5b05bec19afe483f8224cf07c8aef8_sources.zip (3.5 M) > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] devstudio - Product, Installers .................... SUCCESS [ 0.708 s] > [INFO] devstudio - Product Plugins - Core ................. SUCCESS [ 0.224 s] > [INFO] com.jboss.devstudio.core ........................... SUCCESS [ 12.617 s] > [INFO] com.jboss.devstudio.core.project.examples .......... SUCCESS [ 0.664 s] > [INFO] com.jboss.devstudio.core.usage.branding ............ SUCCESS [ 0.823 s] > [INFO] com.jboss.devstudio.core.central ................... SUCCESS [ 2.297 s] > [INFO] com.jboss.devstudio.core.capabilities .............. SUCCESS [ 0.503 s] > [INFO] devstudio - Product Features - Core ................ SUCCESS [ 0.073 s] > [INFO] com.jboss.devstudio.core.feature ................... SUCCESS [ 1.305 s] > [INFO] com.jboss.devstudio.core.feature.source ............ SUCCESS [ 1.219 s] > [INFO] com.jboss.devstudio.core.capabilities.feature ...... SUCCESS [ 0.406 s] > [INFO] com.jboss.devstudio.core.capabilities.feature.source SUCCESS [ 0.406 s] > [INFO] com.jboss.devstudio.core.site ...................... FAILURE [04:26 min] > [INFO] p2-director ........................................ SKIPPED > [INFO] com.jboss.devstudio.core.p2.director ............... SKIPPED > [INFO] p2-director ........................................ SKIPPED > [INFO] installer .......................................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 05:22 min > [INFO] Finished at: 2016-08-10T19:36:46-07:00 > [INFO] Final Memory: 147M/1484M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.25.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project com.jboss.devstudio.core.site: Problem occurred checking upstream buildinfo.json files! > [ERROR] > [ERROR] C:\p\rh\jbds-releng\jbdevstudio-product\site\target\buildinfo\buildinfo_jbosstools-build-sites.json > [ERROR] contains 91249e8dd7f99e9b517cccf99b201dc263efe11a, but upstream jbosstools-build-sites project's MANIFEST.MF has Eclipse-SourceReferences > [ERROR] commitId 337bd38cb5eb530dd039ddbbaa311fb36161e726. > [ERROR] > [ERROR] If you have locally built projects which are being aggregated here, ensure > [ERROR] they are built from the latest SHA from HEAD, not a local topic branch. > [ERROR] > [ERROR] It's also possible that some recent changes have not yet been built upstream. > [ERROR] If that's the case, trigger a build for the jbosstools-build-sites project > [ERROR] to ensure that the latest commits have been built and can be aggregated here.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23291) If start of container fails on timeout, the status in server view is "Started, Synchronized"

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-23291: --------------------------------------- Summary: If start of container fails on timeout, the status in server view is "Started, Synchronized" Key: JBIDE-23291 URL: https://issues.jboss.org/browse/JBIDE-23291 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Reporter: Aurélien Pupier Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23286) Improve UI: avoid borders to have clean UI on Windows

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23286?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-23286: ----------------------------------------- [~mlabuda] What do you call a "whiteboard"? Where "RHT" should be inserted? What is an ERT? > Improve UI: avoid borders to have clean UI on Windows > ----------------------------------------------------- > > Key: JBIDE-23286 > URL: https://issues.jboss.org/browse/JBIDE-23286 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Attachments: screenshot-1.png, screenshot-2.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22965: ------------------------------------ Two remarks: * we should think about Windows workstation ? How to control traffic on those machines ? Windows firewall ? * It seems to me that DNS traffic is allowed ? I think (at least to mimic the Prudential user case) that common enterprise settings is that all outgoing traffic should be managed by the proxy so DNS resolution should not be done on the dev workstation [~dbocharov] [~lalatendum] Comments ? > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM2 > > Attachments: create_proxy-test_env.sh > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 > + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: > {noformat} > lalatenduM: we exepect customers workstation is configured to porixy server > that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work > lalatenduM: on a customer worksttaion > lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information > lalatenduM: vagrant-registration uses subscription manager for registraton > lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3994) Local jbdevstudio-product build always fails to download sources

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3994?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3994: ------------------------------------- I am seeing exactly this issue now: {code} C:\mmalina\git\jbdevstudio-product>mvn clean verify -DBUILD_ALIAS=GA ... [WARNING] No C:\mmalina\git\jbdevstudio-product\site\target\repository\web/site.css found; using default. [INFO] Building zip: C:\mmalina\git\jbdevstudio-product\site\target\com.jboss.devstudio.core.site-10.2.0-SNAPSHOT.zip [INFO] [INFO] --- repository-utils:0.26.0-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) @ com.jboss.devstudio.core.site --- [INFO] Downloaded: jbosstools-aerogear_fe29814b2c5dd2048b67fc566dcbcf2d4006fbf6_sources.zip (495,2 k) [INFO] Downloaded: jbosstools-base_5926ca34e1082a96d67845eca27c93625070f26c_sources.zip (23,6 M) [INFO] Downloaded: jbosstools-browsersim_33883469046757f08797e7cd704214b73c901c41_sources.zip (3,2 M) [INFO] Downloaded: jbosstools-central_34e5692bc2ec0fb3f4ac6561118dfe865f7980f7_sources.zip (8,2 M) [INFO] Downloaded: jbosstools-forge_924261a7241e33ce00dcf88ec0c4236a3ac76142_sources.zip (430,5 k) [INFO] Downloaded: jbosstools-freemarker_8efe69d44fff302cfe1dbd041e2b37a3011299be_sources.zip (381,1 k) [INFO] Downloaded: jbosstools-hibernate_ded2902cba0b08984c491e05e47585718477c042_sources.zip (26,9 M) [INFO] Downloaded: jbosstools-javaee_c16f94e47ef16b10f9e1eac9800f1e47a2f81aad_sources.zip (46,2 M) [INFO] Downloaded: jbosstools-jst_5dd5804049f216374c62e7949f2b80b90cb96c6b_sources.zip (6,3 M) [INFO] Downloaded: jbosstools-livereload_44af911aba916f0e4352a3c6a7961986bbb7d1db_sources.zip (261,2 k) [INFO] Downloaded: jbosstools-openshift_3bd8c0281b900e436c268a666beea022b66d7322_sources.zip (1,9 M) [INFO] Downloaded: jbosstools-server_e23edbfafcd1baa32f8bfe669ba725e487771b43_sources.zip (34,6 M) [INFO] Downloaded: jbosstools-vpe_aadd73ab8f05e6ff244a042c3044ed1099ac64b7_sources.zip (3,5 M) [INFO] Downloaded: jbosstools-webservices_b1a8548974eba2a21ad1415fa8757007d9e02a43_sources.zip (15,4 M) [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] devstudio - Product, Installers .................... SUCCESS [ 0.484 s] [INFO] devstudio - Product Plugins - Core ................. SUCCESS [ 0.031 s] [INFO] com.jboss.devstudio.core ........................... SUCCESS [ 32.332 s] [INFO] com.jboss.devstudio.core.project.examples .......... SUCCESS [ 4.110 s] [INFO] com.jboss.devstudio.core.usage.branding ............ SUCCESS [ 3.985 s] [INFO] com.jboss.devstudio.core.central ................... SUCCESS [ 1.765 s] [INFO] com.jboss.devstudio.core.capabilities .............. SUCCESS [ 3.423 s] [INFO] devstudio - Product Features - Core ................ SUCCESS [ 0.031 s] [INFO] com.jboss.devstudio.core.rpm.feature ............... SUCCESS [ 0.844 s] [INFO] com.jboss.devstudio.core.rpmdeps.feature ........... SUCCESS [ 1.937 s] [INFO] com.jboss.devstudio.core.feature ................... SUCCESS [ 1.001 s] [INFO] com.jboss.devstudio.core.feature.source ............ SUCCESS [ 1.015 s] [INFO] com.jboss.devstudio.core.capabilities.feature ...... SUCCESS [ 1.766 s] [INFO] com.jboss.devstudio.core.capabilities.feature.source SUCCESS [ 1.766 s] [INFO] com.jboss.devstudio.core.site ...................... FAILURE [03:27 min] [INFO] p2-director ........................................ SKIPPED [INFO] com.jboss.devstudio.core.p2.director ............... SKIPPED [INFO] p2-director ........................................ SKIPPED [INFO] installer .......................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 04:56 min [INFO] Finished at: 2016-10-05T10:18:40+02:00 [INFO] Final Memory: 172M/1610M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.26.0-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project com.jboss.devstudio.core.site: Problem occurred checking upstream buildinfo.json files! [ERROR] [ERROR] C:\mmalina\git\jbdevstudio-product\site\target\buildinfo\buildinfo_jbosstools-build-sites.json [ERROR] contains dab8d95f5d7aa20a128f82022e2949336fd41add, but upstream jbosstools-build-sites project's MANIFEST.MF has Eclipse-SourceReferences [ERROR] commitId 91249e8dd7f99e9b517cccf99b201dc263efe11a. [ERROR] [ERROR] If you have locally built projects which are being aggregated here, ensure [ERROR] they are built from the latest SHA from HEAD, not a local topic branch. [ERROR] [ERROR] It's also possible that some recent changes have not yet been built upstream. [ERROR] If that's the case, trigger a build for the jbosstools-build-sites project [ERROR] to ensure that the latest commits have been built and can be aggregated here. [ERROR] [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :com.jboss.devstudio.core.site {code} [~nickboldt], any suggestions what I should try? I was simply building master. Perhaps I should try 10.1.0.GA. > Local jbdevstudio-product build always fails to download sources > ---------------------------------------------------------------- > > Key: JBDS-3994 > URL: https://issues.jboss.org/browse/JBDS-3994 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build > Affects Versions: 10.1.0.AM3 > Environment: 1. No maven local repository; > 2. latest master; > 3. mvn clean install; > 4. Windows 10 Home. > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.x > > Attachments: src-zip-created.png, windows10-version-info.png > > > {code}[INFO] --- repository-utils:0.25.1-SNAPSHOT:generate-repository-facade (generate-facade) @ com.jboss.devstudio.core.site --- > [WARNING] No C:\p\rh\jbds-releng\jbdevstudio-product\site\target\repository\web/site.css found; using default. > [INFO] Building zip: C:\p\rh\jbds-releng\jbdevstudio-product\site\target\com.jboss.devstudio.core.site-10.1.0-SNAPSHOT.zip > [INFO] > [INFO] --- repository-utils:0.25.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) @ com.jboss.devstudio.core.site --- > [INFO] Downloaded: jbosstools-base_6ec1deba2610a94a14d160a7b54ae4f708c40044_sources.zip (23.6 M) > [INFO] Downloaded: jbosstools-browsersim_019a66b4cef24d489c5bad2c0324477e32871222_sources.zip (3.2 M) > [INFO] Downloaded: jbosstools-central_4cef5b7e1c70b213b372fcb5b7ba1c0834e5bff9_sources.zip (8.2 M) > [INFO] Downloaded: jbosstools-forge_6beb7d3b3218e8b02d0497d38915574f9eaf8c1f_sources.zip (430.3 k) > [INFO] Downloaded: jbosstools-freemarker_43ccb5369f1b9bdbd99466755af6158a3c39cea8_sources.zip (379.1 k) > [INFO] Downloaded: jbosstools-hibernate_3e9fb83570c5c7c521f92d3f05c77b67355477d0_sources.zip (26.9 M) > [INFO] Downloaded: jbosstools-javaee_a3e97d0495026b043ff151ac65412ba64bcfc1ff_sources.zip (46.2 M) > [INFO] Downloaded: jbosstools-openshift_810571f6aff04eb4a4b0b986e9ad4c0f16796b25_sources.zip (1.8 M) > [INFO] Downloaded: jbosstools-server_226292c9076be1a5e6f6779e6727fbc5d38af0be_sources.zip (34.6 M) > [INFO] Downloaded: jbosstools-vpe_bd95b9c63a5b05bec19afe483f8224cf07c8aef8_sources.zip (3.5 M) > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] devstudio - Product, Installers .................... SUCCESS [ 0.708 s] > [INFO] devstudio - Product Plugins - Core ................. SUCCESS [ 0.224 s] > [INFO] com.jboss.devstudio.core ........................... SUCCESS [ 12.617 s] > [INFO] com.jboss.devstudio.core.project.examples .......... SUCCESS [ 0.664 s] > [INFO] com.jboss.devstudio.core.usage.branding ............ SUCCESS [ 0.823 s] > [INFO] com.jboss.devstudio.core.central ................... SUCCESS [ 2.297 s] > [INFO] com.jboss.devstudio.core.capabilities .............. SUCCESS [ 0.503 s] > [INFO] devstudio - Product Features - Core ................ SUCCESS [ 0.073 s] > [INFO] com.jboss.devstudio.core.feature ................... SUCCESS [ 1.305 s] > [INFO] com.jboss.devstudio.core.feature.source ............ SUCCESS [ 1.219 s] > [INFO] com.jboss.devstudio.core.capabilities.feature ...... SUCCESS [ 0.406 s] > [INFO] com.jboss.devstudio.core.capabilities.feature.source SUCCESS [ 0.406 s] > [INFO] com.jboss.devstudio.core.site ...................... FAILURE [04:26 min] > [INFO] p2-director ........................................ SKIPPED > [INFO] com.jboss.devstudio.core.p2.director ............... SKIPPED > [INFO] p2-director ........................................ SKIPPED > [INFO] installer .......................................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 05:22 min > [INFO] Finished at: 2016-08-10T19:36:46-07:00 > [INFO] Final Memory: 147M/1484M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.25.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project com.jboss.devstudio.core.site: Problem occurred checking upstream buildinfo.json files! > [ERROR] > [ERROR] C:\p\rh\jbds-releng\jbdevstudio-product\site\target\buildinfo\buildinfo_jbosstools-build-sites.json > [ERROR] contains 91249e8dd7f99e9b517cccf99b201dc263efe11a, but upstream jbosstools-build-sites project's MANIFEST.MF has Eclipse-SourceReferences > [ERROR] commitId 337bd38cb5eb530dd039ddbbaa311fb36161e726. > [ERROR] > [ERROR] If you have locally built projects which are being aggregated here, ensure > [ERROR] they are built from the latest SHA from HEAD, not a local topic branch. > [ERROR] > [ERROR] It's also possible that some recent changes have not yet been built upstream. > [ERROR] If that's the case, trigger a build for the jbosstools-build-sites project > [ERROR] to ensure that the latest commits have been built and can be aggregated here.{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3986) support building devstudio on windows

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3986?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3986: ------------------------------------- [~dgolovin], no, what I was seeing last time I reported here was something different - notice the strange path '\tmp\jbdevstudio-product-bd00bc238f6d35b895b182cdfe07da5e6b62a215.zip' But now I'm seeing the other issue, yes. I will report there. > support building devstudio on windows > ------------------------------------- > > Key: JBDS-3986 > URL: https://issues.jboss.org/browse/JBDS-3986 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.1.0.AM3 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 10.2.0.AM2 > > > Support building devstudio on windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23290) Move parent pom to AM2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23290?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-23290: ------------------------------------- Assignee: Nick Boldt > Move parent pom to AM2 > ---------------------- > > Key: JBIDE-23290 > URL: https://issues.jboss.org/browse/JBIDE-23290 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > > Parent pom [1] and hence all the builds still show AM1, but we're already one week into sprint 121 = AM2. I could just create a PR for the change. But I wonder what happened. Anything went wrong? This change is supposed to be part of the release process after each sprint, no? > [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23290) Move parent pom to AM2

by Martin Malina (JIRA)

Martin Malina created JBIDE-23290: ------------------------------------- Summary: Move parent pom to AM2 Key: JBIDE-23290 URL: https://issues.jboss.org/browse/JBIDE-23290 Project: Tools (JBoss Tools) Issue Type: Task Components: build Affects Versions: 4.4.2.AM2 Reporter: Martin Malina Priority: Blocker Parent pom [1] and hence all the builds still show AM1, but we're already one week into sprint 121 = AM2. I could just create a PR for the change. But I wonder what happened. Anything went wrong? This change is supposed to be part of the release process after each sprint, no? [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2016