[JBoss JIRA] (JBIDE-24042) Provide bigger dialog for adding header of a Jolokia JMX Connection
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24042?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-24042:
--------------------------------
Sprint: devex #129 March 2017
> Provide bigger dialog for adding header of a Jolokia JMX Connection
> -------------------------------------------------------------------
>
> Key: JBIDE-24042
> URL: https://issues.jboss.org/browse/JBIDE-24042
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jmx
> Affects Versions: 4.4.3.Final
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.4.AM2, 4.5.0.AM1
>
> Attachments: image-2017-03-08-10-23-23-647.png, image-2017-03-08-10-23-23-647.png
>
>
> currently, even the title is not completely visible:
> !image-2017-03-08-10-23-23-647.png|thumbnail! !image-2017-03-08-10-23-23-647.png|thumbnail!
> would be nice to have more space for fields too, at least to file some token stuff which would be quite a classical header that will be provided. If there are Jolokia expert would be nice to ask them the maximum size of common values to determine the best size
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23403) As a user I need to be able to inspect the state of my EAP deployments
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23403?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23403:
------------------------------------------
[~rob.stryker] we dont have any tooling that would allow us to inspect deployments in wildfly/eap (via management api), dont we?
> As a user I need to be able to inspect the state of my EAP deployments
> ----------------------------------------------------------------------
>
> Key: JBIDE-23403
> URL: https://issues.jboss.org/browse/JBIDE-23403
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: openshift_v3, server, web_console
> Fix For: 4.4.4.AM2
>
>
> The web console for eap was disabled in the eap image that we have in OpenShift. It's therefore not possible for users to inspect the state of their deployment.
> The only there is to do such thing is to inspect jolokia informations. There is no such tooling in Eclipse yet. Furthermore the url to access those is non-obvious as one can see [here|http://developers.redhat.com/blog/2016/03/30/jolokia-jvm-monitoring-...]. I therefore suggest that we should provide help/tooling that allows users to easily access and manipulate those informations.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24084) To succesfully start CDKv3 Server adapter with hyperV provider, IDE muse be start with admin rights
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24084?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24084:
----------------------------------
Priority: Critical (was: Major)
> To succesfully start CDKv3 Server adapter with hyperV provider, IDE muse be start with admin rights
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24084
> URL: https://issues.jboss.org/browse/JBIDE-24084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.4.AM1
> Environment: Windows 10 Pro, x86_64
> HyperV allowed
> Reporter: Ondrej Dockal
> Priority: Critical
>
> One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE.
> I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly.
> Following steps to reproduce will lead to successfully started CDK3 server adapter in IDE.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-3799) Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3799?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3799:
-----------------------------------
Not that I remember. I guess it's something ancient.
> Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-3799
> URL: https://issues.jboss.org/browse/JBDS-3799
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Priority: Critical
> Labels: havoc
> Fix For: 10.4.0.AM2
>
>
> This unresolved issue: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/272
> Is causing rsync issues such as:
> default: Rsyncing folder: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> There was an error when attempting to rsync a synced folder.
> Please inspect the error message below for more info.
> Host path: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/
> Guest path: /vagrant
> Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant
> Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts.
> dup() in/out/err failed
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-20529:
----------------------------------
Assignee: Andre Dietisheim (was: Rob Stryker)
> Master JIRA for XML Validation Problems
> ---------------------------------------
>
> Key: JBIDE-20529
> URL: https://issues.jboss.org/browse/JBIDE-20529
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: project-examples, server
> Reporter: Rob Stryker
> Assignee: Andre Dietisheim
> Labels: xtriage
> Fix For: 4.4.4.AM2
>
>
> This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20529:
-------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.4.Final)
> Master JIRA for XML Validation Problems
> ---------------------------------------
>
> Key: JBIDE-20529
> URL: https://issues.jboss.org/browse/JBIDE-20529
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: project-examples, server
> Reporter: Rob Stryker
> Assignee: Andre Dietisheim
> Labels: xtriage
> Fix For: 4.4.4.AM2
>
>
> This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20529:
-------------------------------
Sprint: devex #129 March 2017
> Master JIRA for XML Validation Problems
> ---------------------------------------
>
> Key: JBIDE-20529
> URL: https://issues.jboss.org/browse/JBIDE-20529
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: project-examples, server
> Reporter: Rob Stryker
> Assignee: Andre Dietisheim
> Labels: xtriage
> Fix For: 4.4.4.AM2
>
>
> This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years