[JBoss JIRA] (JBIDE-24138) Implement queryMbeans for Jolokia
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24138?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24138:
---------------------------------------
[~aurelien.pupier] so that means that it will still take some time until you can verify, correct? I don't like having this linger in the verification filter, but I'm not sure how to avoid. Because changing the fix version does not seem right.
> Implement queryMbeans for Jolokia
> ---------------------------------
>
> Key: JBIDE-24138
> URL: https://issues.jboss.org/browse/JBIDE-24138
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jmx
> Affects Versions: 4.4.4.AM1
> Reporter: Aurélien Pupier
> Assignee: Aurélien Pupier
> Fix For: 4.4.4.AM3
>
>
> Currently JolokiaMBeanServerConnection.queryMBeans is not implemented
> @Override
> public Set<ObjectInstance> queryMBeans(ObjectName name, QueryExp query) throws IOException {
> // TODO Auto-generated method stub
> return null;
> }
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24271) Runtime search dialog has too many labels
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24271?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24271.
---------------------------------
OK, I agree it's a bit improved now. When the search is finished, there is just one line with the summary at the top and another line saying search is finished. Verified in devstudio 10.4.0.AM3.
> Runtime search dialog has too many labels
> -----------------------------------------
>
> Key: JBIDE-24271
> URL: https://issues.jboss.org/browse/JBIDE-24271
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.4.4.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM3
>
> Attachments: JBIDE-24271.png
>
>
> WHile investigating JBIDE-24230 it became clear to me the runtime search dialog had very weird things going on. There were clearly too many labels and it made no sense what exactly was going on. My attempts to update one label were in fact updating a different label. It turns out, multiple labels were created and stored in the same variable after some they had values set on them. This led to a very weird appearance.
> Screenshot to come.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ERT-505) Attempt to install cordova plugin: Could not find *-Info.plist file, or config.xml file. [EBZ#515753]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-505:
---------------------------------------
Summary: Attempt to install cordova plugin: Could not find *-Info.plist file, or config.xml file. [EBZ#515753]
Key: ERT-505
URL: https://issues.jboss.org/browse/ERT-505
Project: Eclipse Release Train
Issue Type: Task
Components: Thym
Reporter: Friendly Jira Robot
Fix For: Neon (4.6)
Created attachment 267965
screenshot.png
Steps to reproduce:
1) Create thym project
2) Run wizard, right click project and select "Install Cordvoa Plug-In"
3) select cordova-admin-device
3) click next, click back
4) click finish
5) see error
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-21065 at 4/25/17 6:13 AM:
----------------------------------------------------------------
Unfortunately Xavier's use case still does not work. I tried this:
1. Open New Server Wizard
2. Select EAP 6.1+
3. Enter an IP address in the hostname field
4. Proceed and create the server
5. Open server editor - hostname is set to localhost :(
This was with devstudio 10.4.0.AM3.
was (Author: mmalina):
Unfortunately Xavier's use case still does not work. I tried this:
1. Open New Server Wizard
2. Select EAP 6.1+
3. Enter an IP address in the hostname field
4. Proceed and create the server
5. Open server editor - hostname is set to localhost :(
> Server host name address should not be defaulted during server adapter creation
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21065
> URL: https://issues.jboss.org/browse/JBIDE-21065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM3
>
>
> I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}.
> This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address.
> Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21065:
---------------------------------------
It seems you haven't created a tracking issue for the upstream bug, so I did that here: JBIDE-24302
> Server host name address should not be defaulted during server adapter creation
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21065
> URL: https://issues.jboss.org/browse/JBIDE-21065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM3
>
>
> I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}.
> This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address.
> Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24302) Circular fragment workflow for optional runtime use case
by Martin Malina (JIRA)
Martin Malina created JBIDE-24302:
-------------------------------------
Summary: Circular fragment workflow for optional runtime use case
Key: JBIDE-24302
URL: https://issues.jboss.org/browse/JBIDE-24302
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server, upstream
Affects Versions: 4.5.0.AM1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.5.0.AM1
This is a tracking issue for this upstream bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=514888
Rob's description:
While playing with the changes dropped for Bug 513486, I found a small bug.
When a runtime is optional, the wtp framework does not add the runtime fragment directly. It will only add the server fragment, and assume that the server fragment will introduce the runtime fragment in the workflow as it chooses.
A workflow was discovered where the NewServerWizardFragment is still adding the runtime fragment before the server fragment. Since the server may also be adding that fragment later, it leads to circular behavior because the runtime fragment is in the list of fragments twice. The user will then press next continually but never advance.
Sorry for this bug. It only happens under specific situations.
Workflow:
1) new server wizard, choose server type with optional runtime
2) Go forward, change settings in server fragment, causing server fragment to designate runtime fragment as a child
3) go back to main page of server wizard to change host
4) Change host to 127.0.0.1
5) Press forward, forward, forward, etc. never ends.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24301) Error While Executing jbosstools-openshift-4.4.3
by jyoti tumsare (JIRA)
jyoti tumsare created JBIDE-24301:
-------------------------------------
Summary: Error While Executing jbosstools-openshift-4.4.3
Key: JBIDE-24301
URL: https://issues.jboss.org/browse/JBIDE-24301
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build
Affects Versions: 4.4.3.Final
Environment: To build jbosstools-openshift-4.4.3 I followed following steps
1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3.
2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found".
3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue.
Reporter: jyoti tumsare
Attachments: issues.txt
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24231) Unable to accept T&C when downloading EAP 7 in Eclipse
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24231?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24231.
---------------------------------
I still find it a bit cumbersome. It's quite strange to be logging into the web page inside the wizard. I tried right-clicking the link and selecting Open in new Window, but that didn't do anything. So I accepted it inside that window. And it worked. Still, it's not very nice. But I guess it works. So.
> Unable to accept T&C when downloading EAP 7 in Eclipse
> ------------------------------------------------------
>
> Key: JBIDE-24231
> URL: https://issues.jboss.org/browse/JBIDE-24231
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.4.4.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM3
>
>
> I few days ago when I tried to download EAP 7 in JBoss Tools 4.4.0.AM2 while testing it, I was faced with this message instead of the T&C in the wizard:
> It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!
> I used my redhat.com account (mmalina1 at redhat.com). What's also curious is that I used this account many times in the past, so it's strange that I was required to accept the T&C in the first place.
> I was able to log in inside that window (where normally just the text would be displayed) and then got this message:
> {code}
> You Entered All Necessary Information
> Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip.
> {code}
> When I went back and forth, I was then able to download the runtime successfully. So I'm afraid I won't be able to reproduce this unless somebody resets my account.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months