[JBoss JIRA] (JBIDE-17989) keyword used for plugin tracking is missing majority of times on GA
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17989?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17989:
-----------------------------------
Sprint: Sprint #3 May 2015 (was: Sprint #3 May 2015, Sprint #4 May 2015)
> keyword used for plugin tracking is missing majority of times on GA
> -------------------------------------------------------------------
>
> Key: JBIDE-17989
> URL: https://issues.jboss.org/browse/JBIDE-17989
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: usage
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
> Attachments: devstudio-january.png, graphformissingstats.png, jbds.png, scr.png
>
>
> looking at tracking numbers i'm seeing more and more requests where the keywords are not making it into the result.
> Meaning we can't see how many have installed the various plugins.
> What is weird *some* do and others do not have it.
> Need to track down the reason for that being missed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-17989) keyword used for plugin tracking is missing majority of times on GA
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17989?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17989:
-----------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> keyword used for plugin tracking is missing majority of times on GA
> -------------------------------------------------------------------
>
> Key: JBIDE-17989
> URL: https://issues.jboss.org/browse/JBIDE-17989
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: usage
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
> Attachments: devstudio-january.png, graphformissingstats.png, jbds.png, scr.png
>
>
> looking at tracking numbers i'm seeing more and more requests where the keywords are not making it into the result.
> Meaning we can't see how many have installed the various plugins.
> What is weird *some* do and others do not have it.
> Need to track down the reason for that being missed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19898) Error displayed on initial connection to an OpenShift Server for a new eclipse session
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-19898:
-------------------------------------
Summary: Error displayed on initial connection to an OpenShift Server for a new eclipse session
Key: JBIDE-19898
URL: https://issues.jboss.org/browse/JBIDE-19898
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta2
Reporter: Jeff Cantrill
# Create a connection to a v3 instance of openshift
# Restart Eclipse
# Open the OpenShift explorer view
# Expand the previously created connection
# Notice an error like: "system:anonymous..."
Is this related to token's not being saved? It should either go through the sequence to establish a new token or connect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19897) Remove check server type
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19897?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-19897:
----------------------------------
Description: In JBIDE-19829 we disabled the "Check Server Type" button that was detecting the server type (v2 or v3) for a given server url. We should now remove the widget and the related code. (was: In JBIDE-19829 we disabled the "Check Server Type" button that was detecting the server type (v2 or v3) for a given server url. We should now remote the widget and the related code.)
> Remove check server type
> ------------------------
>
> Key: JBIDE-19897
> URL: https://issues.jboss.org/browse/JBIDE-19897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: connection_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: check-server-type-disabled.png
>
>
> In JBIDE-19829 we disabled the "Check Server Type" button that was detecting the server type (v2 or v3) for a given server url. We should now remove the widget and the related code.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19897) Remove check server type
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19897?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-19897:
---------------------------------------
cc [~adietish]
> Remove check server type
> ------------------------
>
> Key: JBIDE-19897
> URL: https://issues.jboss.org/browse/JBIDE-19897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: connection_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: check-server-type-disabled.png
>
>
> In JBIDE-19829 we disabled the "Check Server Type" button that was detecting the server type (v2 or v3) for a given server url. We should now remote the widget and the related code.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on JBIDE-19641:
------------------------------------------
What version of the model-controller-client module is being used here? If there's any variation in the dependencies of that module from the standard ones it shipped with, please note those as well.
Also, [~mmalina] what version of the CLI was used? Same version? If not, the fact some CLI works doesn't tell us much. If the CLI from the same version as model-controller-client doesn't work though, that should help tremendously in figuring out the problem.
> Big war deployment via management API gets stuck
> ------------------------------------------------
>
> Key: JBIDE-19641
> URL: https://issues.jboss.org/browse/JBIDE-19641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
> Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log
>
>
> When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through.
> This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months