May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24301) Error while building jbosstools-openshift-4.4.3

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24301 at 5/11/17 12:27 PM: -------------------------------------------------------------------- [~jyoti-jboss] did you follow my steps to the letter? I have no other explanation than that you didnt, can't explain how you could end up having a directory {code} jbosstools-build-jbosstools-4.4.3.x {code} Please do exactly as told above, nothing else. You should end up have a directory {code} jbosstools-build {code} and within that directory, a git repository that's checked out in the master branch, no 4.4.3.x branch, no jbosstools-build-jbosstools-4.4.3.x directory (that you even have 2 within each other). was (Author: adietish): [~jyoti-jboss] did you follow my steps to the letter? I have no other explanation than that you didnt, can't explain how you could end up having a directory {code} jbosstools-build-jbosstools-4.4.3.x {code} Please do exactly as told above, nothing else. You should end up have a directory jbosstools-build, checked out in the master branch, no 4.4.3.x branch, no jbosstools-build-jbosstools-4.4.3.x directory (that you even have 2 within each other). > Error while building jbosstools-openshift-4.4.3 > ----------------------------------------------- > > Key: JBIDE-24301 > URL: https://issues.jboss.org/browse/JBIDE-24301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.3.Final > Reporter: jyoti tumsare > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM1 > > Attachments: Error.PNG, issues.PNG, issues.txt, jbosstools-build.png, org.jboss.ide.eclipse.as.management.as7.png, target-platform.png > > > To build jbosstools-openshift-4.4.3 I followed following steps > 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3. > 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found". > 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24301) Error while building jbosstools-openshift-4.4.3

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24301: ------------------------------------------ [~jyoti-jboss] did you follow my steps to the letter? I have no other explanation than that you didnt, can't explain how you could end up having a directory {code} jbosstools-build-jbosstools-4.4.3.x {code} Please do exactly as told above, nothing else. You should end up have a directory jbosstools-build, checked out in the master branch, no 4.4.3.x branch, no jbosstools-build-jbosstools-4.4.3.x directory (that you even have 2 within each other). > Error while building jbosstools-openshift-4.4.3 > ----------------------------------------------- > > Key: JBIDE-24301 > URL: https://issues.jboss.org/browse/JBIDE-24301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.3.Final > Reporter: jyoti tumsare > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM1 > > Attachments: Error.PNG, issues.PNG, issues.txt, jbosstools-build.png, org.jboss.ide.eclipse.as.management.as7.png, target-platform.png > > > To build jbosstools-openshift-4.4.3 I followed following steps > 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3. > 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found". > 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24438) JMX connection from OpenShift Server Adapter is not working for OpenSHift instance without port

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-24438: --------------------------------------- Summary: JMX connection from OpenShift Server Adapter is not working for OpenSHift instance without port Key: JBIDE-24438 URL: https://issues.jboss.org/browse/JBIDE-24438 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.4.Final Reporter: Aurélien Pupier Fix For: 4.5.0.AM1 such as open.paas.redhat.com {noformat} java.io.IOException: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324) at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113) at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out at org.jolokia.client.J4pClient.mapException(J4pClient.java:330) at org.jolokia.client.J4pClient.execute(J4pClient.java:198) at org.jolokia.client.J4pClient.execute(J4pClient.java:168) at org.jolokia.client.J4pClient.execute(J4pClient.java:117) at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311) ... 4 more Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:150) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55) at org.jolokia.client.J4pClient.execute(J4pClient.java:190) ... 7 more Caused by: java.net.SocketTimeoutException: connect timed out at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at sun.security.ssl.SSLSocketImpl.connect(Unknown Source) at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337) at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141) ... 18 more {noformat} we can notice that the url used is https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c... althouth it shoul dnot contain the port 8443 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23963) Create and use Neon.3 target platform

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23963?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23963. -------------------------------- Verified. Devstudio is running fine with TP 4.63.0.Final. The only problem is that a remediation page is shown during installation of BYOE/Abridged. It is a known issue which should be solved when we solve FUSETOOLS-2353. Closing this jira. > Create and use Neon.3 target platform > ------------------------------------- > > Key: JBIDE-23963 > URL: https://issues.jboss.org/browse/JBIDE-23963 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.4.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.4.Final > > Attachments: Screenshot_2017-03-24_11-10-30.png > > > Once available in March, we should move up to Neon.3 > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > devstudio tp, > central tp; > jbt-build-sites (and parent pom), > devstudio site build (and devstudio root pom); > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24385) Change www.qa to devstudio.redhat.com on CCI jobs

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24385?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24385. -------------------------------- Verified. I didn't found any occurence of qa.jboss.com > Change www.qa to devstudio.redhat.com on CCI jobs > ------------------------------------------------- > > Key: JBIDE-24385 > URL: https://issues.jboss.org/browse/JBIDE-24385 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > Nick can you please change all www.qa downloads to devstudio.redhat.com globally for all jobs on CCI ? thank you -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4379) switch jobs to use openjdk-1.8 instead of jdk1.8

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4379?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4379. ------------------------------ I updated few jobs which were using default jdk and one integration test. {code} cd ./cache/https/dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio grep -R "<jdk>" ./**/config.xml | grep -v "open" ./view/devstudio_integration_tests/job/devstudio.buildflow.it.smoke/config.xml: <jdk>(Default)</jdk> ./view/devstudio_integration_tests/job/usage.test/config.xml: <jdk>(Default)</jdk> ./view/devstudio_rpm_tests/job/rpm_install_base_devstudio.weekly/config.xml: <jdk>(Default)</jdk> ./view/devstudio_rpm_tests/job/rpm_install_base_eclipse46_devstudio.weekly/config.xml: <jdk>(Default)</jdk> ./view/devstudio_rpm_tests/job/rpm_install_devstudio.weekly/config.xml: <jdk>(Default)</jdk> ./view/devstudio_rpm_tests/job/rpm_ldd.weekly/config.xml: <jdk>(Default)</jdk> ./view/devstudio_rpm_tests/job/rpm_rh_central_IS_test.weekly/config.xml: <jdk>(Default)</jdk> ./view/devstudio_rpm_tests/job/rpm_rh_central_test.weekly/config.xml: <jdk>(Default)</jdk> ./view/devstudio_rpm_tests/job/rpm_rpmlint_test.weekly/config.xml: <jdk>(Default)</jdk> ./view/jbosstools-releng/job/devstudio.cve.report/config.xml: <jdk>(Default)</jdk> ./view/jbosstools-releng/job/devstudio.cve.report-merged/config.xml: <jdk>(Default)</jdk> ./view/jbosstools-releng/job/jbosstools-releng-push-to-dev-stable-00-releng-request-email/config.xml: <jdk>(Default)</jdk> # Find all values stored in hudson.matrix.JDKAxis excluding open jdk grep -RPzo "(?s)<hudson.matrix.JDKAxis>.*?</hudson.matrix.JDKAxis>" ./**/config.xml | grep -a "<string>" | grep -via "open" <string>jdk1.8</string> grep -R "jdk1." ./**/config.xml ./view/devstudio_integration_tests/job/forge.it.weekly/config.xml: <string>jdk1.8</string> {code} I haven't been able to use scripts stored in jbdevstudio-ci \[1\] (pom-sync.xml, ...) so I used config.xmls which were stored in cache folder. Please, let me know if you want me to backup configuration of modified jobs in jbdevstudio-ci repository. \[1\] https://github.com/jbdevstudio/jbdevstudio-ci This jira can be closed. > switch jobs to use openjdk-1.8 instead of jdk1.8 > ------------------------------------------------ > > Key: JBDS-4379 > URL: https://issues.jboss.org/browse/JBDS-4379 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Affects Versions: 10.4.0.GA, 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.4.0.GA > > Attachments: jobs-openjdk18.txt > > > switch jobs to use openjdk-1.8 instead of jdk1.8 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1108) JBTIS 4.4.3.CR1 refers to JBTIS TP 4.4.3.CR1 instead of 4.4.3.CR2

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1108?page=com.atlassian.jira.plugin... ] Paul Leacu resolved JBTIS-1108. ------------------------------- Fix Version/s: 4.4.3.CR1 Resolution: Done Corrected - note that the latest TP is 4.4.3.Final-SNAPSHOT but since it's still a snapshot the correct change is to pull in JBTIS TP 4.4.3.CR2 > JBTIS 4.4.3.CR1 refers to JBTIS TP 4.4.3.CR1 instead of 4.4.3.CR2 > ----------------------------------------------------------------- > > Key: JBTIS-1108 > URL: https://issues.jboss.org/browse/JBTIS-1108 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.4.3.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 4.4.3.CR1 > > > The file at http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... contains > {code} > <children size="2"> >  > <child location="4.4.3.CR1/"/> > <child location="../../../../targetplatforms/jbtistarget/4.4.3.CR1/jbtis/REPO/"/> > </children> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24301) Error while building jbosstools-openshift-4.4.3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24301: ------------------------------------ If you wait a week or so you'll be able to build 4.4.4 instead, which relies on Neon.3b. To recap, here are the projects to build, in order: a) jbosstools-build (parent pom) b) reddeer (test requirements) c) jbosstools-base (server and openshift require this) d) jbosstools-server (openshift requires this) e) jbosstools-openshift for each build, you should only just need to: * clone the project onto your disk * go into the folder where you cloned it * run `mvn clean install` If you are behind a firewall that prevents access to download.jboss.org and Maven Central, you should disable that firewall so you can access the internet during the builds. > Error while building jbosstools-openshift-4.4.3 > ----------------------------------------------- > > Key: JBIDE-24301 > URL: https://issues.jboss.org/browse/JBIDE-24301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.3.Final > Reporter: jyoti tumsare > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM1 > > Attachments: Error.PNG, issues.PNG, issues.txt, jbosstools-build.png, org.jboss.ide.eclipse.as.management.as7.png, target-platform.png > > > To build jbosstools-openshift-4.4.3 I followed following steps > 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3. > 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found". > 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24387) Implement cleanup methods for OS requirements

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24387?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-24387. ------------------------------- > Implement cleanup methods for OS requirements > --------------------------------------------- > > Key: JBIDE-24387 > URL: https://issues.jboss.org/browse/JBIDE-24387 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 4.4.4.Final > > > Reddeer requirements should be able to clean after themselves. Implement cleanup for OS requirements so it can be used from the annotation rather than afterclass. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24417) getProjectRootPomParents.sh should support released parent pom versions (not just SNAPSHOTs)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24417?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24417: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.4.4.Final) > getProjectRootPomParents.sh should support released parent pom versions (not just SNAPSHOTs) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24417 > URL: https://issues.jboss.org/browse/JBIDE-24417 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.0.Final > > > Ran this: > {code} > /tmp/jbt.github/jbosstools-build-ci/util/getProjectRootPomParents.sh -updateRootPom -b jbosstools-4.4.x -b2 jbosstools-4.4.x -pv 4.4.4.Final -w1 /tmp/jbt.github -vjbt 4.4.4.Final -vds 10.4.0.GA -tpmin 4.60.3.Final -tpmax 4.63.0.Final -p1 "aerogear::aerogear-hybrid arquillian base::foundation browsersim central forge freemarker hibernate javaee::jsf jst livereload openshift server vpe::visual-page-editor-core webservices integration-tests" -p2 "build build-sites::updatesite discovery::central-update devdoc download.jboss.org maven-plugins:build versionwatch" -p3 "artwork ci::build devdoc product::installer qa website" -jirahost https://issues.jboss.org{code} > and the output suggested that all the root poms are already updated because they have 4.4.4.Final-SNAPSHOT (not 4.4.4.Final). > So... need to fix this ASAP. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 May 2017