June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19500. ------------------------------- Verified with JBDS 9.0.0.Beta1-v20150605-2014-B34 > warn/inform users running on non-compatilbe JVMs they are loosing out on features > --------------------------------------------------------------------------------- > > Key: JBIDE-19500 > URL: https://issues.jboss.org/browse/JBIDE-19500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: JVMProblemDetector.png, JVMProblemDetector2.png > > > while reading https://developer.jboss.org/message/922318?et=watches.email.thread#922318 I got the idea that we could have a startup plugin that detects if the error log has lines matching: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.preferences [1447] > Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))" > {code} > and there by tell them that they need to run JavaSE 1.7 to get this to work. > This dialog should show up and have "don't disturb me again" for the specific bundle/feature that is filtered out. > This is to warn those users that run ecipse with default javavm that still is java 6 on many installs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19969) JMX plugins have wrong provider?

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19969?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-19969: ------------------------------------- Assignee: Rob Stryker > JMX plugins have wrong provider? > -------------------------------- > > Key: JBIDE-19969 > URL: https://issues.jboss.org/browse/JBIDE-19969 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Attachments: plugins-provider.png > > > Vlado noticed today that some plugins have strange provider. > (All features have "JBoss by Red Hat" as their provider.) > Some JMX plugins have: > JvmMonitor.org > One has: > Jeff Mesnil > [~rob.stryker], can you check if this is correct? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19969) JMX plugins have wrong provider?

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19969?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19969: ---------------------------------- Attachment: plugins-provider.png Screenshot: !plugins-provider.png! > JMX plugins have wrong provider? > -------------------------------- > > Key: JBIDE-19969 > URL: https://issues.jboss.org/browse/JBIDE-19969 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Attachments: plugins-provider.png > > > Vlado noticed today that some plugins have strange provider. > (All features have "JBoss by Red Hat" as their provider.) > Some JMX plugins have: > JvmMonitor.org > One has: > Jeff Mesnil > [~rob.stryker], can you check if this is correct? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19969) JMX plugins have wrong provider?

by Martin Malina (JIRA)

Martin Malina created JBIDE-19969: ------------------------------------- Summary: JMX plugins have wrong provider? Key: JBIDE-19969 URL: https://issues.jboss.org/browse/JBIDE-19969 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 4.3.0.Beta1 Reporter: Martin Malina Vlado noticed today that some plugins have strange provider. (All features have "JBoss by Red Hat" as their provider.) Some JMX plugins have: JvmMonitor.org One has: Jeff Mesnil [~rob.stryker], can you check if this is correct? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19893) Enhancement: utility methods for wizards

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19893?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19893. ------------------------------- Verified on github > Enhancement: utility methods for wizards > ---------------------------------------- > > Key: JBIDE-19893 > URL: https://issues.jboss.org/browse/JBIDE-19893 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > > Moved the util methods from openshift to common. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19710) Add new caching strategy in URLTransportUtility

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19710?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19710. ------------------------------- Verified > Add new caching strategy in URLTransportUtility > ----------------------------------------------- > > Key: JBIDE-19710 > URL: https://issues.jboss.org/browse/JBIDE-19710 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > Currently, you can use URLTransportUtility like > new URLTransportUtility().getCachedFileForURL(url, "Download stuff", lifespan, monitor); > with lifespan possible values being : > - URLTransportUtility.CACHE_UNTIL_EXIT : will cache the file during the workspace session > - URLTransportUtility.CACHE_FOREVER : will cache the file forever once downloaded > In certain cases, we want to be able to use CACHE_UNTIL_EXIT, but also be able to recover from network outages. So adding something like > - URLTransportUtility.SAFE_CACHE_UNTIL_EXIT (feel free to find a better name) : if the remote file is available, it will be downloaded on new Eclipse session, if it's not, the last valid cache will be returned. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19460) No provider for o.j.t.vpe.browsersim.javafx.mock

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19460?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19460. ------------------------------- Verified with JBDS 9.0.0.Beta1-v20150605-2014-B34 > No provider for o.j.t.vpe.browsersim.javafx.mock > ------------------------------------------------ > > Key: JBIDE-19460 > URL: https://issues.jboss.org/browse/JBIDE-19460 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.3.CR1 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Beta1 > > > Provider should be *JBoss by Red Hat*, not *null*. > !https://issues.jboss.org/secure/attachment/12388322/810cr1-redux-plugins.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19947) OpenShift v3 plugin can't work after update

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19947?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-19947: --------------------------------------- Well. Issue with JDK is, that our batch component requires JDK 8 (or its dependency requires it, I am not quite sure at the moment, cos. I am not involved in batch). So if you were installing and using to run java 7 previously and then you changed your java to java 8, it's possible it is not backward compatible. Could you please at least give us error log after opening OpenShift Explorer view? To have stack trace of the issue. Thanks And to the related update issues, maybe [~nickboldt] can bring more clarity into this? > OpenShift v3 plugin can't work after update > ------------------------------------------- > > Key: JBIDE-19947 > URL: https://issues.jboss.org/browse/JBIDE-19947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Ma Deshuai > Attachments: error1.jpg, error2.jpg, error3.jpg > > > Description of problem: > After update openshift v3 plugin from uri:http://download.jboss.org/jbosstools/updates/nightly/mars/. Can't open openshift v3 plug in eclipse. > Version-Release number of selected component (if applicable): > Eclipse: mars > Jdk: 1.7 > OpenShift plug : 3.0.0.Beta1-v20150604-1037-B825 > How reproducible: > Always > Steps to Reproduce: > 1.Update OpenShift v3 plugin from http://download.jboss.org/jbosstools/updates/nightly/mars/ > 2.Restart eclipse and open "OpenShift Explorer" > Actual results: > 2.Open "OpenShift Explorer" with error > Could not create the view: org.jboss.tools.openshift.express.ui.explorer.expressConsoleView > Expected results: > 2.Open "OpenShift Explorer" corectly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19787) As a user I want to import existing OpenShift projects into my Eclipse workspace

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19787?page=com.atlassian.jira.plugi... ] Ma Deshuai commented on JBIDE-19787: ------------------------------------ [~adietish] The context item name of "Import Application..." display incorrectly. seen this: https://issues.jboss.org/browse/JBIDE-19968 > As a user I want to import existing OpenShift projects into my Eclipse workspace > -------------------------------------------------------------------------------- > > Key: JBIDE-19787 > URL: https://issues.jboss.org/browse/JBIDE-19787 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: import_wizard, new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: import-application-2.png, import-application-3.png, import-application.png > > > This is the case where a user has added resources via the CLI or console and wants to create an Eclipse project in order to start developing. > The Eclipse project nature will be of the appropriate type as inferred from the source. > Main focus is to correctly import java/maven projects or “General” project otherwise. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19968) The context item "Import Application..." in OpenShift explorer dispaly error.

by Ma Deshuai (JIRA)

Ma Deshuai created JBIDE-19968: ---------------------------------- Summary: The context item "Import Application..." in OpenShift explorer dispaly error. Key: JBIDE-19968 URL: https://issues.jboss.org/browse/JBIDE-19968 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Ma Deshuai Attachments: Import.png Description of problem: The context item of "Import Application..." display error. Version-Release number of selected component (if applicable): openshift-v3 plug: 3.0.0.Beta2-v20150606-0237-B829 How reproducible: Always. Steps to Reproduce: 1. Connect to the openshift server in jbt 2. Import existing OpenShift projects into Eclipse workspace 1) Select a connection or a project and right click 2) Pick "Import Application" from the context menu. Actual results: 2.2 The context item name should be "Import Application..." Expected results: 2.2 The context item name is "%openshift.command.application.import" Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 2015