March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19452) extension point for editors to tell html5 preview which html content to render

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19452?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-19452: ------------------------------------------- Fix Version/s: 4.3.0.Alpha2 > extension point for editors to tell html5 preview which html content to render > ------------------------------------------------------------------------------ > > Key: JBIDE-19452 > URL: https://issues.jboss.org/browse/JBIDE-19452 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha2 > > > html preview seem to figure out that text from structured editor is the actual document in the editor. > But when you have something like the Visual JSF Page Editor or Mylyn wiki text editor where the html content is actually not in the main document but something generated html preview does not work. > it would be great if html5 preview would have an extension point where one can install a handler for a specific editor what html should be shown in the preview. > end result: when opening mylyn wiki text editor it should show what corresponds to the Preview tab, not the source tab. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19447) Constraint violation resolving org.jboss.tools.browsersim.ui

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19447?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-19447: ------------------------------------------- Fix Version/s: 4.3.0.Alpha2 > Constraint violation resolving org.jboss.tools.browsersim.ui > ------------------------------------------------------------ > > Key: JBIDE-19447 > URL: https://issues.jboss.org/browse/JBIDE-19447 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha2 > > > Build is OK, and publish is working, but tests are failing: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-browsersim_master/136/console} > 00:04:56.920 !ENTRY org.jboss.tools.browsersim.eclipse 4 0 2015-03-13 08:51:58.758 > 00:04:56.920 !MESSAGE FrameworkEvent ERROR > 00:04:56.920 !STACK 0 > 00:04:56.920 org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [265] > 00:04:56.920 Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.3.0" > 00:04:56.921 -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true" > 00:04:56.921 org.jboss.tools.browsersim.ui [266] > 00:04:56.921 Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.javafx.mock; bundle-version="3.6.0"; resolution:="optional" > 00:04:56.921 Bundle was not resolved because of a uses contraint violation. > 00:04:56.921 org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"] because it is exposed to package 'org.eclipse.jetty.util.component' from resources org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="9.2.5.v20141112"] and org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] via two dependency chains. > 00:04:56.922 > 00:04:56.922 Chain 1: > 00:04:56.922 org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"] > 00:04:56.923 require: (&(osgi.wiring.bundle=org.eclipse.jetty.util)(bundle-version>=8.1.14)) > 00:04:56.923 | > 00:04:56.923 provide: osgi.wiring.bundle: org.eclipse.jetty.util > 00:04:56.923 org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="9.2.5.v20141112"] > 00:04:56.923 > 00:04:56.923 Chain 2: > 00:04:56.923 org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"] > 00:04:56.924 require: (&(osgi.wiring.bundle=org.eclipse.jetty.websocket)(bundle-version>=8.1.14)) > 00:04:56.924 | > 00:04:56.924 provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.jetty.websocket"; bundle-version:Version="8.1.14.v20131031" > 00:04:56.924 org.eclipse.jetty.websocket [osgi.identity; osgi.identity="org.eclipse.jetty.websocket"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] > 00:04:56.924 import: (&(osgi.wiring.package=org.eclipse.jetty.io)(&(version>=8.1.0)(!(version>=9.0.0)))) > 00:04:56.924 | > 00:04:56.925 export: osgi.wiring.package=org.eclipse.jetty.io; uses:=org.eclipse.jetty.util.log > 00:04:56.925 org.eclipse.jetty.io [osgi.identity; osgi.identity="org.eclipse.jetty.io"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] > 00:04:56.925 import: (&(osgi.wiring.package=org.eclipse.jetty.util.log)(&(version>=8.1.0)(!(version>=9.0.0)))) > 00:04:56.925 | > 00:04:56.925 export: osgi.wiring.package: org.eclipse.jetty.util.log; uses:=org.eclipse.jetty.util.component > 00:04:56.925 export: osgi.wiring.package=org.eclipse.jetty.util.component > 00:04:56.925 org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] > 00:04:56.926 at org.eclipse.osgi.container.Module.start(Module.java:434) > 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > 00:04:56.927 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > 00:04:56.927 at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > 00:04:56.927 at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340){code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19500: ---------------------------------------- Component/s: common/jst/core > 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 > > 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.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19522) Snapshot restore app from different type archive does not pop up with failure info .

by Yanping Zhang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19522?page=com.atlassian.jira.plugi... ] Yanping Zhang updated JBIDE-19522: ---------------------------------- Summary: Snapshot restore app from different type archive does not pop up with failure info . (was: Snapshot save app from different type archive does not pop up with failure info .) > Snapshot restore app from different type archive does not pop up with failure info . > ------------------------------------------------------------------------------------ > > Key: JBIDE-19522 > URL: https://issues.jboss.org/browse/JBIDE-19522 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.3.CR1 > Environment: JBoss Developer Studio 8.1.0 Beta1 > Reporter: Yanping Zhang > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19523) Can't check server type in jboss tools Connection Wizard Dialog

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19523?page=com.atlassian.jira.plugi... ] Ma Deshuai updated JBIDE-19523: ------------------------------- Tester: (was: Andre Dietisheim) > Can't check server type in jboss tools Connection Wizard Dialog > --------------------------------------------------------------- > > Key: JBIDE-19523 > URL: https://issues.jboss.org/browse/JBIDE-19523 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: Version-Release number of selected component (if applicable): > jbt version: /nightly/mars/2015-03-26_16-23-29-B9619 > eclipse version: mars(4.5.0M5) > openshift-plug version: 3.0.0.Alpha2-v20150325-0237-B742 > Reporter: Ma Deshuai > Priority: Blocker > Labels: connection_wizard > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19523) Can't check server type in jboss tools Connection Wizard Dialog

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19523?page=com.atlassian.jira.plugi... ] Ma Deshuai updated JBIDE-19523: ------------------------------- Tester: Andre Dietisheim > Can't check server type in jboss tools Connection Wizard Dialog > --------------------------------------------------------------- > > Key: JBIDE-19523 > URL: https://issues.jboss.org/browse/JBIDE-19523 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: Version-Release number of selected component (if applicable): > jbt version: /nightly/mars/2015-03-26_16-23-29-B9619 > eclipse version: mars(4.5.0M5) > openshift-plug version: 3.0.0.Alpha2-v20150325-0237-B742 > Reporter: Ma Deshuai > Priority: Blocker > Labels: connection_wizard > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19520) Unable to establish a connection in v2 or v3

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19520?page=com.atlassian.jira.plugi... ] Ma Deshuai commented on JBIDE-19520: ------------------------------------ [~adietish] I also file another related bug above. Can you help to resolve? > Unable to establish a connection in v2 or v3 > -------------------------------------------- > > Key: JBIDE-19520 > URL: https://issues.jboss.org/browse/JBIDE-19520 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Priority: Blocker > Labels: connection_wizard > Fix For: 4.3.0.Alpha2 > > > After installing v2 and v3 plugin, unable to establish a connection in v2 or v3. > Noticed: > * Creds are visible initially for v2 but disappear and never reappear after flipping back and forth between v2 and v3 > * Trying a v2 connection after entering a URL never connects > * Canceling the v2 connection the URL text box is repopulated with the default URL, I suspect 'trying to connect' is not getting the URL that was entered -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19523) Can't check server type in jboss tools Connection Wizard Dialog

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19523?page=com.atlassian.jira.plugi... ] Ma Deshuai updated JBIDE-19523: ------------------------------- Labels: connection_wizard (was: ) > Can't check server type in jboss tools Connection Wizard Dialog > --------------------------------------------------------------- > > Key: JBIDE-19523 > URL: https://issues.jboss.org/browse/JBIDE-19523 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: Version-Release number of selected component (if applicable): > jbt version: /nightly/mars/2015-03-26_16-23-29-B9619 > eclipse version: mars(4.5.0M5) > openshift-plug version: 3.0.0.Alpha2-v20150325-0237-B742 > Reporter: Ma Deshuai > Priority: Blocker > Labels: connection_wizard > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19523) Can't check server type in jboss tools Connection Wizard Dialog

by Ma Deshuai (JIRA)

Ma Deshuai created JBIDE-19523: ---------------------------------- Summary: Can't check server type in jboss tools Connection Wizard Dialog Key: JBIDE-19523 URL: https://issues.jboss.org/browse/JBIDE-19523 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Alpha2 Environment: Version-Release number of selected component (if applicable): jbt version: /nightly/mars/2015-03-26_16-23-29-B9619 eclipse version: mars(4.5.0M5) openshift-plug version: 3.0.0.Alpha2-v20150325-0237-B742 Reporter: Ma Deshuai Priority: Blocker -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19520) Unable to establish a connection in v2 or v3

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19520?page=com.atlassian.jira.plugi... ] Ma Deshuai edited comment on JBIDE-19520 at 3/27/15 1:37 AM: ------------------------------------------------------------- [~adietish] I can reproduce, The steps is: 1. Open connection Wizard dialog and The default server type is v2, In the dialog there are Username and password. 2. Select the server type to "OpenShift 3" 3. Select the server type back to "OpenShift 2" 4. The "Username" and "password" input dialog disappear 5. Input the v2 server and never connect to the v2. Additional info: If there is no step 2, Openshift V2 can connect successfully was (Author: deshuai): [~adietish] I can reproduce, The steps is: 1. Open connection Wizard dialog and The default server type is v2, In the dialog there are Username and password. 2. Select the server type to "OpenShift 3" 3. Select the server type back to "OpenShift 2" 4. The "Username" and "password" input dialog disappear 5. Input the v2 server and never connect to the v2. > Unable to establish a connection in v2 or v3 > -------------------------------------------- > > Key: JBIDE-19520 > URL: https://issues.jboss.org/browse/JBIDE-19520 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Priority: Blocker > Labels: connection_wizard > Fix For: 4.3.0.Alpha2 > > > After installing v2 and v3 plugin, unable to establish a connection in v2 or v3. > Noticed: > * Creds are visible initially for v2 but disappear and never reappear after flipping back and forth between v2 and v3 > * Trying a v2 connection after entering a URL never connects > * Canceling the v2 connection the URL text box is repopulated with the default URL, I suspect 'trying to connect' is not getting the URL that was entered -- This message was sent by Atlassian JIRA (v6.3.11#6341)

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