July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16575) Tests for BrowserSim

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16575?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov edited comment on JBIDE-16575 at 7/31/14 5:22 PM: ------------------------------------------------------------------------- {quote}well why not fix those testsrun ? {quote} the easiest way to fix. If [~vpakan] can confirm that browsersim integration tests comes with vpe only because browsersim was a part of VPE. {quote}if we run in eclipse we aren't actually testing the right thing are we ? {quote} Literally not the right thing, but browsersim can be successfully started in Eclipse process without any problems(with SWT.WEBKIT). was (Author: kmarmaliykov): {quote}well why not fix those testsrun ? {quote} the easiest way to fix. If [~vpakan] can confirm that browsersim integration tests comes with vpe only because browsersim was a part of VPE. {quote}if we run in eclipse we aren't actually testing the right thing are we ? {quote} Literally not the same, but browsersim can be successfully started in Eclipse process without any problems(with SWT.WEBKIT). > Tests for BrowserSim > -------------------- > > Key: JBIDE-16575 > URL: https://issues.jboss.org/browse/JBIDE-16575 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim > Reporter: Alexey Kazakov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.CR1 > > > We should create JUnit tests which will run BrowserSim on both Java platforms: with JavaFX and w/o it. Those tests should check if webkit BS can be run on both platforms and if JavaFX BS can be run on the platform with JavaFX. > It's probably imposible to have such tests without special Jenkins settings. > So [~nickboldt]'s help is needed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16575) Tests for BrowserSim

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16575?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov edited comment on JBIDE-16575 at 7/31/14 5:23 PM: ------------------------------------------------------------------------- {quote}well why not fix those testsrun ? {quote} the easiest way to fix. If [~vpakan] can confirm that browsersim integration tests comes with vpe only because browsersim was a part of VPE. {quote}if we run in eclipse we aren't actually testing the right thing are we ? {quote} Literally not the right thing, but browsersim can be successfully started in Eclipse process without any problems(with SWT.WEBKIT) (I mean if there is some errors - it will be detected by test running this way). was (Author: kmarmaliykov): {quote}well why not fix those testsrun ? {quote} the easiest way to fix. If [~vpakan] can confirm that browsersim integration tests comes with vpe only because browsersim was a part of VPE. {quote}if we run in eclipse we aren't actually testing the right thing are we ? {quote} Literally not the right thing, but browsersim can be successfully started in Eclipse process without any problems(with SWT.WEBKIT). > Tests for BrowserSim > -------------------- > > Key: JBIDE-16575 > URL: https://issues.jboss.org/browse/JBIDE-16575 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim > Reporter: Alexey Kazakov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.CR1 > > > We should create JUnit tests which will run BrowserSim on both Java platforms: with JavaFX and w/o it. Those tests should check if webkit BS can be run on both platforms and if JavaFX BS can be run on the platform with JavaFX. > It's probably imposible to have such tests without special Jenkins settings. > So [~nickboldt]'s help is needed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18028) IMPORTANT/URGENT etc. from asciidoc gets no styling

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18028?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18028: --------------------------------------------- You write any of the adminitions on the url http://asciidoctor.org/docs/asciidoc-writers-guide/#admonitions i.e. IMPORTANT: this fails Put that in a blog and run rake clean preview and see the page will not have that section with any styling. I opened this issue to not forget and then see it triage. This is on the website and there is not a specific priority or hard schedule on this. It is to be looked and triaged by those maintaining/leading the website component. > IMPORTANT/URGENT etc. from asciidoc gets no styling > ---------------------------------------------------- > > Key: JBIDE-18028 > URL: https://issues.jboss.org/browse/JBIDE-18028 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Max Rydahl Andersen > > the adminitions documented here http://asciidoctor.org/docs/asciidoc-writers-guide/#admonitions renders without any styling on website/blog. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16575) Tests for BrowserSim

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16575?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-16575: ------------------------------------------------ {quote}well why not fix those testsrun ? {quote} the easiest way to fix. If [~vpakan] can confirm that browsersim integration tests comes with vpe only because browsersim was a part of VPE. {quote}if we run in eclipse we aren't actually testing the right thing are we ? {quote} Literally not the same, but browsersim can be successfully started in Eclipse process without any problems(with SWT.WEBKIT). > Tests for BrowserSim > -------------------- > > Key: JBIDE-16575 > URL: https://issues.jboss.org/browse/JBIDE-16575 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim > Reporter: Alexey Kazakov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.CR1 > > > We should create JUnit tests which will run BrowserSim on both Java platforms: with JavaFX and w/o it. Those tests should check if webkit BS can be run on both platforms and if JavaFX BS can be run on the platform with JavaFX. > It's probably imposible to have such tests without special Jenkins settings. > So [~nickboldt]'s help is needed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17498) Can't run default hybrid project on device

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17498?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-17498: ------------------------------------- [~gercan], I run it on device, not emulator. Does running on the device could be coupled with JBIDE-15279? > Can't run default hybrid project on device > ------------------------------------------ > > Key: JBIDE-17498 > URL: https://issues.jboss.org/browse/JBIDE-17498 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Environment: windows > Reporter: Ilya Buziuk > Assignee: Gorkem Ercan > Fix For: 4.2.0.CR1 > > Attachments: BUILD SUCCESSFUL.png, Launching.png > > > After choosing *Run As.. -> Run on Android Device* getting exception: > {code} > !ENTRY org.eclipse.ant.launching 4 0 2014-06-02 13:03:42.618 > !MESSAGE Ant Build Failed > !STACK 1 > org.eclipse.core.runtime.CoreException: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv > Cause: The name is undefined. > Action: Check the spelling. > Action: Check that any custom tasks/types have been declared. > Action: Check that any <presetdef>/<macrodef> declarations have taken place. > at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:448) > at org.eclipse.ant.core.AntRunner.run(AntRunner.java:380) > at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265) > at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884) > at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97) > at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58) > at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv > Cause: The name is undefined. > Action: Check the spelling. > Action: Check that any custom tasks/types have been declared. > Action: Check that any <presetdef>/<macrodef> declarations have taken place. > at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499) > at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431) > at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163) > at org.apache.tools.ant.Task.perform(Task.java:347) > at org.apache.tools.ant.Target.execute(Target.java:435) > at org.apache.tools.ant.Target.performTasks(Target.java:456) > at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) > at org.apache.tools.ant.Project.executeTarget(Project.java:1364) > at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) > at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36) > at org.apache.tools.ant.Project.executeTargets(Project.java:1248) > at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703) > at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371) > ... 12 more > !SUBENTRY 1 org.eclipse.ant.core 4 1 2014-06-02 13:03:42.618 > !MESSAGE E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv > Cause: The name is undefined. > Action: Check the spelling. > Action: Check that any custom tasks/types have been declared. > Action: Check that any <presetdef>/<macrodef> declarations have taken place. > !STACK 0 > E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv > Cause: The name is undefined. > Action: Check the spelling. > Action: Check that any custom tasks/types have been declared. > Action: Check that any <presetdef>/<macrodef> declarations have taken place. > at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499) > at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431) > at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163) > at org.apache.tools.ant.Task.perform(Task.java:347) > at org.apache.tools.ant.Target.execute(Target.java:435) > at org.apache.tools.ant.Target.performTasks(Target.java:456) > at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) > at org.apache.tools.ant.Project.executeTarget(Project.java:1364) > at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) > at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36) > at org.apache.tools.ant.Project.executeTargets(Project.java:1248) > at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703) > at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371) > at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265) > at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884) > at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97) > at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58) > at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > !ENTRY org.jboss.tools.aerogear.hybrid.android.core 4 0 2014-06-02 13:03:42.620 > !MESSAGE Build failed... Build artifact does not exist > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18028) IMPORTANT/URGENT etc. from asciidoc gets no styling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18028?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18028: ------------------------------------ Max, as project lead, could you go ahead and provide steps to reproduce or an example URL of where it fails? Great, thanks. Also, affects/fix versions would be useful since we need to know priority & schedule. > IMPORTANT/URGENT etc. from asciidoc gets no styling > ---------------------------------------------------- > > Key: JBIDE-18028 > URL: https://issues.jboss.org/browse/JBIDE-18028 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Max Rydahl Andersen > > the adminitions documented here http://asciidoctor.org/docs/asciidoc-writers-guide/#admonitions renders without any styling on website/blog. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15798) Missing scroolbar in Cordova Feature Dialog

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15798?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-15798: -------------------------------------- Has this been reported to upstream? Is there a bug number > Missing scroolbar in Cordova Feature Dialog > ------------------------------------------- > > Key: JBIDE-15798 > URL: https://issues.jboss.org/browse/JBIDE-15798 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.1.1.Beta1 > Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 > Reporter: Vlado Pakan > Assignee: Daniel Azarov > Priority: Minor > Fix For: 4.2.0.CR1 > > > 1. Create new Hybrid Mobile project > 2. Open project config.xml file in Cordova Configuration Editor > 3. Go to Platform Properties tab. and click on Add.... button to add features > 4. Type some text to Find text field to specify search condition which cannot be fulfilled to get empty list of plugins > 5. Clear Find: text field > ERROR: Opened dialog has no scroll bar -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17508) Cordova config.xml editor stays open with unidentified error after HMT project is deleted

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17508?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-17508: --------------------------------------- I am running Ubuntu Linux. > Cordova config.xml editor stays open with unidentified error after HMT project is deleted > ----------------------------------------------------------------------------------------- > > Key: JBIDE-17508 > URL: https://issues.jboss.org/browse/JBIDE-17508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Fix For: 4.2.x > > Attachments: cordova-config.png > > > Now after HMT project is created, config.xml is opened by default for it. Wen project is deleted, config.xml editor stays opened in broken state. > !cordova-config.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17508) Cordova config.xml editor stays open with unidentified error after HMT project is deleted

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17508?page=com.atlassian.jira.plugi... ] Gorkem Ercan edited comment on JBIDE-17508 at 7/31/14 3:46 PM: --------------------------------------------------------------- [~dgolovin] I can not repro on Mac. What are you running? was (Author: gercan): I can not repro on Mac. What are you running? > Cordova config.xml editor stays open with unidentified error after HMT project is deleted > ----------------------------------------------------------------------------------------- > > Key: JBIDE-17508 > URL: https://issues.jboss.org/browse/JBIDE-17508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Fix For: 4.2.x > > Attachments: cordova-config.png > > > Now after HMT project is created, config.xml is opened by default for it. Wen project is deleted, config.xml editor stays opened in broken state. > !cordova-config.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17214) Wrong tooltip on info column of Engines table in Hybrid Mobile preferences

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17214?page=com.atlassian.jira.plugi... ] Gorkem Ercan edited comment on JBIDE-17214 at 7/31/14 3:41 PM: --------------------------------------------------------------- This is fixed as part of the fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=439650 . The fix will land to JBT 4.2.0 CR1. If you want early access you can use the Thym project snapshot update site. was (Author: gercan): This is fixed as part of the fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=439650 > Wrong tooltip on info column of Engines table in Hybrid Mobile preferences > -------------------------------------------------------------------------- > > Key: JBIDE-17214 > URL: https://issues.jboss.org/browse/JBIDE-17214 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Reporter: Vlado Pakan > Fix For: 4.2.0.CR1 > > > See Case 5: within linked issue JBIDE-16883 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 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 July 2014