August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3982) wrap new devstudio-javaee update site inside an rpm for linux installs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3982?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3982: ---------------------------------- build.sh takes about 45 mins: * 4 mins to download update site zips * 1 min to install from update sites to devstudio/ folder * 5 mins to create tar.gz * 20 seconds to create src.rpm * ~35 mins to createrepo_c > wrap new devstudio-javaee update site inside an rpm for linux installs > ---------------------------------------------------------------------- > > Key: JBDS-3982 > URL: https://issues.jboss.org/browse/JBDS-3982 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.AM3 > > > wrap new update site (JBDS-3981) in a rh-eclipse46-devstudio*.rpm so we can install it on Fedora 24 and RHEL 7 > will need to port http://download.jboss.org/jbosstools/updates/scripted-install/director.xml to bash so it can be called along with rpmbuilder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22874) ide-config.properties needs updating for 10.1.0.AM3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22874?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22874: ------------------------------------ Yes. We update ide-config.properties every time we stage or release a new release. > ide-config.properties needs updating for 10.1.0.AM3 > --------------------------------------------------- > > Key: JBIDE-22874 > URL: https://issues.jboss.org/browse/JBIDE-22874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > > Today I installed a new build of devstudio (devstudio-10.1.0.AM3-v20160802-1710-B5682-installer-standalone.jar) and immediately after launching it, I got these in the error log view: > {code} > No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! > {code} > {code} > All attempts to discover connectors have failed > {code} > {code} > Failed to get connectors from RemoteProxyWizardDiscoveryStrategy > java.lang.NullPointerException > at java.net.URI$Parser.parse(URI.java:3042) > at java.net.URI.<init>(URI.java:588) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90) > at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117) > at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68) > at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114) > at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107) > at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > {code} > No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! > {code} > This is probably happening because [1] doesn't have any lines that would apply for devstudio 10.1.0.AM3. > At first I thought it's something that was overlooked when changing product version from 10.0.1 to 10.1.0, but it seems 10.0.1.AM3 would have no match either as there is currently only 10.0.1.AM2 there. Shouldn't we have also have lines for a more general version like 10.1.0, so that a match is guaranteed? > On the other hand, JBoss Tools should be fine - I can see lines for both 4.4.1 and 4.4.1.AM3. > Feel free to move this to JBDS if you think that's more appropriate. > [1] http://download.jboss.org/jbosstools/configuration/ide-config.properties -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22968) if a build fails to publish, future builds may think there's nothing new and also not publish

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22968?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22968: ------------------------------------ we could enable p2diff checks like this: https://github.com/jbdevstudio/jbdevstudio-ci/commit/62d10dcfc1d772156ac4... > if a build fails to publish, future builds may think there's nothing new and also not publish > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22968 > URL: https://issues.jboss.org/browse/JBIDE-22968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > Attachments: openshift-failed-future-builds-did-not-publish.png > > > When publishing snapshots to download.jboss.org via Jenkins jobs, we need to add a check for "did the last build fail? if so, set skipRevisionCheckWhenPublishing = true" > That way we don't get situations where the Openshift build fails (because failed enforcer check) and then the next 4-5 builds are NOT published (because as far as the current tests are concerned, the latest SHA in Jenkins == latest SHA in github... but NOT the latest SHA on download.jboss.org/.../snapshots/JOB_NAME/latest/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22968) if a build fails to publish, future builds may think there's nothing new and also not publish

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22968?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22968: ------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.Final) > if a build fails to publish, future builds may think there's nothing new and also not publish > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22968 > URL: https://issues.jboss.org/browse/JBIDE-22968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > Attachments: openshift-failed-future-builds-did-not-publish.png > > > When publishing snapshots to download.jboss.org via Jenkins jobs, we need to add a check for "did the last build fail? if so, set skipRevisionCheckWhenPublishing = true" > That way we don't get situations where the Openshift build fails (because failed enforcer check) and then the next 4-5 builds are NOT published (because as far as the current tests are concerned, the latest SHA in Jenkins == latest SHA in github... but NOT the latest SHA on download.jboss.org/.../snapshots/JOB_NAME/latest/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22992) OpenShift tools use wrong rest client bits

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22992?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22992 at 8/10/16 4:50 PM: ------------------------------------------------------------- FWIW, the Jenkins console doesn't even tell you what version is being used in the build: {code}[INFO] Downloading: http://snapshots.jboss.org/maven2/com/openshift/openshift-restclient-java... [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/com/openshift... [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/releases/com/open... [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/com/ope... [INFO] Downloading: http://maven.repository.redhat.com/ga/com/openshift/openshift-restclient-... [INFO] Downloaded: http://snapshots.jboss.org/maven2/com/openshift/openshift-restclient-java... (1002 B at 2.9 KB/sec) [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/com/openshift... (1002 B at 1.9 KB/sec) [INFO] Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/com/ope... (1002 B at 1.8 KB/sec) [INFO] Copying openshift-restclient-java-5.0.0-SNAPSHOT.jar to /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.client/lib/openshift-restclient-java-5.0.0-SNAPSHOT.jar [INFO] Copying openshift-restclient-java-5.0.0-SNAPSHOT.jar to /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.client/lib/openshift-restclient-java-5.0.0-SNAPSHOT.jar{code} was (Author: nickboldt): FWIW, the Jenkins console doesn't even tell you what version is being used in the build: [code} [INFO] Downloading: http://snapshots.jboss.org/maven2/com/openshift/openshift-restclient-java... [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/com/openshift... [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/releases/com/open... [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/com/ope... [INFO] Downloading: http://maven.repository.redhat.com/ga/com/openshift/openshift-restclient-... [INFO] Downloaded: http://snapshots.jboss.org/maven2/com/openshift/openshift-restclient-java... (1002 B at 2.9 KB/sec) [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/com/openshift... (1002 B at 1.9 KB/sec) [INFO] Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/com/ope... (1002 B at 1.8 KB/sec) [INFO] Copying openshift-restclient-java-5.0.0-SNAPSHOT.jar to /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.client/lib/openshift-restclient-java-5.0.0-SNAPSHOT.jar [INFO] Copying openshift-restclient-java-5.0.0-SNAPSHOT.jar to /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.client/lib/openshift-restclient-java-5.0.0-SNAPSHOT.jar{code} > OpenShift tools use wrong rest client bits > ------------------------------------------ > > Key: JBIDE-22992 > URL: https://issues.jboss.org/browse/JBIDE-22992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.1.AM3 > Environment: eclipse.buildId=10.1.0.AM3-v20160810-0441-B5735 > java.version=1.8.0_101 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product > Reporter: Denis Golovin > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.1.Final > > > An internal error occurred during: "Loading service-manager to configure additional frameworks that CDK depends on.".{code}java.lang.NoSuchMethodError: com.openshift.restclient.ClientBuilder.withMaxRequests(I)Lcom/openshift/restclient/ClientBuilder; > at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:53) > at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:1) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:77) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:55) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureOpenshift(ConfigureDependentFrameworksListener.java:91) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:56) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:44) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22996) PR checks fails on Windows slaves if some special symbols are used in the commit message

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-22996: -------------------------------------- Summary: PR checks fails on Windows slaves if some special symbols are used in the commit message Key: JBIDE-22996 URL: https://issues.jboss.org/browse/JBIDE-22996 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.1.AM3 Reporter: Alexey Kazakov Assignee: Nick Boldt Fix For: 4.4.x For example: https://github.com/jbosstools/jbosstools-openshift/pull/1282 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22995) Upgrade Forge Runtime to 3.3.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22995?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-22995. ------------------------------------- Resolution: Done > Upgrade Forge Runtime to 3.3.0.Final > ------------------------------------ > > Key: JBIDE-22995 > URL: https://issues.jboss.org/browse/JBIDE-22995 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.4.1.AM2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-828) Add handling for dirty Properties View

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-828: ---------------------------------- Summary: Add handling for dirty Properties View Key: JBTIS-828 URL: https://issues.jboss.org/browse/JBTIS-828 Project: JBoss Tools Integration Stack Issue Type: Task Components: QE Affects Versions: 4.3.1.Final Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík Priority: Critical Fix For: 4.3.1.Final Properties view can be mark as dirty for some reason. The current implementation of _PropertiesView_ in RedDeer cannot handle this situation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3982) wrap new devstudio-javaee update site inside an rpm for linux installs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3982?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3982: ----------------------------- Description: wrap new update site (JBDS-3981) in a rh-eclipse46-devstudio*.rpm so we can install it on Fedora 24 and RHEL 7 will need to port http://download.jboss.org/jbosstools/updates/scripted-install/director.xml to bash so it can be called along with rpmbuilder. was: wrap new update site (JBDS-3981) in a rh-eclipse46-devstudio*.rpm so we can install it on Fedora 24 and RHEL 7 > wrap new devstudio-javaee update site inside an rpm for linux installs > ---------------------------------------------------------------------- > > Key: JBDS-3982 > URL: https://issues.jboss.org/browse/JBDS-3982 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.AM3 > > > wrap new update site (JBDS-3981) in a rh-eclipse46-devstudio*.rpm so we can install it on Fedora 24 and RHEL 7 > will need to port http://download.jboss.org/jbosstools/updates/scripted-install/director.xml to bash so it can be called along with rpmbuilder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3982) wrap new devstudio-javaee update site inside an rpm for linux installs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3982?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3982: ---------------------------------- Thx to [~rgrunber] for this starting point: https://rgrunber.fedorapeople.org/resolveFeature Thx also to [~mat.booth] for the initial build.sh script from which this PR was born: https://github.com/jbdevstudio/jbdevstudio-product/pull/393 > wrap new devstudio-javaee update site inside an rpm for linux installs > ---------------------------------------------------------------------- > > Key: JBDS-3982 > URL: https://issues.jboss.org/browse/JBDS-3982 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.AM3 > > > wrap new update site (JBDS-3981) in a rh-eclipse46-devstudio*.rpm so we can install it on Fedora 24 and RHEL 7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016