June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24593) Reconnect to jmx yields progress monitor errors

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24593?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24593: -------------------------------- Attachment: JMXLoad.mp4 > Reconnect to jmx yields progress monitor errors > ----------------------------------------------- > > Key: JBIDE-24593 > URL: https://issues.jboss.org/browse/JBIDE-24593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Fix For: 4.5.0.AM2 > > Attachments: JMXLoad.mp4 > > > when I connect, expand some nodes, call refresh, collapse them then disconnect then reconnect, all the previously expanded node are loaded with a progress monitor which is not showing progress and stay blocked at 0% -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24291) Improve initial loading of JMX Connection tree

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24291?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-24291. --------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.5.0.AM2) Resolution: Done This was fixed in AM1. Please see JBIDE-24593 for what you consider to still be broken. > Improve initial loading of JMX Connection tree > ---------------------------------------------- > > Key: JBIDE-24291 > URL: https://issues.jboss.org/browse/JBIDE-24291 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: JMXLoad.mp4 > > > JMX Navigator is taking quite a long time to load the first level of elements when the connection is targeting a remote server with quite a high latency (such open.paas.redhat.com which is taking around 450ms for each request for me) > It would be nice to improve the lazy-loading to be able to display the first level of the tree without loading every MBeans and doing one query per MBean Names registered on the server. > For instance on a FIS project, it is 112 MBean Names * 450ms = 50.4s! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24593) Reconnect to jmx yields progress monitor errors

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-24593: ----------------------------------- Summary: Reconnect to jmx yields progress monitor errors Key: JBIDE-24593 URL: https://issues.jboss.org/browse/JBIDE-24593 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 4.5.0.AM1 Reporter: Rob Stryker when I connect, expand some nodes, call refresh, collapse them then disconnect then reconnect, all the previously expanded node are loaded with a progress monitor which is not showing progress and stay blocked at 0% -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24593) Reconnect to jmx yields progress monitor errors

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24593?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24593: -------------------------------- Fix Version/s: 4.5.0.AM2 > Reconnect to jmx yields progress monitor errors > ----------------------------------------------- > > Key: JBIDE-24593 > URL: https://issues.jboss.org/browse/JBIDE-24593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Fix For: 4.5.0.AM2 > > > when I connect, expand some nodes, call refresh, collapse them then disconnect then reconnect, all the previously expanded node are loaded with a progress monitor which is not showing progress and stay blocked at 0% -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24573) Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24573?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24573: ------------------------------------- Are you able to attach a slimmed-down example project that suffers the same problem? Are you using m2e-wtp to help integrate the maven and wtp profiles? > Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin > ---------------------------------------------------------------------------- > > Key: JBIDE-24573 > URL: https://issues.jboss.org/browse/JBIDE-24573 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server, upstream > Affects Versions: 4.4.4.Final > Environment: windows 7 eclipse neon maven > Reporter: stefano canu > > I 'm tryng to deploy to wildfly 10 an ear project (maven) composed by one war and one jar (ejb) project, but the ear deployed with eclipse wildfly connector is different form one present in the target foleder, library in web-inf lib is missing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24535) itests are not run for server in Jenkins

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24535?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24535: ------------------------------------- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > itests are not run for server in Jenkins > ---------------------------------------- > > Key: JBIDE-24535 > URL: https://issues.jboss.org/browse/JBIDE-24535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > I wanted to verify JBIDE-24483 which added itests for incremental deployment via management. But it turns out none of the itests are run here: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Shouldn't they be run? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24581) suppress old pre-Final/pre-GA milestones from the downloads overview page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24581?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24581: ------------------------------------ Fixed: http://tools.stage.jboss.org/documentation/whatsnew/index.html Pushing to prod now too. > suppress old pre-Final/pre-GA milestones from the downloads overview page > ------------------------------------------------------------------------- > > Key: JBIDE-24581 > URL: https://issues.jboss.org/browse/JBIDE-24581 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, website > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Recently I commented out a lot of old releases because they're old. > But as a result the what's new page [1] now shows a ton of old milestones as coming soon. > So we either need to hide old milestones from the what's new page, or find a way to suppress builds from appearing on the downloads page [2]. > [1] http://tools.jboss.org/documentation/whatsnew/ > [2] http://tools.jboss.org/downloads/overview.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24548) Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24548?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-24548: ------------------------------------------ the linked issue is fixed and now syncing of code works fine for wildfly. Still, want to add the default value to our tools to avoid this issue again. > Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly > -------------------------------------------------------------------------------- > > Key: JBIDE-24548 > URL: https://issues.jboss.org/browse/JBIDE-24548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Environment: Running on Mac 10.12.4 > JBDS > Version: 10.3.0.GA > Build id: GA-v20170218-1636-B94 > Build date: 20170218-1636 > Installed minishift v1.0.1 > Reporter: Veer Muchandi > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > > * Created a Wildfly application on openshift web-ui > * Setup a server adapter > * Imported application to JBDS > * Made code changes and saved. > Result: > While the data seems to be exchanged, the changes are not synced with the pod and the application is not updated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4422) Rename RPM package to rh-eclipse47-devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4422?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4422: ----------------------------- Story Points: 10 > Rename RPM package to rh-eclipse47-devstudio > -------------------------------------------- > > Key: JBDS-4422 > URL: https://issues.jboss.org/browse/JBDS-4422 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: rpm > Affects Versions: 11.0.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.AM2 > > Attachments: build.log.txt, core.runtime.note.resolved.started-config.ini.log.txt, root.log.txt > > > Devstudio RPM should be renamed to "rh-eclipse47-devstudio". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24243) migrate Fuse Tools builds to JBT infrastructure/process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24243: ------------------------------- Story Points: 21 (was: 7) > migrate Fuse Tools builds to JBT infrastructure/process > ------------------------------------------------------- > > Key: JBIDE-24243 > URL: https://issues.jboss.org/browse/JBIDE-24243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, fuse-tooling, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Fuse Tooling currently has jobs under this view: https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/staging/builds/integration-stac... > ** https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/integration/updates/integration... > which publish integration, development or stable update sites. > As part of the migration of Fuse Tooling into JBoss Tools 4.5 for Oxygen, this path will change to something like: > * http://download.jboss.org/jbosstools/*oxygen*/snapshots/builds/fuse-tooling/ > * http://download.jboss.org/jbosstools/*oxygen*/staging/updates/fuse-tooling/ > We will also need to ensure that JBT composites/aggregates are configured to pick up these features/plugins. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2017