May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-183) Bad error message when running a Docker Image build on a Docker file when no Docker connections [EBZ#493210]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-183: --------------------------------------- Summary: Bad error message when running a Docker Image build on a Docker file when no Docker connections [EBZ#493210] Key: ERT-183 URL: https://issues.jboss.org/browse/ERT-183 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon (4.6) Created attachment 261544 Capture When we run a Docker Image build on a Docker file but our workspace has no existing Docker connections, the dialog displays a strange (bad I18N processing) error message (see attached image) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-184) NPE when chromium feature is not present [EBZ#493234]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-184: --------------------------------------- Summary: NPE when chromium feature is not present [EBZ#493234] Key: ERT-184 URL: https://issues.jboss.org/browse/ERT-184 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Priority: Critical Fix For: Neon (4.6) RC1 Starting a debugging session without Chromium feature available causes an NPE. This can have 2 solutions (and maybe both of them are desirable). * A better error message than a NPE when there is no debug support * Include the chromium feature by default, as "included" by the main JSDT feature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-185) NullPointerException when image has no tags [EBZ#493347]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-185: --------------------------------------- Summary: NullPointerException when image has no tags [EBZ#493347] Key: ERT-185 URL: https://issues.jboss.org/browse/ERT-185 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon (4.6) The following error occurred: !ENTRY org.eclipse.core.jobs 4 2 2016-05-10 14:54:14.321 !MESSAGE An internal error occurred during: "Refreshing Images...". !STACK 0 java.lang.NullPointerException at java.util.ArrayList.<init>(ArrayList.java:177) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:847) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:785) at org.eclipse.linuxtools.internal.docker.ui.commands.RefreshCommandHandler$2.run(RefreshCommandHandler.java:102) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) This happens on the "busybox' image that has no tags, as shown here: $> docker inspect d167449 [ { "Id": "sha256:d1674496321777c667b6a13597bf89752116f95ca248bd07a146948c2f119e4c", "RepoTags": [], "RepoDigests": [ "busybox@sha256:7d3ce4e482101f0c484602dd6687c826bb8bef6295739088c58e84245845912e" ], ... ] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-508. ----------------------------------- Verified. Moreover, all such properties at http://download.jboss.org/jbosstools/configuration/ide-config.properties refer to the "parent" sites. > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.3.GA, 9.0.0.Alpha2 > > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22317) Cannot build jbosstools-central locally

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22317?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22317: ----------------------------------- Assignee: Fred Bricon > Cannot build jbosstools-central locally > --------------------------------------- > > Key: JBIDE-22317 > URL: https://issues.jboss.org/browse/JBIDE-22317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > With a clean jbosstools-central, "mvn clean verify" fails locally with > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (copy-central-webpage) on project org.jboss.tools.central: Unable to find artifact. Could not find artifact org.jboss.tools.central:jbosstools-central-webpage:zip:2.0.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) > [ERROR] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22317) Cannot build jbosstools-central locally

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22317?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22317: -------------------------------- Story Points: 1 > Cannot build jbosstools-central locally > --------------------------------------- > > Key: JBIDE-22317 > URL: https://issues.jboss.org/browse/JBIDE-22317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > With a clean jbosstools-central, "mvn clean verify" fails locally with > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (copy-central-webpage) on project org.jboss.tools.central: Unable to find artifact. Could not find artifact org.jboss.tools.central:jbosstools-central-webpage:zip:2.0.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) > [ERROR] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22317) Cannot build jbosstools-central locally

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22317?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22317: ------------------------------------- it's usually published in the jboss snapshot repo. I saw the snapshots have been wiped out, for some reason. So I redeployed it. > Cannot build jbosstools-central locally > --------------------------------------- > > Key: JBIDE-22317 > URL: https://issues.jboss.org/browse/JBIDE-22317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > With a clean jbosstools-central, "mvn clean verify" fails locally with > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (copy-central-webpage) on project org.jboss.tools.central: Unable to find artifact. Could not find artifact org.jboss.tools.central:jbosstools-central-webpage:zip:2.0.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) > [ERROR] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-21857: -------------------------------------- Was able to work around this problem by providing my own "run" script for s2i. After adding an admin user in the pod console ($jboss_home/bin/add-user.sh), I was able to connect jconsole to the eap inside the pod with the url service:jmx:remoting-jmx://localhost:9999 > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Thomas Mäder > Priority: Blocker > Fix For: 4.4.x > > Attachments: HCRFailure.zip > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-474) Build with Tycho 0.23.1

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-474?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-474. ----------------------------------- Verified with the branch 'jbosstools-4.3.x' > Build with Tycho 0.23.1 > ----------------------- > > Key: JBTIS-474 > URL: https://issues.jboss.org/browse/JBTIS-474 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution, target-platform > Affects Versions: 4.3.0.Final-TP, 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Labels: releasework > Fix For: 9.0.0.Alpha2 > > > Tycho 0.23 is released [1]. > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > We should move parent pom, target platform builds, and other places where tychoVersion or tycho-version is set) to use the latest version. > This would also include releasing a new version of repo-utils and everything else in jbosstools-maven-plugins [2]. > [2] https://github.com/jbosstools/jbosstools-maven-plugins/tree/master/tycho-... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-22195: --------------------------------------- Reported in https://bugs.eclipse.org/bugs/show_bug.cgi?id=493328 > Docker-machine look-up does not work > ------------------------------------ > > Key: JBIDE-22195 > URL: https://issues.jboss.org/browse/JBIDE-22195 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha2 > > > The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying : > {quote} > The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin > {quote} > even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016