May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14348) BrowserSim address string disappearing

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14348?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-14348: ------------------------------------------ This video illustrates the blinking when we show it on scrolling up: [^scrolling-down.avi]. What I do on the video is just scroll the page down by mouse wheel. The reason of this is that scroll event is fired when browser window is resized. And the value of {{window.pageYOffset}} may become {{0}} after the scrollbar is hidden. This makes our code think that the user scrolled the page up. > BrowserSim address string disappearing > -------------------------------------- > > Key: JBIDE-14348 > URL: https://issues.jboss.org/browse/JBIDE-14348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.0.Alpha2 > Reporter: Daniel Azarov > Assignee: Yahor Radtsevich > Fix For: 4.1.0.Beta1 > > Attachments: scrolling-down.avi > > > Test case: > EXECUTE: > 1. Create project > 2. Create html file: > {code} > <html> > <head> > </head> > <body> > <a id="page1">1 Jump to this place</a> > > aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg > > <a id="page2">2 Jump to this place</a> > > aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg > > <a id="page3">3 Jump to this place</a> > > aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg > > <a id="page4">4 Jump to this place</a> > > aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg > > <a id="page5">5 Jump to this place</a> > > aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg > > <a id="page6">6 Jump to this place</a> > > aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg > > </body> > </html> > {code} > 3. Open file with BrowserSim > 4. Try to add #page3 to the address string > FAIL: > Address string disapeared -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14369) BrowserSim: Functionality is broken on landscape mode

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-14369: ---------------------------------------------- Summary: BrowserSim: Functionality is broken on landscape mode Key: JBIDE-14369 URL: https://issues.jboss.org/browse/JBIDE-14369 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.1.0.Beta1 Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov Priority: Minor Fix For: 4.1.0.Beta2 Open IPhone skin in portrait orientation 1. Go to medl.io 2. Click into footer at the bottom of the page. ASSERT: Contact block appears 3. Change orientation to landscape, repeat step 2 ASSERT: Contact block doesn't appears. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Carsten Pfeiffer (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Carsten Pfeiffer commented on JBIDE-2720: ----------------------------------------- OK, I cloned the http://hg.mozilla-x86-64.com/mozilla1.9.2-win64-mq/ to https://bitbucket.org/cpfeiffer/xulrunner-1.9.2-x86_64-win64-mq and added our patches to the latter. You need to follow the instructions from http://wiki.mozilla-x86-64.com/Firefox:SourceCode in order to build it (follow the section "Firefox 3.6"). > Need 64-bit windows support > --------------------------- > > Key: JBIDE-2720 > URL: https://issues.jboss.org/browse/JBIDE-2720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha > Reporter: Samuel Mendenhall > Assignee: Yahor Radtsevich > Fix For: 4.0.x > > Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, mozconfig1, mozconfig2 > > > If you use a 64 bit jdk, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for windows 64 bit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14362) CordovaSim: need to implement Phonegap's Barcode Scanner plugin

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14362?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-14362: -------------------------------- Description: Here is a description of Barcode Scanner plugin - https://github.com/phonegap/phonegap-plugins/tree/master/iOS/BarcodeScanner, https://github.com/phonegap/phonegap-plugins/tree/master/Android/BarcodeS... (was: Here is a description of Barcode Scanner plugin - https://github.com/phonegap/phonegap-plugins/tree/master/iOS/BarcodeScanner) > CordovaSim: need to implement Phonegap's Barcode Scanner plugin > ---------------------------------------------------------------- > > Key: JBIDE-14362 > URL: https://issues.jboss.org/browse/JBIDE-14362 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.1.0.Beta1 > > > Here is a description of Barcode Scanner plugin - https://github.com/phonegap/phonegap-plugins/tree/master/iOS/BarcodeScanner, https://github.com/phonegap/phonegap-plugins/tree/master/Android/BarcodeS... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14348) BrowserSim address string disappearing

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14348?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-14348: ------------------------------------- Attachment: scrolling-down.avi > BrowserSim address string disappearing > -------------------------------------- > > Key: JBIDE-14348 > URL: https://issues.jboss.org/browse/JBIDE-14348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.0.Alpha2 > Reporter: Daniel Azarov > Assignee: Yahor Radtsevich > Fix For: 4.1.0.Beta1 > > Attachments: scrolling-down.avi > > > Test case: > EXECUTE: > 1. Create project > 2. Create html file: > {code} > <html> > <head> > </head> > <body> > <a id="page1">1 Jump to this place</a> > > aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg > > <a id="page2">2 Jump to this place</a> > > aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg > > <a id="page3">3 Jump to this place</a> > > aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg > > <a id="page4">4 Jump to this place</a> > > aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg > > <a id="page5">5 Jump to this place</a> > > aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg > > <a id="page6">6 Jump to this place</a> > > aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg > > </body> > </html> > {code} > 3. Open file with BrowserSim > 4. Try to add #page3 to the address string > FAIL: > Address string disapeared -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14368) forge view is stuck (no input accepted, stop is not responding) if I edit the runtime

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14368?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-14368: ------------------------------ Fix Version/s: 4.1.0.Beta1 > forge view is stuck (no input accepted, stop is not responding) if I edit the runtime > ------------------------------------------------------------------------------------- > > Key: JBIDE-14368 > URL: https://issues.jboss.org/browse/JBIDE-14368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Koen Aers > Fix For: 4.1.0.Beta1 > > Attachments: forge-is-not-running.png, forge-is-running.png, local-runtime.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13799) Source Lookup enhancements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13799?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13799: --------------------------------------------- I think we chatted about https://github.com/ifedorenko/com.ifedorenko.m2e.sourcelookup at some point but could you put here how we compare/what features it has that we dont and if it could be merged or if they coexist fine in peace ? > Source Lookup enhancements > -------------------------- > > Key: JBIDE-13799 > URL: https://issues.jboss.org/browse/JBIDE-13799 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta1 > > > The PR includes the following enhancements: > - AS 7.2/EAP 6.1 are now recognized correctly > - the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2 > - the fix for the ConcurrentModificationException exception > - included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container > - JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search) > - JBoss Java Project Source Container > See http://screencast.com/t/39LHqYx5m > Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2. > Note: > You have to have some deployment on the servers in order the WeldBootstrap class to be created. > You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason. > The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14298) deprecate downloadRuntimes ext. pt., add new extension pt

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14298?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-14298: ----------------------------------- Assignee: Fred Bricon Assigning to you for PR approval. Feel free to ping me on questions > deprecate downloadRuntimes ext. pt., add new extension pt > --------------------------------------------------------- > > Key: JBIDE-14298 > URL: https://issues.jboss.org/browse/JBIDE-14298 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > > The downloadRuntimes extension point allows plugins to simply contribute via xml what runtimes are to be exposed via the runtimes preference pages. This is not suitable enough, as it means all runtimes must either be declared in xml, or, available in a web file currently stored at http://download.jboss.org/jbosstools/examples/download_runtimes.xml. > These two should be unified to support an extension point plus API that allows for downloadRuntimeProviders, which may return any set of download runtimes. > Callers of this may generate their list however they want, but, the suggested method would be by depending on jboss stacks and returning a list of runtimes from within the stacks yaml file that fit the component. > So for example, ASTools should get a list of available runtimes from stacks with the "SERVER" type, whereas seam would similarly return those with an appropriate seam tag or label. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14368) forge view is stuck (no input accepted, stop is not responding) if I edit the runtime

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14368?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14368: ------------------------------------- Workaround Description: close the forge view and reopen it. then start the runtime via button on the top right Workaround: Workaround Exists > forge view is stuck (no input accepted, stop is not responding) if I edit the runtime > ------------------------------------------------------------------------------------- > > Key: JBIDE-14368 > URL: https://issues.jboss.org/browse/JBIDE-14368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Koen Aers > Attachments: forge-is-not-running.png, forge-is-running.png, local-runtime.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14368) forge view is stuck (no input accepted, stop is not responding) if I edit the runtime

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14368?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14368: ------------------------------------- Steps to Reproduce: 1) ASSERT: make sure you have a local forge runtime installed on your harddrive and added in the forge preferences 2) ASSERT: make sure forge tooling is running on local runtime !local-runtime.png! 3) ASSERT: make sure you have the Forge view opened and forge running !forge-is-running.png! 4) EXEC: in the forge preferences hit *Edit* but dont change anything. Simply hit "OK" and close your preferences Result: Once you get back from preferences the forge view is not responding. You cannot enter any input and the *Stop* button is not responding either. 5) EXEC: close the forge view and reopen it: Result: The forge view is telling you that the forge runtime is not running: !forge-is-not-running.png! It pretty much looks like as if editing the runtime kills the runtime without the view noticing it. was: 1) ASSERT: make sure you have a local forge runtime installed on your harddrive and added in the forge preferences 2) ASSERT: make sure forge tooling is running on local runtime !local-runtime.png! 3) ASSERT: make sure you have the Forge view opened and forge running !forge-is-running.png! 4) EXEC: in the forge preferences hit *Edit* but dont change anything. Simply hit "OK" and close your preferences Result: Once you get back from preferences the forge view is not responding. You cannot enter any input and the *Stop* button is not responding either. 5) EXEC: close the forge view and reopen it: Result: The forge view is telling you that the forge runtime is not running: !forge-is-not-running.png! It pretty much looks like as if editing the runtime kills the runtime without the view noticing it. > forge view is stuck (no input accepted, stop is not responding) if I edit the runtime > ------------------------------------------------------------------------------------- > > Key: JBIDE-14368 > URL: https://issues.jboss.org/browse/JBIDE-14368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Koen Aers > Attachments: forge-is-not-running.png, forge-is-running.png, local-runtime.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 May 2013