[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 Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22274?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-22274:
---------------------------------------
Bugzilla: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=492725]
> 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.1.AM1
>
>
> 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
[JBoss JIRA] (JBIDE-22552) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22552?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22552:
-------------------------------
Fix Version/s: 4.4.1.AM1
(was: 4.4.1.AM2)
> For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1
> ------------------------------------------------
>
> Key: JBIDE-22552
> URL: https://issues.jboss.org/browse/JBIDE-22552
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.AM1
>
>
> For JBIDE 4.4.1.Alpha1: Please perform the following tasks:
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3930
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22552) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22552?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-22552:
----------------------------------
Assignee: Nick Boldt
> For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1
> ------------------------------------------------
>
> Key: JBIDE-22552
> URL: https://issues.jboss.org/browse/JBIDE-22552
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.AM1
>
>
> For JBIDE 4.4.1.Alpha1: Please perform the following tasks:
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3930
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22552) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22552?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-22552.
------------------------------
Resolution: Done
> For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1
> ------------------------------------------------
>
> Key: JBIDE-22552
> URL: https://issues.jboss.org/browse/JBIDE-22552
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.AM1
>
>
> For JBIDE 4.4.1.Alpha1: Please perform the following tasks:
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3930
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22554) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central Discovery]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22554?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-22554.
------------------------------
Fix Version/s: 4.4.1.AM1
(was: 4.4.1.AM2)
Resolution: Rejected
Nothing to do, as there are no changes in Central discovery since 4.4.0.
> For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central Discovery]
> --------------------------------------------------------------------
>
> Key: JBIDE-22554
> URL: https://issues.jboss.org/browse/JBIDE-22554
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central-update
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.AM1
>
>
> For JBIDE 4.4.1.Alpha1 [Central Discovery]: Please perform the following tasks:
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22562) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22562?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-22562.
------------------------------
Resolution: Done
I've updated the two python scripts, deleted the job, and added a note to the JIRA component description making it deprecated.
There's no way to archive a component in JIRA, but I could delete it. That would mean all the JIRAs for this component would have to be moved somewhere else (or lose their component, which might cause jiralint to complain).
> For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground]
> -------------------------------------------------------------
>
> Key: JBIDE-22562
> URL: https://issues.jboss.org/browse/JBIDE-22562
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: playground
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.AM2
>
>
> For JBIDE 4.4.1.Alpha1 [Playground]: Please perform the following tasks:
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months