[JBoss JIRA] (JBIDE-17944) BrowserSim: Use http: protocol instead of file: for accessing local files
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17944?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-17944:
-------------------------------------
< But there is a point in having the option to "simulate" standalone apps
So, why not to do this support in CordovaSim. We have focussed on the fact that Ripple handles only Hybrid mobile projects (In fact it's not) - !ripple.png|thumbnail! (NOTE this picture is from my [cordovasim|https://github.com/ibuziuk/incubator-ripple/commits/cordovasim] branch for incubator-ripple migration. On master we have only *Apache Cordova / Phonegap* 3.0 platform supported)
So we can extend CordovaSim functionality by managing Mobile Web platform (I think this is something that will cover a case with stanalone apps <- need to investigate it properly)
Could you give me for instance of a standalone app for testing?
> BrowserSim: Use http: protocol instead of file: for accessing local files
> -------------------------------------------------------------------------
>
> Key: JBIDE-17944
> URL: https://issues.jboss.org/browse/JBIDE-17944
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Alpha1
>
> Attachments: ripple.png
>
>
> Currently, BrowserSim works through file: protocol but this protocol doesn't work well with paths relative to the webroot (which start with "/").
> So if a local file contains any links to local resources (css, js, ...) via relative paths then these resources are not available in BrowserSim.
> For example all official ionic example projects use such paths. It makes "open with BrowserSim" feature useless for those projects.
> It would be great if BrowserSim uses http: as our HTML5 preview does.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-17989) keyword used for plugin tracking is missing majority of times on GA
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17989?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-17989:
---------------------------------------
Branding is still an issue, because currently not all features are listed under JBoss Tools Icon in About dialog, fix is easy though and I'll attach PR in a bit.
> keyword used for plugin tracking is missing majority of times on GA
> -------------------------------------------------------------------
>
> Key: JBIDE-17989
> URL: https://issues.jboss.org/browse/JBIDE-17989
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: usage
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> looking at tracking numbers i'm seeing more and more requests where the keywords are not making it into the result.
> Meaning we can't see how many have installed the various plugins.
> What is weird *some* do and others do not have it.
> Need to track down the reason for that being missed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBTIS-293) Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-293?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-293:
----------------------------------
Looks like the same issue.
> Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
> -----------------------------------------------------------------------------------------------------
>
> Key: JBTIS-293
> URL: https://issues.jboss.org/browse/JBTIS-293
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Fuse IDE
> Affects Versions: 4.2.0.Alpha1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> If I run eclipse/jbdevstudio -clean (purging the OSGi cache) I don'y get this error.
> SESSION 2014-07-30 09:22:59.386 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_60-ea
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.fusesource.ide.branding 4 0 2014-07-30 09:23:05.987
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.branding [975]
> Unresolved requirement: Require-Bundle: org.fusesource.ide.camel.model
> -> Bundle-SymbolicName: org.fusesource.ide.camel.model; bundle-version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"
> org.fusesource.ide.camel.model [977]
> No resolution report for the bundle. Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] because it is exposed to package 'javax.xml.bind.annotation.adapters' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
> Chain 1:
> org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
> require: (osgi.wiring.bundle=org.eclipse.core.runtime)
> |
> provide: osgi.wiring.bundle: org.eclipse.core.runtime
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"]
> Chain 2:
> org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
> import: (osgi.wiring.package=org.fusesource.camel.tooling.util)
> |
> export: osgi.wiring.package=org.fusesource.camel.tooling.util; uses:=org.apache.camel.model
> io.fabric8.camel-tooling-util [osgi.identity; osgi.identity="io.fabric8.camel-tooling-util"; type="osgi.bundle"; version:Version="1.0.0.redhat-379"]
> import: (&(osgi.wiring.package=org.apache.camel.model)(&(version>=2.12.0)(!(version>=3.0.0))))
> |
> export: osgi.wiring.package=org.apache.camel.model; uses:=javax.xml.bind.annotation.adapters
> org.apache.camel.camel-core [osgi.identity; osgi.identity="org.apache.camel.camel-core"; type="osgi.bundle"; version:Version="2.12.0.redhat-610379"]
> import: (osgi.wiring.package=javax.xml.bind.annotation.adapters)
> |
> export: osgi.wiring.package: javax.xml.bind.annotation.adapters
> javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBTIS-293) Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-293:
--------------------------------
Summary: Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
Key: JBTIS-293
URL: https://issues.jboss.org/browse/JBTIS-293
Project: JBoss Tools Integration Stack
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Fuse IDE
Affects Versions: 4.2.0.Alpha1
Reporter: Paul Leacu
Assignee: Paul Leacu
If I run eclipse/jbdevstudio -clean (purging the OSGi cache) I don'y get this error.
SESSION 2014-07-30 09:22:59.386 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.7.0_60-ea
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
!ENTRY org.fusesource.ide.branding 4 0 2014-07-30 09:23:05.987
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.branding [975]
Unresolved requirement: Require-Bundle: org.fusesource.ide.camel.model
-> Bundle-SymbolicName: org.fusesource.ide.camel.model; bundle-version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"
org.fusesource.ide.camel.model [977]
No resolution report for the bundle. Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] because it is exposed to package 'javax.xml.bind.annotation.adapters' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
Chain 1:
org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
require: (osgi.wiring.bundle=org.eclipse.core.runtime)
|
provide: osgi.wiring.bundle: org.eclipse.core.runtime
org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"]
Chain 2:
org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
import: (osgi.wiring.package=org.fusesource.camel.tooling.util)
|
export: osgi.wiring.package=org.fusesource.camel.tooling.util; uses:=org.apache.camel.model
io.fabric8.camel-tooling-util [osgi.identity; osgi.identity="io.fabric8.camel-tooling-util"; type="osgi.bundle"; version:Version="1.0.0.redhat-379"]
import: (&(osgi.wiring.package=org.apache.camel.model)(&(version>=2.12.0)(!(version>=3.0.0))))
|
export: osgi.wiring.package=org.apache.camel.model; uses:=javax.xml.bind.annotation.adapters
org.apache.camel.camel-core [osgi.identity; osgi.identity="org.apache.camel.camel-core"; type="osgi.bundle"; version:Version="2.12.0.redhat-610379"]
import: (osgi.wiring.package=javax.xml.bind.annotation.adapters)
|
export: osgi.wiring.package: javax.xml.bind.annotation.adapters
javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
at org.eclipse.osgi.container.Module.start(Module.java:434)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-17944) BrowserSim: Use http: protocol instead of file: for accessing local files
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17944?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-17944:
--------------------------------
Attachment: ripple.png
> BrowserSim: Use http: protocol instead of file: for accessing local files
> -------------------------------------------------------------------------
>
> Key: JBIDE-17944
> URL: https://issues.jboss.org/browse/JBIDE-17944
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Alpha1
>
> Attachments: ripple.png
>
>
> Currently, BrowserSim works through file: protocol but this protocol doesn't work well with paths relative to the webroot (which start with "/").
> So if a local file contains any links to local resources (css, js, ...) via relative paths then these resources are not available in BrowserSim.
> For example all official ionic example projects use such paths. It makes "open with BrowserSim" feature useless for those projects.
> It would be great if BrowserSim uses http: as our HTML5 preview does.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-4791) Properties list in Properties view disappears when the user clicks a tab in CSS Properties view
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4791?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-4791:
------------------------------------------
Fix Version/s: 4.3.x
> Properties list in Properties view disappears when the user clicks a tab in CSS Properties view
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-4791
> URL: https://issues.jboss.org/browse/JBIDE-4791
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 3.1.0.M3
> Environment: Ubuntu 8.10, JBossTools revision 17062
> Reporter: Olga Chukhutsina
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 3.1.0.M4, 4.3.x
>
> Attachments: CSSPropertiesBug_1.png, CSSPropertiesBug_2.png
>
>
> Properties list disappears from Properties view when the user clicks tabs in CSS Properties view.
> Steps:
> Choose some selector in CSS file>Text/Font tab is opened in CSS Properties view by default and the properties list in Properties view is displayed>choose another tab in CSS Properties view(e.g Background )>now properties list in Properties view is not shown any more
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-16991) arquillian editor - quailfiier list is very slow to load and does not seem to be cached
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16991?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-16991:
-------------------------------------
Assignee: Max Rydahl Andersen (was: Snjezana Peco)
Could you please review?
The PR has been applied to master.
> arquillian editor - quailfiier list is very slow to load and does not seem to be cached
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-16991
> URL: https://issues.jboss.org/browse/JBIDE-16991
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.0.CR1
>
>
> clicking and opening qualifier list the first time freezes the UI (it shouldn't).
> Then an empty dialog shows up.
> A few seconds later the content starts "dripping in'
> Second time there is no freeze - but the content still takes a bit to load and no info about it loading.
> Can't this be cached ?
> Can't we show "Loading..." while it is running and secondly - how will this work when not connected to the network (I assume it is loading something remotely which is great, but we need to work while offline too)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months