[JBoss JIRA] (JBIDE-22599) Tag "decision" is not reporting error in source view
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-22599:
-------------------------------------
Summary: Tag "decision" is not reporting error in source view
Key: JBIDE-22599
URL: https://issues.jboss.org/browse/JBIDE-22599
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: batch
Affects Versions: 4.4.0.Final
Environment: Fedora 24,
devstudio:
Version: 10.0.0.GA
Build id: GA-v20160613-1243-B18
Build date: 20160613-1243
Reporter: Ondrej Dockal
Priority: Minor
Attachments: DesignView.png, SourceView.png
While validation in design and diagram views is reporting missing reference in decision tag, in the source view this report is missing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22598) Support runtime detection for manual CDK install
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22598?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22598:
----------------------------------------
This will became relevant when we have Dev suite zips for Linux and Macs.
And I would prefer the option a)
> Support runtime detection for manual CDK install
> ------------------------------------------------
>
> Key: JBIDE-22598
> URL: https://issues.jboss.org/browse/JBIDE-22598
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk, runtime-detection
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> Right now with CDK 2.1 when you have a manual cdk install (i.e. using cdk.zip and then adding the vagrant box yourself), there will be no .cdk marker, so Runtime Detection will not work.
> The only case where Runtime Detection will work is when you use the (as of now Windows-only) suite installer. At that point Runtime Detection will do its thing silently without you noticing.
> The way I see it there are two options:
> a) Create and upstream issue with CDK and ask them to include a basic .cdk in their zip
> b) Make the runtime detection work without .cdk
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22115) Connection wizard: Truncated error message display connecting to server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22115:
-------------------------------------
Labels: connection_wizard openshift_v3 (was: )
> Connection wizard: Truncated error message display connecting to server
> -----------------------------------------------------------------------
>
> Key: JBIDE-22115
> URL: https://issues.jboss.org/browse/JBIDE-22115
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Final
> Environment: Version: 9.1.0.GA
> Build id: GA-v20160403-1700-B477
> Build date: 20160403-1700
> Reporter: Len DiMaggio
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: bad_token_1.png, bad_token_2.png
>
>
> See attached screenshot - the error message is truncated until the user expands the width of the dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22115) Connection wizard: Truncated error message display connecting to server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22115:
-------------------------------------
Summary: Connection wizard: Truncated error message display connecting to server (was: Truncated error message display connecting to server)
> Connection wizard: Truncated error message display connecting to server
> -----------------------------------------------------------------------
>
> Key: JBIDE-22115
> URL: https://issues.jboss.org/browse/JBIDE-22115
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Final
> Environment: Version: 9.1.0.GA
> Build id: GA-v20160403-1700-B477
> Build date: 20160403-1700
> Reporter: Len DiMaggio
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.4.x
>
> Attachments: bad_token_1.png, bad_token_2.png
>
>
> See attached screenshot - the error message is truncated until the user expands the width of the dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21871) Weird message in error log when connecting to cdk openshift - Unauthorized
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21871?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-21871:
----------------------------------
Assignee: Jeff MAURY
> Weird message in error log when connecting to cdk openshift - Unauthorized
> ---------------------------------------------------------------------------
>
> Key: JBIDE-21871
> URL: https://issues.jboss.org/browse/JBIDE-21871
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Jeff MAURY
> Fix For: 4.4.x
>
> Attachments: secure-storage.png
>
>
> Everytime I start cdk and then want to connect to the openshift instance in OpenShift Explorer view, I get this info message in Error Log:
> Unauthorized. Trying to reauthenticate
> All the time I was thinking that the connection is actually not working, but then I tried to create a project and it worked.
> I can see a few issues here:
> 1. Why is this info message displayed even though the connection is actually established? It's confusing.
> 2. There is no clear indication if a connection is established or not - could we do something about it? If there is an existing project, then you can see it. But currently there is none for the openshift-dev user by default. What makes is worse is the fact that once you start cdk, there is a little arrow next to the openshift connection as if you could expand it. When you do that, it will expand 1 line with "Loading.." and then it will suddenly disappear, so it really looks like something is wrong.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21871) Weird message in error log when connecting to cdk openshift - Unauthorized
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21871?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21871:
-------------------------------
Story Points: 5
> Weird message in error log when connecting to cdk openshift - Unauthorized
> ---------------------------------------------------------------------------
>
> Key: JBIDE-21871
> URL: https://issues.jboss.org/browse/JBIDE-21871
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Jeff MAURY
> Fix For: 4.4.x
>
> Attachments: secure-storage.png
>
>
> Everytime I start cdk and then want to connect to the openshift instance in OpenShift Explorer view, I get this info message in Error Log:
> Unauthorized. Trying to reauthenticate
> All the time I was thinking that the connection is actually not working, but then I tried to create a project and it worked.
> I can see a few issues here:
> 1. Why is this info message displayed even though the connection is actually established? It's confusing.
> 2. There is no clear indication if a connection is established or not - could we do something about it? If there is an existing project, then you can see it. But currently there is none for the openshift-dev user by default. What makes is worse is the fact that once you start cdk, there is a little arrow next to the openshift connection as if you could expand it. When you do that, it will expand 1 line with "Loading.." and then it will suddenly disappear, so it really looks like something is wrong.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months