[JBoss JIRA] (JBIDE-21150) SSL certificate dialog: Provide a way to change one's mind about accepting an SSL certificate
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21150?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21150:
-----------------------------------------------
For (1): there is a checkbox 'Remember decision...', so that if user rejects the certificate with the checkbox on, it is logical that he will not see the dialog until he changes preferences. Or, we should not remember rejection, but then the label for the checkbox should clearly explain how it works. What do you think of it?
> SSL certificate dialog: Provide a way to change one's mind about accepting an SSL certificate
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21150
> URL: https://issues.jboss.org/browse/JBIDE-21150
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jan Richter
> Labels: openshift_v2, openshift_v3
> Fix For: 4.3.1.Beta2
>
>
> The tooling will only give the user one chance to accept/deny the SSL certificate, which happens on start of the session. This is particularly annoying when for some reason the user denies the certificate (or just cancels the dialog) because the only way to reset it is to restart the IDE.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21382) remove dependency from o.j.t.common.model.ui to org.eclipse.core.runtime.compatibility_3.2.300.v20150423-0821 (removed from Neon in M3)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21382?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-21382 at 1/4/16 1:28 PM:
----------------------------------------------------------------
-o.j.t.common.model.ui contains an internal editor which is used for XModel meta file editing.-
Never mind. It's actually meta.ui, not model.ui, which is for meta editing.
So, I just removed org.eclipse.core.runtime.compatibility from model.ui plugin.
was (Author: akazakov):
o.j.t.common.model.ui contains an internal editor which is used for XModel meta file editing. I don't see any value of this plugin for JBDS or JBT users.
So, I removed org.eclipse.core.runtime.compatibility from this plugin but I also removed it from org.jboss.tools.common.ui.feature : https://github.com/jbosstools/jbosstools-base/pull/475
> remove dependency from o.j.t.common.model.ui to org.eclipse.core.runtime.compatibility_3.2.300.v20150423-0821 (removed from Neon in M3)
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21382
> URL: https://issues.jboss.org/browse/JBIDE-21382
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> org.eclipse.core.runtime.compatibility 3.2.300.v20150423-0821 was removed from Neon as of M3. It is required by these IUs:
> * o.j.t.common.model.ui,
> * o.e.platform.feature,
> * o.e.m2e.feature,
> * o.e.datatools.oda.cshelp,
> * o.aspectj.ajde,
> * o.e.wst.xml.xpath.core, and
> * o.e.birt.feature
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add deployment view to OpenShift v3 explorer
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-19178:
----------------------------------
Summary: Explorer, Servers view: Add deployment view to OpenShift v3 explorer (was: Explorer, Servers view: Add logical view to OpenShift v3 explorer)
> Explorer, Servers view: Add deployment view to OpenShift v3 explorer
> --------------------------------------------------------------------
>
> Key: JBIDE-19178
> URL: https://issues.jboss.org/browse/JBIDE-19178
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: explorer, openshift_v3
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
> Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Initial deployment view.png, Pipeline view mockup.bmml, Pipeline view mockup.png
>
>
> Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21376) Different application proposals on Eclipse tooling vs Web Console
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21376:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
> Different application proposals on Eclipse tooling vs Web Console
> -----------------------------------------------------------------
>
> Key: JBIDE-21376
> URL: https://issues.jboss.org/browse/JBIDE-21376
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
> Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png
>
>
> Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling.
> See attached screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21376) Different application proposals on Eclipse tooling vs Web Console
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21376:
-------------------------------------
Issue Type: Feature Request (was: Bug)
> Different application proposals on Eclipse tooling vs Web Console
> -----------------------------------------------------------------
>
> Key: JBIDE-21376
> URL: https://issues.jboss.org/browse/JBIDE-21376
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Xavier Coulon
> Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png
>
>
> Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling.
> See attached screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21376) Different application proposals on Eclipse tooling vs Web Console
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21376:
------------------------------------------
It turns out that this is actually a missing feature. In the web console you can build from template or from builder image (notice the title in the web console "Select Image or Template") with git source. In Eclipse we're missing this yet.
> Different application proposals on Eclipse tooling vs Web Console
> -----------------------------------------------------------------
>
> Key: JBIDE-21376
> URL: https://issues.jboss.org/browse/JBIDE-21376
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Xavier Coulon
> Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png
>
>
> Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling.
> See attached screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21376) Different application proposals on Eclipse tooling vs Web Console
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21376 at 1/4/16 12:29 PM:
-------------------------------------------------------------------
It turns out that this is actually a missing feature. In the web console you can build from template or from builder image (notice the title in the web console "Select Image or Template") with git source. In Eclipse we're missing this.
was (Author: adietish):
It turns out that this is actually a missing feature. In the web console you can build from template or from builder image (notice the title in the web console "Select Image or Template") with git source. In Eclipse we're missing this yet.
> Different application proposals on Eclipse tooling vs Web Console
> -----------------------------------------------------------------
>
> Key: JBIDE-21376
> URL: https://issues.jboss.org/browse/JBIDE-21376
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Xavier Coulon
> Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png
>
>
> Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling.
> See attached screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21165) Need to improve js tools (npm / bower) launch
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21165?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21165:
----------------------------------------
Added "new_and_noteworthy" to highlight that the preference page for Bower is gone.
> Need to improve js tools (npm / bower) launch
> ----------------------------------------------
>
> Key: JBIDE-21165
> URL: https://issues.jboss.org/browse/JBIDE-21165
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: javascript, nodejs, upstream
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.4.0.Alpha1
>
>
> For now npm / bower is launched via node. Basically, this was done due to the fact that on Mac Os launched from desktop node PATH var not available:
> {quote}
> env: node: No such file or directory
> {quote}
> In order to handle it, it was suggested to launch npm / bower tools via node and have a preference for each tool. However, on thym project more elegant solution was found - execute the given command and returns a handle to the process.
> More details can be found here:
> - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core...
> - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core...
> Basically, this approach kills two birds with one stone:
> 1. No mac os Path issue
> 2. No need to have preferences for node / npm / bower
> Also, it will be quite easy to provide cheatsheets for this tools which will include sets of commands
> The plan is:
> - reimplement the launch process that will be generic for both jsdt and thym (maybe some other tools in future)
> - remove irrelevant code with preferences, detectors etc
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21165) Need to improve js tools (npm / bower) launch
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21165?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21165:
-----------------------------------
Labels: new_and_noteworthy (was: )
> Need to improve js tools (npm / bower) launch
> ----------------------------------------------
>
> Key: JBIDE-21165
> URL: https://issues.jboss.org/browse/JBIDE-21165
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: nodejs, upstream
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.4.0.Alpha1
>
>
> For now npm / bower is launched via node. Basically, this was done due to the fact that on Mac Os launched from desktop node PATH var not available:
> {quote}
> env: node: No such file or directory
> {quote}
> In order to handle it, it was suggested to launch npm / bower tools via node and have a preference for each tool. However, on thym project more elegant solution was found - execute the given command and returns a handle to the process.
> More details can be found here:
> - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core...
> - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core...
> Basically, this approach kills two birds with one stone:
> 1. No mac os Path issue
> 2. No need to have preferences for node / npm / bower
> Also, it will be quite easy to provide cheatsheets for this tools which will include sets of commands
> The plan is:
> - reimplement the launch process that will be generic for both jsdt and thym (maybe some other tools in future)
> - remove irrelevant code with preferences, detectors etc
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years