October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25028) Aerogear New and Noteworthy for 4.5.1.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25028?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25028: ------------------------------------ [~gercan] can you process it ? > Aerogear New and Noteworthy for 4.5.1.AM3 > --------------------------------------------------- > > Key: JBIDE-25028 > URL: https://issues.jboss.org/browse/JBIDE-25028 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Jeff MAURY > Assignee: Gorkem Ercan > Priority: Critical > Labels: task > Fix For: 4.5.1.AM3 > > > Gorkem Ercan, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Aerogear 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 Aerogear, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Aerogear 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-25020 #comment Create N&N for Aerogear 4.5.1.AM3 #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 Aerogear 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-25042) Server New and Noteworthy for 4.5.1.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25042?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25042: ------------------------------------ [~rob.stryker] anything new for this sprint ? > Server New and Noteworthy for 4.5.1.AM3 > --------------------------------------------------- > > Key: JBIDE-25042 > URL: https://issues.jboss.org/browse/JBIDE-25042 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Labels: task > Fix For: 4.5.1.AM3 > > > Rob Stryker, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server 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 Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server 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-25020 #comment Create N&N for Server 4.5.1.AM3 #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 Server 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-25037) Javascript New and Noteworthy for 4.5.1.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25037?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25037: ------------------------------------ [~vrubezhny] can you process it ? > Javascript New and Noteworthy for 4.5.1.AM3 > --------------------------------------------------- > > Key: JBIDE-25037 > URL: https://issues.jboss.org/browse/JBIDE-25037 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, nodejs > Reporter: Jeff MAURY > Assignee: Victor Rubezhny > Priority: Critical > Labels: task > Fix For: 4.5.1.AM3 > > > Victor Rubezhny, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Javascript 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 Javascript, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Javascript 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-25020 #comment Create N&N for Javascript 4.5.1.AM3 #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 Javascript 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-25043) Visual Editor New and Noteworthy for 4.5.1.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25043?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25043: ------------------------------------ [~ibuziuk] can you process it ? > Visual Editor New and Noteworthy for 4.5.1.AM3 > --------------------------------------------------- > > Key: JBIDE-25043 > URL: https://issues.jboss.org/browse/JBIDE-25043 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core, visual-page-editor-templates > Reporter: Jeff MAURY > Assignee: Ilya Buziuk > Priority: Critical > Labels: task > Fix For: 4.5.1.AM3 > > > Ilya Buziuk, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Visual Editor 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 Visual Editor, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Visual Editor 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-25020 #comment Create N&N for Visual Editor 4.5.1.AM3 #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 Visual Editor 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-25072) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [foundation]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25072?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25072. ------------------------------ Resolution: Done > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [foundation] > -------------------------------------------------------------------- > > Key: JBIDE-25072 > URL: https://issues.jboss.org/browse/JBIDE-25072 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [foundation]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25070) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [aerogear-hybrid]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25070?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25070. ------------------------------ Resolution: Done > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [aerogear-hybrid] > ------------------------------------------------------------------------- > > Key: JBIDE-25070 > URL: https://issues.jboss.org/browse/JBIDE-25070 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [aerogear-hybrid]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25073) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [browsersim]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25073?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25073. ------------------------------ Resolution: Done > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [browsersim] > -------------------------------------------------------------------- > > Key: JBIDE-25073 > URL: https://issues.jboss.org/browse/JBIDE-25073 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [browsersim]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for browsersim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25078) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [hibernate]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25078?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25078. ------------------------------ Resolution: Done > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [hibernate] > ------------------------------------------------------------------- > > Key: JBIDE-25078 > URL: https://issues.jboss.org/browse/JBIDE-25078 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [hibernate]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25075) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [forge]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25075?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25075. ------------------------------ Resolution: Done > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [forge] > --------------------------------------------------------------- > > Key: JBIDE-25075 > URL: https://issues.jboss.org/browse/JBIDE-25075 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [forge]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24491: --------------------------------------- I agree that at the very least we need better explanation - a tooltip or something like that that would say that "minishift openshift registry" is called to retrieve this information. Is there something like a question mark icon that when you hover over will display some text. I was looking at different pages in Preferences and couldn't find anything similar there. Rob, do you think something like that would be possible? Or how else could we explain this to the user? Also, the error should be better. It should say that the command "minishift openshift registry" failed and to check that the cdk server adapter is set up correctly and is running. Especially because an error will happen in 2 out of 3 situations: a) cdk server adapter is not set up at all - error occurs b) cdk server adapter is set up, but cdk/minishift is stopped - error occurs c) cdk server adapter is set up and cdk/minishift is running - it works It turns out that b) actually does produce a reasonable error, I didn't know. But currently it says that minishift docker-env failed. That's not really the command used, right? That one will display the DOCKER vars, such as DOCKER_HOST. But not the registry. c) works. So we to alter b) and improve a). > CDK Server adapter: allow users to look up the address of the docker registry > ----------------------------------------------------------------------------- > > Key: JBIDE-24491 > URL: https://issues.jboss.org/browse/JBIDE-24491 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.5.1.AM3 > > > if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry. > When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address. > Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code} > It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line. > I dont know yet how to look it up for the OpenShift online variant though. -- 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 October 2017