June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14734) JQuery Mobile Palette Wizards appear on wrong display

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-14734: ------------------------------------- Summary: JQuery Mobile Palette Wizards appear on wrong display Key: JBIDE-14734 URL: https://issues.jboss.org/browse/JBIDE-14734 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml/html source editing Affects Versions: 4.1.0.Beta1 Environment: Mac Os, Windows 8 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 4.1.0.Beta2 Reproduced on follow configuration: Two displays, main display on the right, second display on the left. Test case: EXECUTE: 1. Open JBDS 2. Open following html file in Visual Page Editor {code} <!DOCTYPE html> {code} 3. Place JBDS on the left display 4. Try do drop elements from jQuery Mobile Palette to the editor FAIL: Dialog appears on the right display -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14727) SeamRuntimeDetectionTest test failure

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14727?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14727: --------------------------------------- It seems that https://github.com/jbosstools/jbosstools-javaee/pull/82 hasn't been applied correctly. > SeamRuntimeDetectionTest test failure > ------------------------------------- > > Key: JBIDE-14727 > URL: https://issues.jboss.org/browse/JBIDE-14727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.1.0.Beta1 > Environment: RHEL 5 x86_64 Oracle JDK 1.7 > Reporter: Victor Rubezhny > Fix For: 4.1.0.Beta2 > > > Issue is reproducible not only on RHEL 6 x86, Oracle JDK 1.6 configuration as well. > {code}org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest.testSeamFoundTwice (from org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests) > Failing for the past 15 builds (Since #381 ) > Took 1.3 sec. > add description > Error Message > expected:<1> but was:<2> > Stacktrace > java.lang.AssertionError: expected:<1> but was:<2> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest.testSeamFoundTwice(SeamRuntimeDetectionTest.java:368) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > {code} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14727) SeamRuntimeDetectionTest test failure

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14727?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-14727: ------------------------------------- Assignee: Alexey Kazakov > SeamRuntimeDetectionTest test failure > ------------------------------------- > > Key: JBIDE-14727 > URL: https://issues.jboss.org/browse/JBIDE-14727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.1.0.Beta1 > Environment: RHEL 5 x86_64 Oracle JDK 1.7 > Reporter: Victor Rubezhny > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta2 > > > Issue is reproducible not only on RHEL 6 x86, Oracle JDK 1.6 configuration as well. > {code}org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest.testSeamFoundTwice (from org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests) > Failing for the past 15 builds (Since #381 ) > Took 1.3 sec. > add description > Error Message > expected:<1> but was:<2> > Stacktrace > java.lang.AssertionError: expected:<1> but was:<2> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest.testSeamFoundTwice(SeamRuntimeDetectionTest.java:368) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > {code} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14625) CordovaSim: Firebug doesn't work with Cordova 2.3.0 - 2.7.0

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14625?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-14625: ------------------------------------- Summary: CordovaSim: Firebug doesn't work with Cordova 2.3.0 - 2.7.0 (was: CordovaSim: Firebug doesn't work with cordova (2.3.0 - 2.7.0)) > CordovaSim: Firebug doesn't work with Cordova 2.3.0 - 2.7.0 > ----------------------------------------------------------- > > Key: JBIDE-14625 > URL: https://issues.jboss.org/browse/JBIDE-14625 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.1.0.Beta2 > > Attachments: Firebug_error.png > > > Firebug runs via adding simple script to the page (https://getfirebug.com/firebug-lite.js#startInNewWindow) > The InAppBrowser is a web-browser that is shown in your app when you use the window.open call -> ("#startInNewWindow" for Firebug lite) > Note: InAppBrowser API has appeared only from 2.3.0 version http://docs.phonegap.com/en/2.7.0/cordova_inappbrowser_inappbrowser.md.ht... , and isn't implemented in Ripple/CordovaSim -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2389) cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2389?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2389: ----------------------------- Fix Version/s: 7.0.0.Beta2 (was: 7.0.0.Beta1) > cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives > ------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2389 > URL: https://issues.jboss.org/browse/JBDS-2389 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, updatesite > Affects Versions: 6.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Beta2 > > > Steps to repro: > Unpack bare Juno JEE. > Install JBDS BYOE feature ("Core Features"). Restart > Install JBDS Branded Product Feature. Restart. > Uninstall JBDS Branded Product Feature (or revert configuration to previous). Restart. Eclipse is now broken: > {code} > java.lang.RuntimeException: Application "" could not be found in the registry. > {code} > Addtional info: > {quote} > Bare Juno JEE eclipse.ini: > {code} > $➔ cat eclipse/eclipse.ini > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > -product > org.eclipse.epp.package.jee.product > --launcher.defaultAction > openFile > -showsplash > org.eclipse.platform > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Dosgi.requiredJavaVersion=1.5 > -Dhelp.lucene.tokenizer=standard > -XX:MaxPermSize=256m > -Xms40m > -Xmx512m > {code} > or, for Eclipse Platform Binary: > {code} > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > -showsplash > org.eclipse.platform > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Xms40m > -Xmx384m > {code} > After installing JBDS BYOE: > {code} > $➔ cat eclipse/eclipse.ini > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > -showsplash > org.eclipse.platform > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Xms512m > -Xmx1024m > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml > {code} > After installing JBDS branded product, eclipse.ini becomes jbdevstudio.ini: > {code} > $➔ cat eclipse/jbdevstudio.ini > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -product > com.jboss.jbds.product.product > -showsplash > platform:/base/plugins/com.jboss.jbds.product > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml > -Xms512m > -Xmx1024m > -Dosgi.instance.area.default=(a)user.home/workspace > {code} > After UNINSTALLING JBDS branded product (to drop back to Eclipse + JBDS BYOE), can no longer start Eclipse. Here is the resulting eclipse.ini file: > {code} > $➔ cat eclipse/eclipse.ini > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > -product > com.jboss.jbds.product.product > -showsplash > platform:/base/plugins/com.jboss.jbds.product > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml > -Xms512m > -Xmx1024m > {code} > {quote} > So, I think we need an instructions.unconfigure in com.jboss.jbds.p2.inf to remove these lines > {code} > -product > com.jboss.jbds.product.product > -showsplash > platform:/base/plugins/com.jboss.jbds.product > {code} > and replace them with the following when JBDS is uninstalled: > {code} > -application > org.eclipse.ui.ide.workbench > -showsplash > org.eclipse.platform > {code} > Also need to know what happens if there are two -product directives... can we just > add (and later remove, when uninstalling) our product to the list, or must we replace > any existing -product entries with ours? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13832) MD5 sometimes not correct

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13832?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13832: ------------------------------- Fix Version/s: (was: 4.1.0.Beta1) > MD5 sometimes not correct > ------------------------- > > Key: JBIDE-13832 > URL: https://issues.jboss.org/browse/JBIDE-13832 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.1.0.Beta2 > > > If you look for instance at this repo: http://download.jboss.org/jbosstools/builds/staging/jbosstools-hibernate_... , you'll notice that the .MD5 files contains string that don't match the actual files md5 checksum, which is accurate in the log files (checksum.txt). > This is most likely an issue in the publish script. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14733) JUnit tests for jQuery Mobile Palette wizards code generation + DnD code insertion

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-14733: -------------------------------------- Summary: JUnit tests for jQuery Mobile Palette wizards code generation + DnD code insertion Key: JBIDE-14733 URL: https://issues.jboss.org/browse/JBIDE-14733 Project: Tools (JBoss Tools) Issue Type: Task Components: jsp/jsf/xml/html source editing Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.1.0.Beta2 Now we have tests that check what text is generated by the wizards. It would be useful to have tests that check what text is inserted into the editor. It's not always the same text. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14694) Cheatsheet is not opened when importing project as existing one

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14694?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14694: --------------------------------------------- if you remove https://github.com/jbosstools/jbosstools-central/pull/112 a tons of other things are removed so I assume you just means *part* of this ? And why don't we just keep a list of projects in a shortlived cache and if time it was registered is low enough we assume cheatsheet.xml was part of the open/import ? or is that too uncertain too ? > Cheatsheet is not opened when importing project as existing one > --------------------------------------------------------------- > > Key: JBIDE-14694 > URL: https://issues.jboss.org/browse/JBIDE-14694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta2 > > Attachments: jboss-as-kitchensink.zip > > > When I try to import project via Existing projects into workspace no cheatsheet is opened. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14694) Cheatsheet is not opened when importing project as existing one

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14694?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-14694: ------------------------------------------- Assignee: Snjezana Peco (was: Max Rydahl Andersen) Okey so let us please get junit tests added for this so we avoid having commits break the actual functionallity. > Cheatsheet is not opened when importing project as existing one > --------------------------------------------------------------- > > Key: JBIDE-14694 > URL: https://issues.jboss.org/browse/JBIDE-14694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta2 > > Attachments: jboss-as-kitchensink.zip > > > When I try to import project via Existing projects into workspace no cheatsheet is opened. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14505) CordovaSim: BrowserSim's change skin controls should be used instead of Ripple's select device controls (Device API should know which device is selected)

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14505?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-14505: ------------------------------------- Fix Version/s: 4.1.x (was: 4.1.0.Beta2) > CordovaSim: BrowserSim's change skin controls should be used instead of Ripple's select device controls (Device API should know which device is selected) > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14505 > URL: https://issues.jboss.org/browse/JBIDE-14505 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.1.x > > > Ripple original select device controls ('Devices' Tab) was removed in CordovaSim. Need to add analogous > tab with BrowserSim skins. Selected skin will be displayed on this tab, and user will have a possibility of changing BS skins via controls. -- 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, 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 2013