June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-314) Add default entry for 'Docker Hub' in the registry accounts [EBZ#496177]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-314?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-314: --------------------------------- Assignee: Jeff Johnston > Add default entry for 'Docker Hub' in the registry accounts [EBZ#496177] > ------------------------------------------------------------------------ > > Key: ERT-314 > URL: https://issues.jboss.org/browse/ERT-314 > Project: Eclipse Release Train > Issue Type: Enhancement > Components: Linux Tools > Reporter: Nick Boldt > Assignee: Jeff Johnston > Labels: Docker, bzira > > The registry will just contain the Server Address, so the user will have just to edit the settings to specify the credentials if he/she wants to push images. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22682) "Show In > Web Browser on External Device..." is disabled for OpenShift Servers

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22682?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22682: ----------------------------------- Story Points: 1 Sprint: devex #116 June 2016 Assignee: Fred Bricon > "Show In > Web Browser on External Device..." is disabled for OpenShift Servers > ------------------------------------------------------------------------------- > > Key: JBIDE-22682 > URL: https://issues.jboss.org/browse/JBIDE-22682 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload, openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > > Even though BrowserSim is installed, Show In > Web Browser on External Device is disabled for OpenShift Server adapters -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22682) "Show In > Web Browser on External Device..." is disabled for OpenShift Servers

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22682: ----------------------------------- Summary: "Show In > Web Browser on External Device..." is disabled for OpenShift Servers Key: JBIDE-22682 URL: https://issues.jboss.org/browse/JBIDE-22682 Project: Tools (JBoss Tools) Issue Type: Bug Components: livereload, openshift Affects Versions: 4.4.0.Final Reporter: Fred Bricon Even though BrowserSim is installed, Show In > Web Browser on External Device is disabled for OpenShift Server adapters -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22274) Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory)

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22274?page=com.atlassian.jira.plugi... ] Jeff Johnston resolved JBIDE-22274. ----------------------------------- Resolution: Done > Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22274 > URL: https://issues.jboss.org/browse/JBIDE-22274 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.4.0.Alpha1 > Environment: JBDS 10.0.0.Alpha1-v20160428-0509-B5247 > Reporter: Radim Hopp > Assignee: Jeff Johnston > Fix For: 4.4.x > > > Start docker container with -v parameter pointing to some file. For example: "docker run -d -p 5000:5000 -v /home/rhopp/temp/config.yml_new:/etc/docker/registry/config.yml --name registry1 registry:2" > Go to Docker Explorer, expand running container->right click on the only volume in there->Show In->System Explorer-> Error is logged: > {noformat:title=Failed to open in Web Browser} > java.io.IOException: Cannot run program "/bin/sh" (in directory "/home/rhopp/temp/config.yml_new"): error=20, Not a directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) > at java.lang.Runtime.exec(Runtime.java:620) > at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.getLaunchProcess(ShowInSystemExplorerCommandHandler.java:99) > at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.access$0(ShowInSystemExplorerCommandHandler.java:96) > at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler$1.run(ShowInSystemExplorerCommandHandler.java:65) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.io.IOException: error=20, Not a directory > at java.lang.UNIXProcess.forkAndExec(Native Method) > at java.lang.UNIXProcess.<init>(UNIXProcess.java:248) > at java.lang.ProcessImpl.start(ProcessImpl.java:134) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > ... 5 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22634) fix buildflow jobs to correctly represent interdependencies of jbosstools-* projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22634?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22634: ------------------------------------ New sequence: https://github.com/jbdevstudio/jbdevstudio-ci/commit/eafacaafd243290d498f... > fix buildflow jobs to correctly represent interdependencies of jbosstools-* projects > ------------------------------------------------------------------------------------ > > Key: JBIDE-22634 > URL: https://issues.jboss.org/browse/JBIDE-22634 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM1 > > > Some jobs fail when upstream deps have not been published: > * aerogear depends browsersim > * browsersim depends jst > * vpe depends jst > * arquillian depends javaee > * central depends javaee > * javaee depends vpe > So need to retool the buildflow jobs (and the force-push ones too) to correctly align with these dep chains. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-323) Registry Account Unavailable In Preferences

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-323?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg closed ERT-323. ------------------------------- Assignee: Roland Grunberg Resolution: Done Closing this issue, as it seems to have been resolved. The main issue having been that we didn't update the marketplace entry for Eclipse Docker Tooling to have the latest 2.0.0 release. I'll discuss with Jeff whether it's worth adding it to our upstream releng wiki page right after announcing the release. > Registry Account Unavailable In Preferences > ------------------------------------------- > > Key: ERT-323 > URL: https://issues.jboss.org/browse/ERT-323 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Affects Versions: Mars.2 (4.5), Neon (4.6) > Environment: Windows 7 Enterprise 64-bit > 64-bit Eclipse > Reporter: Trevor Trevor > Assignee: Roland Grunberg > Attachments: no_registry_account.png > > > According to the [user guide|https://wiki.eclipse.org/Linux_Tools_Project/Docker_Tooling/User_Guide] "By default, the Docker Hub registry will be used, however, a user may specify an additional private registry if desired. Additional registries are added using Windows -> Preferences -> Docker -> Registry Accounts." > However, the only things available under Docker are "Docker Machine," and "Logging"; "Registry Accounts" is not present. I have observed this on both Eclipse Neon and Mars, and on a different Windows 7 machine. The plugin does work to show containers and images, but this prevents me from being able to connect to private repository on my network. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-238) Issue in DockerConnection#hasImage(String, String) [EBZ#495243]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-238?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg closed ERT-238. ------------------------------- Resolution: Done Fixed in the corresponding upstream Eclipse bug. > Issue in DockerConnection#hasImage(String,String) [EBZ#495243] > -------------------------------------------------------------- > > Key: ERT-238 > URL: https://issues.jboss.org/browse/ERT-238 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Affects Versions: Neon (4.6) > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > > The method only inspects the first 'repo' value for a given image, so if a given Docker image was tagged with different names (eg: 'jboss/wildfly' and 'xcoulon/wildfly'), then one method call will respond 'false' while it should be 'true'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13671 at 6/29/16 12:29 PM: -------------------------------------------------------------- Using these two PRs [1], [2], here's what happens in Base when we switch to jgit. * Before, AM1 prefix is seen. After, only the timestamp of the last change in git (or local dirty change, for foundation.core) is seen: !base-before-after-jgit.png|thumbnail! [1] https://github.com/jbosstools/jbosstools-build/pull/223 [2] https://github.com/jbosstools/jbosstools-base/pull/514 And, here's some examples of what happens in Arquillian when comparing a clean jgit-based build with a dirty-workspace version of the same build, to show that even without committing changes, your LOCALLY built plugins/features will be correctly upversioned so you can do install tests. * left side, after changing to jgit timestamps. right side, after making a change in the local git workspace & rebuilding: !arq-dirty-workspace-compare1.png|thumbnail! * detail of the feature.source feature.xml files, before and after the dirty change. We see that the correctly versioned new plugin appears in the feature, and the feature version is increased too, even though the change is only in the plugin. !arq-dirty-workspace-compare1.png|thumbnail! * For a bigger change like a refactoring, we see now that the .java and .class files are updated, and again the plugins are upversioned: !arq-dirty-workspace-compare3-bigger-change.png|thumbnail! * And as expected the features are also upversioned for the change: !arq-dirty-workspace-compare4-bigger-change.png|thumbnail! was (Author: nickboldt): Using these two PRs [1], [2], here's what happens in Base when we switch to jgit: !base-before-after-jgit.png|thumbnail! [1] https://github.com/jbosstools/jbosstools-build/pull/223 [2] https://github.com/jbosstools/jbosstools-base/pull/514 And, here's some examples of what happens in Arquillian when comparing a clean jgit-based build with a dirty-workspace version of the same build, to show that even without committing changes, your LOCALLY built plugins/features will be correctly upversioned so you can do install tests. !arq-dirty-workspace-compare1.png|thumbnail! !arq-dirty-workspace-compare1.png|thumbnail! !arq-dirty-workspace-compare3-bigger-change.png|thumbnail! !arq-dirty-workspace-compare4-bigger-change.png|thumbnail! > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.1.AM1 > > Attachments: arq-dirty-workspace-compare1.png, arq-dirty-workspace-compare2.png, arq-dirty-workspace-compare3-bigger-change.png, arq-dirty-workspace-compare4-bigger-change.png, base-before-after-jgit.png, jbide13671-before-and-after.png, server-before-after-jgit-3-different-timestamps.png, server-before-after-jgit-4-different-timestamps-features.png, server-before-after-jgit-dirty-workspace-upversioned-features.png, server-before-after-jgit-dirty-workspace-upversioned-plugin-with-change.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13671 at 6/29/16 12:25 PM: -------------------------------------------------------------- More screenshots showing what happens after we move to jgit: * 3 different plugin timestamps, which match up with when those plugins were last edited in github: !server-before-after-jgit-3-different-timestamps.png|thumbnail! * 4 different feature timestamps, which match up with when those features or their contained plugins were last edited in github: !server-before-after-jgit-4-different-timestamps-features.png|thumbnail! * showing a local dirty change to as.core plugin: !server-before-after-jgit-dirty-workspace-upversioned-plugin-with-change.png|thumbnail! * showing the features that contain the local dirty workspace change to as.core: !server-before-after-jgit-dirty-workspace-upversioned-features.png|thumbnail! was (Author: nickboldt): More screenshots showing what happens after we move to jgit: !server-before-after-jgit-3-different-timestamps.png|thumbnail! !server-before-after-jgit-4-different-timestamps-features.png|thumbnail! !server-before-after-jgit-dirty-workspace-upversioned-features.png|thumbnail! !server-before-after-jgit-dirty-workspace-upversioned-plugin-with-change.png|thumbnail! > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.1.AM1 > > Attachments: arq-dirty-workspace-compare1.png, arq-dirty-workspace-compare2.png, arq-dirty-workspace-compare3-bigger-change.png, arq-dirty-workspace-compare4-bigger-change.png, base-before-after-jgit.png, jbide13671-before-and-after.png, server-before-after-jgit-3-different-timestamps.png, server-before-after-jgit-4-different-timestamps-features.png, server-before-after-jgit-dirty-workspace-upversioned-features.png, server-before-after-jgit-dirty-workspace-upversioned-plugin-with-change.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13671 at 6/29/16 12:22 PM: -------------------------------------------------------------- Using these two PRs [1], [2], here's what happens in Base when we switch to jgit: !base-before-after-jgit.png|thumbnail! [1] https://github.com/jbosstools/jbosstools-build/pull/223 [2] https://github.com/jbosstools/jbosstools-base/pull/514 And, here's some examples of what happens in Arquillian when comparing a clean jgit-based build with a dirty-workspace version of the same build, to show that even without committing changes, your LOCALLY built plugins/features will be correctly upversioned so you can do install tests. !arq-dirty-workspace-compare1.png|thumbnail! !arq-dirty-workspace-compare1.png|thumbnail! !arq-dirty-workspace-compare3-bigger-change.png|thumbnail! !arq-dirty-workspace-compare4-bigger-change.png|thumbnail! was (Author: nickboldt): Using these two PRs [1], [2], here's what happens in Base when we switch to jgit: !base-before-after-jgit.png|thumbnail! [1] https://github.com/jbosstools/jbosstools-build/pull/223 [2] https://github.com/jbosstools/jbosstools-base/pull/514 And, here's some examples of what happens in Arquillian when comparing a clean jgit-based build with a dirty-workspace version of the same build, to show that even without committing changes, your LOCALLY built plugins/features will be correctly upversioned so you can do install tests. !arq-dirty-workspace-compare1.png|thumbnail! !arq-dirty-workspace-compare1.png|thumbnail! !arq-dirty-workspace-compare3-bigger-change.png|thumbnail! !arq-dirty-workspace-compare4-bigger-change.png|thumbnail! > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.1.AM1 > > Attachments: arq-dirty-workspace-compare1.png, arq-dirty-workspace-compare2.png, arq-dirty-workspace-compare3-bigger-change.png, arq-dirty-workspace-compare4-bigger-change.png, base-before-after-jgit.png, jbide13671-before-and-after.png, server-before-after-jgit-3-different-timestamps.png, server-before-after-jgit-4-different-timestamps-features.png, server-before-after-jgit-dirty-workspace-upversioned-features.png, server-before-after-jgit-dirty-workspace-upversioned-plugin-with-change.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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