December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18692) Jenkins build for jbosstools-incubator-ripple

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18692?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18692: ------------------------------------- [~mickael_istria], [~gercan] this is great! However, I'd rather apply and test those PRs after 4.2.1 codefreeze if you don't mind. > Jenkins build for jbosstools-incubator-ripple > --------------------------------------------- > > Key: JBIDE-18692 > URL: https://issues.jboss.org/browse/JBIDE-18692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > We need a jenkins job to build for jbosstools-incubator-ripple, and have it > invoking "./configure && jake" and distribute the builds to Nexus so that cordovasim can start using ripple from this repo. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18698) Irrelevant server item at 4.2.0 Final What's New page

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18698?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18698: --------------------------------------------- Yeah it is not optimal but can't think of a better way at the moment. +1 > Irrelevant server item at 4.2.0 Final What's New page > ----------------------------------------------------- > > Key: JBIDE-18698 > URL: https://issues.jboss.org/browse/JBIDE-18698 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.Final > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.3.x > > > If you look at http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Final.html... > There is an item for > JBIDE-17076 Move 'externally managed' server setting into the launch config ui's > This was done for 4.2.0 Beta2 > But later it was reverted with > JBIDE-17616 Move 'externally managed' from launch config to server editor > I understand that currently the Final What's New page is an aggregate of all pre-final pages, so that's how this happened. And there is an ongoing discussion about this. > But before a the mechanism is changed, I would prefer to simply remove this one item from the Beta2 N&N page - better to remove it altogether than to show an irrelevant item in the Final N&N page. > Let me know if you agree and I can create a PR for it. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17212) Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17212?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17212. --------------------------------- > Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-17212 > URL: https://issues.jboss.org/browse/JBIDE-17212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.Final > > > As you said in JBIDE-7515, when you specify startup and shutdown scripts with a deploy-only server, the server process should be killed if the shutdown script fails. But that is not the case. > From JBIDE-7515: > {quote} > I left the shutdown script empty. > You said that if the shutdown script fails, the process ID will be killed. Maybe technically an empty command does not fail, but I believe in this case the running java process should still be killed and it isn't. > In fact, it doesn't work even if I put something that will fail there, e.g. "exit 1". > {quote} > The shutdown should default to process kill even if the shutdown script is empty. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18685) Sometimes the internal browser shows cached outdated content when using Show In Web Browser

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18685?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-18685: --------------------------------------- [~rob.stryker], I will take a look at it. > Sometimes the internal browser shows cached outdated content when using Show In Web Browser > ------------------------------------------------------------------------------------------- > > Key: JBIDE-18685 > URL: https://issues.jboss.org/browse/JBIDE-18685 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Final > > > Sometimes "Show in web browser" on a server in Server View results in wrong content being shown. When you start EAP 6, open the home page in web browser, then stop EAP, start AS7, open the home page again (using Show In) and the browser will still show EAP's home page. > [~ljelinko] discovered this bug on Linux and I was able to reproduce it on OS X. > I understand that this might be a problem in Eclipse itself, that's up to you, Rob, to investigate :) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18698) Irrelevant server item at 4.2.0 Final What's New page

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18698?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18698: --------------------------------------- Xavier, no worries. Here's the proposed PR: https://github.com/jbosstools/jbosstools-website/pull/291 > Irrelevant server item at 4.2.0 Final What's New page > ----------------------------------------------------- > > Key: JBIDE-18698 > URL: https://issues.jboss.org/browse/JBIDE-18698 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.Final > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.3.x > > > If you look at http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Final.html... > There is an item for > JBIDE-17076 Move 'externally managed' server setting into the launch config ui's > This was done for 4.2.0 Beta2 > But later it was reverted with > JBIDE-17616 Move 'externally managed' from launch config to server editor > I understand that currently the Final What's New page is an aggregate of all pre-final pages, so that's how this happened. And there is an ongoing discussion about this. > But before a the mechanism is changed, I would prefer to simply remove this one item from the Beta2 N&N page - better to remove it altogether than to show an irrelevant item in the Final N&N page. > Let me know if you agree and I can create a PR for it. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18819) When discovery URL is not set, "Software/Updates" page is silently hidden

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18819?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18819: ---------------------------------------- I'd need a bad ide-config.properties in order to test this. What's the way/system property to set in order to use alternative source for ide-config.properties ? > When discovery URL is not set, "Software/Updates" page is silently hidden > ------------------------------------------------------------------------- > > Key: JBIDE-18819 > URL: https://issues.jboss.org/browse/JBIDE-18819 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.1.CR1, 4.3.0.Alpha1 > > > With latest CI build (in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... ), Central editor seems to miss the "Software/Updates" tab. > Log mentions an error, which doesn't seem related at first sight: > {code:none} > !SESSION 2014-11-21 15:51:47.555 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.8.0_11 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > !ENTRY org.jboss.tools.project.examples 4 0 2014-11-21 15:53:24.762 > !MESSAGE All attempts to discover connectors have failed > !SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2014-11-21 15:53:24.762 > !MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy > !STACK 0 > java.lang.NullPointerException > at java.net.URI$Parser.parse(URI.java:3042) > at java.net.URI.<init>(URI.java:588) > at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90) > at org.jboss.tools.project.examples.internal.discovery.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117) > at org.jboss.tools.project.examples.internal.discovery.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:62) > 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:45) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18450) Include EGit 3.5.0 in 9.0

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18450?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-18450. ---------------------------------- Resolution: Out of Date > Include EGit 3.5.0 in 9.0 > ------------------------- > > Key: JBIDE-18450 > URL: https://issues.jboss.org/browse/JBIDE-18450 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, target-platform > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha1 > > > From Andre: > {quote} > I'd argue that since OpenShift is using git our users would benefit from > any improvement in EGit. So big +1 for me! > > You mean +1 for 4.2.0/8.0.0 ? > > If so, do you think you can make extensive testing of this newer EGit > > and evaluate how well it integrates in JBT/JBDS before Thursday ? > yeah, worth it imho (if max agrees). I'll do that. > {quote} > -- http://lists.jboss.org/pipermail/jbosstools-dev/2014-September/009369.html -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18450) Include EGit 3.5.0 in 9.0

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18450?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18450: ---------------------------------------- JBDS 9 is already built against a Mars-based target-platforms. which currently includes EGit 3.6.0.M1. > Include EGit 3.5.0 in 9.0 > ------------------------- > > Key: JBIDE-18450 > URL: https://issues.jboss.org/browse/JBIDE-18450 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, target-platform > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha1 > > > From Andre: > {quote} > I'd argue that since OpenShift is using git our users would benefit from > any improvement in EGit. So big +1 for me! > > You mean +1 for 4.2.0/8.0.0 ? > > If so, do you think you can make extensive testing of this newer EGit > > and evaluate how well it integrates in JBT/JBDS before Thursday ? > yeah, worth it imho (if max agrees). I'll do that. > {quote} > -- http://lists.jboss.org/pipermail/jbosstools-dev/2014-September/009369.html -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18450) Include EGit 3.5.0 in 9.0

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18450?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18450: ----------------------------------- Summary: Include EGit 3.5.0 in 9.0 (was: Include EGit 3.5.0 in JBDS 8.0.1 / 8.1 / 9.0 [TBD]) > Include EGit 3.5.0 in 9.0 > ------------------------- > > Key: JBIDE-18450 > URL: https://issues.jboss.org/browse/JBIDE-18450 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, target-platform > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha1 > > > From Andre: > {quote} > I'd argue that since OpenShift is using git our users would benefit from > any improvement in EGit. So big +1 for me! > > You mean +1 for 4.2.0/8.0.0 ? > > If so, do you think you can make extensive testing of this newer EGit > > and evaluate how well it integrates in JBT/JBDS before Thursday ? > yeah, worth it imho (if max agrees). I'll do that. > {quote} > -- http://lists.jboss.org/pipermail/jbosstools-dev/2014-September/009369.html -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18595) Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18595?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18595: ----------------------------------- Component/s: qa (was: maven) (was: target-platform) > Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-18595 > URL: https://issues.jboss.org/browse/JBIDE-18595 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Fix For: 4.2.1.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 is a pretty serious bug causing havoc into any plugins that try to iterate properties as pure strings since equinox for reasons beyond me now stores non-string objects into system properties breaking the contract. > Are we not using a recent enough SR1 or are we just not bundling/using the SR1 plugins that triggers the error ? (1 is m2e logging) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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 December 2014