September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25019) Travis builds and PRs failing - problem with Awestruct 0.5.6.beta8?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25019?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25019: ------------------------------------ Thanks to a tip from Jason that pointed me at https://twitter.com/mojavelinux/status/905303225871589376 the builds in master and production are green again in Travis. > Travis builds and PRs failing - problem with Awestruct 0.5.6.beta8? > ------------------------------------------------------------------- > > Key: JBIDE-25019 > URL: https://issues.jboss.org/browse/JBIDE-25019 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > In https://travis-ci.org/jbosstools/jbosstools-website/pull_requests my PR passed (but Lars' failed). > Then in https://travis-ci.org/jbosstools/jbosstools-website/builds my change failed in BOTH master and production (as did Lars' N&N change) > Wondering what's causing this: > {code} > NoMethodError: undefined method `spec' for nil:NilClass > An error occurred while installing awestruct (0.5.6.beta8), and Bundler cannot > continue. > Make sure that `gem install awestruct -v '0.5.6.beta8'` succeeds before > bundling. > The command "eval bundle install --without development --path .bundle " failed. Retrying, 2 of 3.{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24914) Fuse Tools New and Noteworthy for 4.5.1.AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24914?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24914: ------------------------------------ Fixed travis thanks to help from Jason Porter and Dan Allen. Your N&N is live: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.5.1.AM2.html See also https://issues.jboss.org/browse/JBIDE-25019 > Fuse Tools New and Noteworthy for 4.5.1.AM2 > --------------------------------------------------- > > Key: JBIDE-24914 > URL: https://issues.jboss.org/browse/JBIDE-24914 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Reporter: Jeff MAURY > Assignee: Lars Heinemann > Priority: Critical > Labels: task > Fix For: 4.5.1.AM2 > > > Lars Heinemann, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Fuse Tools JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Fuse Tools, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Fuse Tools by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24908 #comment Create N&N for Fuse Tools 4.5.1.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Fuse Tools for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24991) Improve server port offset detection by inspecting configured system properties

by Vsevolod Golovanov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24991?page=com.atlassian.jira.plugi... ] Vsevolod Golovanov commented on JBIDE-24991: -------------------------------------------- [~rob.stryker], no, I'm not touching the launch config in Eclipse. The system property is defined in the one and only standalone.xml, on the server: {code}<?xml version="1.0" encoding="UTF-8" standalone="no"?> <server xmlns="urn:jboss:domain:4.0"> <extensions> <extension module="org.jboss.as.deployment-scanner"/> <extension module="org.jboss.as.clustering.infinispan"/> <system-properties> <property name="jboss.socket.binding.port-offset" value="10"/> ... </system-properties> ... <socket-binding-group default-interface="public" name="standard-sockets" port-offset="${jboss.socket.binding.port-offset:0}"> ... </socket-binding-group> </server> {code} JBT already looks at the {{port-offset="$\{jboss.socket.binding.port-offset:0\}"}} and picks up this {{0}}. I propose that JBT also sees the {{jboss.socket.binding.port-offset}} part and checks system-properties in the same standalone.xml. > Improve server port offset detection by inspecting configured system properties > ------------------------------------------------------------------------------- > > Key: JBIDE-24991 > URL: https://issues.jboss.org/browse/JBIDE-24991 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.5.0.Final > Environment: JBDS11, WF10 > Reporter: Vsevolod Golovanov > Assignee: Rob Stryker > Fix For: 4.5.x > > > The default Wildfly standalone.xml config has port offset configured like this: > {code} > <socket-binding-group ... port-offset="${jboss.socket.binding.port-offset:0}"> > {code} > With the way our configuration process is set up we don't change that. Instead we add a system property to the same config file: > {code} > <system-properties> > <property name="jboss.socket.binding.port-offset" value="10"/> > </system-properties> > {code} > The problem is JBoss Tools doesn't detect this currently. It could be improved to inspect the port-offset attribute and find the corresponding system property value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4548) Multiple bundle conflict after install from RH Central

by Lukáš Valach (JIRA)

Lukáš Valach created JBDS-4548: ---------------------------------- Summary: Multiple bundle conflict after install from RH Central Key: JBDS-4548 URL: https://issues.jboss.org/browse/JBDS-4548 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: rpm Affects Versions: 11.1.0.AM2 Environment: RHEL 7 DevTools: http://brewweb.engineering.redhat.com/brewroot/repos/devtools-2.1-rh-ecli... DevStudio repo: https://devstudio.redhat.com/11/snapshots/builds/devstudio.rpm_master/201... Reporter: Lukáš Valach Assignee: Nick Boldt Priority: Minor Fix For: 11.1.0.AM3 Attachments: rh-eclipse47-devstudio11.1-0.20170914.0818.el7.log.20170914-1109_strict.txt After installation of plugins form RH Central I got multiple bundle exceptions, see the log: [^rh-eclipse47-devstudio11.1-0.20170914.0818.el7.log.20170914-1109_strict.txt] It seems that Central comes with versions suitable for Oxygen 1 RC3 but /opt/rh/rh-eclipse47 contains old versions. {code} Package: org.eclipse.mylyn.tasks.ui /opt/rh/rh-eclipse47: org.eclipse.mylyn.tasks.ui_3.23.0.v20170628-0950.jar ~/.eclipse: org.eclipse.mylyn.tasks.ui_3.23.1.v20170623-0008.jar ---------------------------------------------------------- Package: org.eclipse.mylyn.bugzilla.core /opt/rh/rh-eclipse47: org.eclipse.mylyn.bugzilla.core_3.23.0.v20170628-0950.jar ~/.eclipse: org.eclipse.mylyn.bugzilla.core_3.23.1.v20170623-0008.jar ---------------------------------------------------------- Package: org.eclipse.mylyn.bugzilla.ui /opt/rh/rh-eclipse47: org.eclipse.mylyn.bugzilla.ui_3.23.0.v20170628-0950.jar ~/.eclipse: org.eclipse.mylyn.bugzilla.ui_3.23.1.v20170623-0008.jar ---------------------------------------------------------- Package: org.eclipse.m2e.core /opt/rh/rh-eclipse47: org.eclipse.m2e.core_1.8.0.20170808-0936.jar ~/.eclipse: org.eclipse.m2e.core_1.8.1.20170728-1531.jar ---------------------------------------------------------- Package: org.eclipse.m2e.core.ui /opt/rh/rh-eclipse47: org.eclipse.m2e.core.ui_1.8.0.20170808-0936.jar ~/.eclipse: org.eclipse.m2e.core.ui_1.8.1.20170728-1531.jar ---------------------------------------------------------- Package: org.eclipse.m2e.discovery /opt/rh/rh-eclipse47: org.eclipse.m2e.discovery_1.8.0.20170808-0936.jar ~/.eclipse: org.eclipse.m2e.discovery_1.8.1.20170728-1531.jar ---------------------------------------------------------- Package: org.eclipse.m2e.editor /opt/rh/rh-eclipse47: org.eclipse.m2e.editor_1.8.0.20170808-0936.jar ~/.eclipse: org.eclipse.m2e.editor_1.8.1.20170728-1531.jar ---------------------------------------------------------- Package: org.eclipse.m2e.editor.xml /opt/rh/rh-eclipse47: org.eclipse.m2e.editor.xml_1.8.0.20170808-0936.jar ~/.eclipse: org.eclipse.m2e.editor.xml_1.8.1.20170728-1531.jar ---------------------------------------------------------- Package: org.eclipse.m2e.importer /opt/rh/rh-eclipse47: org.eclipse.m2e.importer_1.8.0.20170808-0936.jar ~/.eclipse: org.eclipse.m2e.importer_1.8.1.20170728-1531.jar ---------------------------------------------------------- Package: org.eclipse.m2e.jdt /opt/rh/rh-eclipse47: org.eclipse.m2e.jdt_1.8.0.20170808-0936.jar ~/.eclipse: org.eclipse.m2e.jdt_1.8.1.20170728-1531.jar ---------------------------------------------------------- Package: org.eclipse.m2e.launching /opt/rh/rh-eclipse47: org.eclipse.m2e.launching_1.8.0.20170808-0936.jar ~/.eclipse: org.eclipse.m2e.launching_1.8.1.20170728-1531.jar ---------------------------------------------------------- Package: org.eclipse.m2e.model.edit /opt/rh/rh-eclipse47: org.eclipse.m2e.model.edit_1.8.0.20170808-0936.jar ~/.eclipse: org.eclipse.m2e.model.edit_1.8.1.20170728-1531.jar ---------------------------------------------------------- Package: org.eclipse.m2e.profiles.core /opt/rh/rh-eclipse47: org.eclipse.m2e.profiles.core_1.8.0.20170808-0936.jar ~/.eclipse: org.eclipse.m2e.profiles.core_1.8.1.20170728-1531.jar ---------------------------------------------------------- Package: org.eclipse.m2e.profiles.ui /opt/rh/rh-eclipse47: org.eclipse.m2e.profiles.ui_1.8.0.20170808-0936.jar ~/.eclipse: org.eclipse.m2e.profiles.ui_1.8.1.20170728-1531.jar ---------------------------------------------------------- Package: org.eclipse.m2e.refactoring /opt/rh/rh-eclipse47: org.eclipse.m2e.refactoring_1.8.0.20170808-0936.jar ~/.eclipse: org.eclipse.m2e.refactoring_1.8.1.20170728-1531.jar ---------------------------------------------------------- {code} As m2e seems to be working fine I am setting priority to minor. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25019) Travis builds and PRs failing - problem with Awestruct 0.5.6.beta8?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25019?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25019: ------------------------------------ I tried this: https://github.com/jbosstools/jbosstools-website/pull/751 and it built fine as a PR [1] then failed as a build [2]. [1] https://travis-ci.org/jbosstools/jbosstools-website/builds/275504904 [2] https://travis-ci.org/jbosstools/jbosstools-website/builds/275508367 [~lightguard] [~xcoulon] [~maxandersen] Got any advice for what we can fix in the travis config to make builds work again? Do we need to move to Awestruct 0.5.7? > Travis builds and PRs failing - problem with Awestruct 0.5.6.beta8? > ------------------------------------------------------------------- > > Key: JBIDE-25019 > URL: https://issues.jboss.org/browse/JBIDE-25019 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > In https://travis-ci.org/jbosstools/jbosstools-website/pull_requests my PR passed (but Lars' failed). > Then in https://travis-ci.org/jbosstools/jbosstools-website/builds my change failed in BOTH master and production (as did Lars' N&N change) > Wondering what's causing this: > {code} > NoMethodError: undefined method `spec' for nil:NilClass > An error occurred while installing awestruct (0.5.6.beta8), and Bundler cannot > continue. > Make sure that `gem install awestruct -v '0.5.6.beta8'` succeeds before > bundling. > The command "eval bundle install --without development --path .bundle " failed. Retrying, 2 of 3.{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25019) Travis builds and PRs failing - problem with Awestruct 0.5.6.beta8?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25019?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25019: ---------------------------------- Assignee: Nick Boldt > Travis builds and PRs failing - problem with Awestruct 0.5.6.beta8? > ------------------------------------------------------------------- > > Key: JBIDE-25019 > URL: https://issues.jboss.org/browse/JBIDE-25019 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > In https://travis-ci.org/jbosstools/jbosstools-website/pull_requests my PR passed (but Lars' failed). > Then in https://travis-ci.org/jbosstools/jbosstools-website/builds my change failed in BOTH master and production (as did Lars' N&N change) > Wondering what's causing this: > {code} > NoMethodError: undefined method `spec' for nil:NilClass > An error occurred while installing awestruct (0.5.6.beta8), and Bundler cannot > continue. > Make sure that `gem install awestruct -v '0.5.6.beta8'` succeeds before > bundling. > The command "eval bundle install --without development --path .bundle " failed. Retrying, 2 of 3.{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25019) Travis builds and PRs failing - problem with Awestruct 0.5.6.beta8?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25019: ---------------------------------- Summary: Travis builds and PRs failing - problem with Awestruct 0.5.6.beta8? Key: JBIDE-25019 URL: https://issues.jboss.org/browse/JBIDE-25019 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Nick Boldt In https://travis-ci.org/jbosstools/jbosstools-website/pull_requests my PR passed (but Lars' failed). Then in https://travis-ci.org/jbosstools/jbosstools-website/builds my change failed in BOTH master and production (as did Lars' N&N change) Wondering what's causing this: {code} NoMethodError: undefined method `spec' for nil:NilClass An error occurred while installing awestruct (0.5.6.beta8), and Bundler cannot continue. Make sure that `gem install awestruct -v '0.5.6.beta8'` succeeds before bundling. The command "eval bundle install --without development --path .bundle " failed. Retrying, 2 of 3.{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25019) Travis builds and PRs failing - problem with Awestruct 0.5.6.beta8?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25019?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25019: ------------------------------- Component/s: website > Travis builds and PRs failing - problem with Awestruct 0.5.6.beta8? > ------------------------------------------------------------------- > > Key: JBIDE-25019 > URL: https://issues.jboss.org/browse/JBIDE-25019 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Nick Boldt > Fix For: 4.5.1.AM2 > > > In https://travis-ci.org/jbosstools/jbosstools-website/pull_requests my PR passed (but Lars' failed). > Then in https://travis-ci.org/jbosstools/jbosstools-website/builds my change failed in BOTH master and production (as did Lars' N&N change) > Wondering what's causing this: > {code} > NoMethodError: undefined method `spec' for nil:NilClass > An error occurred while installing awestruct (0.5.6.beta8), and Bundler cannot > continue. > Make sure that `gem install awestruct -v '0.5.6.beta8'` succeeds before > bundling. > The command "eval bundle install --without development --path .bundle " failed. Retrying, 2 of 3.{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25019) Travis builds and PRs failing - problem with Awestruct 0.5.6.beta8?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25019?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25019: ------------------------------- Fix Version/s: 4.5.1.AM2 > Travis builds and PRs failing - problem with Awestruct 0.5.6.beta8? > ------------------------------------------------------------------- > > Key: JBIDE-25019 > URL: https://issues.jboss.org/browse/JBIDE-25019 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Nick Boldt > Fix For: 4.5.1.AM2 > > > In https://travis-ci.org/jbosstools/jbosstools-website/pull_requests my PR passed (but Lars' failed). > Then in https://travis-ci.org/jbosstools/jbosstools-website/builds my change failed in BOTH master and production (as did Lars' N&N change) > Wondering what's causing this: > {code} > NoMethodError: undefined method `spec' for nil:NilClass > An error occurred while installing awestruct (0.5.6.beta8), and Bundler cannot > continue. > Make sure that `gem install awestruct -v '0.5.6.beta8'` succeeds before > bundling. > The command "eval bundle install --without development --path .bundle " failed. Retrying, 2 of 3.{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24773) Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24773?page=com.atlassian.jira.plugi... ] Aurélien Pupier reassigned JBIDE-24773: --------------------------------------- Assignee: (was: Aurélien Pupier) > Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24773 > URL: https://issues.jboss.org/browse/JBIDE-24773 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Fix For: 4.5.1.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 September 2017