June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4431) Update default server / runtime type

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4431?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-4431: ------------------------------------- OK, maybe I was wrong. I saw cdk 3 as the default type probably because it was already added as a server when I started devstudio - because ~/.minishift existed. Now I tried deleting that directory and starting devstudio with a new workspace and then the new server dialog started with eap 7.0 selected. Same with Preferences -> Server -> Runtime Environments and New - EAP 7.0 is selected. So I guess it works as expected then. > Update default server / runtime type > ------------------------------------ > > Key: JBDS-4431 > URL: https://issues.jboss.org/browse/JBDS-4431 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: product > Affects Versions: 10.4.0.GA > Reporter: Rob Stryker > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > > The plugin_customization.ini should be updated with the newest product server types that work (ie not tech-preview). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4431) Update default server / runtime type

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4431?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-4431. ------------------------------- > Update default server / runtime type > ------------------------------------ > > Key: JBDS-4431 > URL: https://issues.jboss.org/browse/JBDS-4431 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: product > Affects Versions: 10.4.0.GA > Reporter: Rob Stryker > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > > The plugin_customization.ini should be updated with the newest product server types that work (ie not tech-preview). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4431) Update default server / runtime type

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4431?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-4431: ------------------------------------- [~rob.stryker], [~nickboldt], what is the purpose of this? I would assume that this should ensure that when you open the New Server dialog, EAP 7.0 should be selected by default. But what if more plugin_customization.ini files exist? Right now in devstudio 11.0.0.AM1 the default server type in the New Server dialog is CDK 3. > Update default server / runtime type > ------------------------------------ > > Key: JBDS-4431 > URL: https://issues.jboss.org/browse/JBDS-4431 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: product > Affects Versions: 10.4.0.GA > Reporter: Rob Stryker > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > > The plugin_customization.ini should be updated with the newest product server types that work (ie not tech-preview). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24579) Can't import push-helloworld-cordova project

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-24579: ------------------------------------ Summary: Can't import push-helloworld-cordova project Key: JBIDE-24579 URL: https://issues.jboss.org/browse/JBIDE-24579 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, project-examples Affects Versions: 4.5.0.AM1 Environment: JBT 4.5.0.AM1 (stage) or devstudio-11.0.0.AM1-v20170622-1352-B295, Fedora 25 (wayland disabled), openjdk version "1.8.0_131" Reporter: Lukáš Valach Fix For: 4.5.0.AM2 Attachments: push-helloworld-cordova.png I can't install "push-helloworld-cordova" project from RH Central. During the installation I got a window with message *"push-helloworld-cordova project has not been fully imported. Check if it is defined correctly"*. I see that the project has been downloaded successfully but it wasn't imported (it isn't displayed in Project Explorer). I tried to import project from the disk into the Eclipse and it worked without problems. There is no error in the log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24540) Remove Openshift 2 tooling

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24540?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24540: ------------------------------------ +1 for the list of plugins/features to be removed. However, there are also some integration tests to be deleted and there are not stored in a separate plugin so this needs removing some classes from the openshift integration tests plugin > Remove Openshift 2 tooling > -------------------------- > > Key: JBIDE-24540 > URL: https://issues.jboss.org/browse/JBIDE-24540 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > End of support of Openshift 2 was in December 2016 [1] > There was a mail thread back in November/December 2016, where Todd stated, that Devstudio 11 would be the right release for dropping Openshift 2 support from Tools/Devstudio [2][3]. > Should we get PM/PgM approval once again just to be sure we are OK with removing Openshift 2 tooling from Tools/Devstudio? > [1] https://access.redhat.com/support/policy/updates/openshift/ > [2] http://post-office.corp.redhat.com/archives/devtools-program/2016-Novembe... > [3] http://post-office.corp.redhat.com/archives/devtools-program/2016-Decembe... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4432) Test optimization and enhancements

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4432?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4432: ------------------------------ Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) > Test optimization and enhancements > ---------------------------------- > > Key: JBDS-4432 > URL: https://issues.jboss.org/browse/JBDS-4432 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 11.0.0.AM2 > > > See subtasks for details -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4432) Test optimization and enhancements

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4432?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4432: ------------------------------ Sprint: (was: devex #133 Jun 2017) > Test optimization and enhancements > ---------------------------------- > > Key: JBDS-4432 > URL: https://issues.jboss.org/browse/JBDS-4432 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 11.0.0.AM1 > > > See subtasks for details -- 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 Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24291?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24291: --------------------------------------- [~aurelien.pupier], just the server name is not enough - open.paas.redhat.com. I don't know what details to enter to create this connection. But you're right, even with EAP it now only shows 0 % and then it loads. So I guess that's a regression. I was even able to reproduce the expanded view, then collapsing all, then disconnect and then connect - it expands everything again. But only if you do it exactly as in the video - you also need to refresh first. So it goes like this: 1. Connect JMX (e.g. EAP 6.4) 2. Expand all the way to some mbeans 3. Refresh the connection 4. Collapse everything so that only MBeans is visible under the connection 5. Disconnect 6. Connect Now everything will be expanded as it was before you collapsed it > 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-21727) add OpenShift server adapter to downloadable WTP server adapters

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21727?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21727: ------------------------------------ Too late to change in upstream as WTP 3.9.0 is done for Oxygen.0. Is we want to recategorize something we can suggest it for Oxygen.x or Photon.0.MX Note that this JIRA has sat for more than a year so I don't know if it's really a problem. :) > add OpenShift server adapter to downloadable WTP server adapters > ---------------------------------------------------------------- > > Key: JBIDE-21727 > URL: https://issues.jboss.org/browse/JBIDE-21727 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: compositeArtifacts.xml, compositeContent.xml, mockup-change-1.png, mockup-change-2.png, openshiftv3-tools-server-adapter-manually-installed.png, openshiftv3-tools-server-adapter-no-license-found.png, openshiftv3-tools-server-adapter.png, screenshot-1.png > > > We have JBoss server adapters available in Eclise new Server wizard; would be great if we could put OpenShift in there too. > Anything preventing us from doing so ? > Is there a workflow from New server that helps users to create openshift connection etc. ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs

by Mikhail Kalkov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugi... ] Mikhail Kalkov commented on JBIDE-22878: ---------------------------------------- Thanks for fixing this, guys! I've moved on to another project and we're still running JBDS 10.4 here, so I cannot spend time on installing JBDS 11.0 just to verify this fix right now. However, I concur with Martin that version number in GUI is just a minor nuisance and the real issue had to do wtih produced artifacts. So, I'm happy that it seems to be solved now. > EAR deployed from DevStudio to EAP contains errorneously named ejbs > ------------------------------------------------------------------- > > Key: JBIDE-22878 > URL: https://issues.jboss.org/browse/JBIDE-22878 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: JBIDE-22878-deployment-assembly.png, screendump.png, test-ear.ear, test-projects.zip > > > I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar. > When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot. > This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml as well as possibly fix filenames in persistence.xml, and remember to revert these changes before committing! -- 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