February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-17442) BrowserSim crash on Fedora 20 when browsing jQuery Mobile app

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17442?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-17442: ------------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > BrowserSim crash on Fedora 20 when browsing jQuery Mobile app > ------------------------------------------------------------- > > Key: JBIDE-17442 > URL: https://issues.jboss.org/browse/JBIDE-17442 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Beta1 > Environment: Fedora 20 > JBoss Developer Studio 8.0.0.Beta1 > webkitgtk-2.2.7-1.fc20.x86_64 > Reporter: Vineet Reynolds > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha2 > > > BrowserSim crashes when launching the TicketMonster app (from WFK 2.6). The offending line of code seems to be : > {noformat} > $("#container").enhanceWithin(); > {noformat} > in the mobile {{router.js}}. The [enhanceWithin API|http://api.jquerymobile.com/enhanceWithin/] is new in jQueryMobile 1.4.x. The same line works without any flaw in BrowserSim on Windows and Mac OS X. It also works without problems in Chrome 34 and Firefox 28 on Fedora 20. > The crash occurred on both GTK2 and GTK3 engines. > Additional notes - strace output reveals that BrowserSim is terminated due to a SIGTRAP event, which is a bit weird. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-18177: ------------------------------------------------ {quote}2. IMO better to have Html 5 Option next to JSF one, it saves some space{quote} Don't see where it is? {quote}Lets calm down and remove exclamation point from "Do not show this dialog again!"{quote} Why shouldn't we have it? You don't need it - just set up checkbox and use preferences. > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-18177 > URL: https://issues.jboss.org/browse/JBIDE-18177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014, new_and_noteworthy, requirements > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19162) add new plugins to openshift pom and create feature

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19162?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19162: ------------------------------------- Fix Version/s: 4.3.0.Alpha1 > add new plugins to openshift pom and create feature > --------------------------------------------------- > > Key: JBIDE-19162 > URL: https://issues.jboss.org/browse/JBIDE-19162 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha1 > > > In JBIDE-19048 we created new plugins for the OpenShift v3 tooling and moved reusable parts to common plugins. We now need to get the maven build working (add the new modules) and create a v3 feature. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19162) add new plugins to openshift pom and create feature

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19162: ---------------------------------------- Summary: add new plugins to openshift pom and create feature Key: JBIDE-19162 URL: https://issues.jboss.org/browse/JBIDE-19162 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.Alpha1 Reporter: Andre Dietisheim In JBIDE-19048 we created new plugins for the OpenShift v3 tooling and moved reusable parts to common plugins. We now need to get the maven build working (add the new modules) and create a v3 feature. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19162) add new plugins to openshift pom and create feature

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19162?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19162: ---------------------------------------- Assignee: Andre Dietisheim > add new plugins to openshift pom and create feature > --------------------------------------------------- > > Key: JBIDE-19162 > URL: https://issues.jboss.org/browse/JBIDE-19162 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > In JBIDE-19048 we created new plugins for the OpenShift v3 tooling and moved reusable parts to common plugins. We now need to get the maven build working (add the new modules) and create a v3 feature. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ] Marek Novotny commented on JBDS-3199: ------------------------------------- [~mjobanek] found out other issue in rf kitchensink datastore - WFK2-874, so I fixed it and staged new repository https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... > Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3199 > URL: https://issues.jboss.org/browse/JBDS-3199 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, upstream > Affects Versions: 8.0.0.GA > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 8.1.0.GA > > > These "kitchensink" strings are retained: > grep -ir kitchen * > main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source> > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS" > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true" > test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS" > test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19161) Filter applications by the current user

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19161?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-19161: ------------------------------- Fix Version/s: 4.2.3.Beta1 > Filter applications by the current user > --------------------------------------- > > Key: JBIDE-19161 > URL: https://issues.jboss.org/browse/JBIDE-19161 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Pavol Srna > Fix For: 4.2.3.Beta1 > > > In the current state the FeedHenry import dialog list all cordova applications available in the current space. With growing number of users and projects, the list can grow very quickly and become not manageable. > A good feature would be if the import dialog would offer the possibility to filter the applications by current user. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19161) Filter applications by the current user

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-19161: ---------------------------------- Summary: Filter applications by the current user Key: JBIDE-19161 URL: https://issues.jboss.org/browse/JBIDE-19161 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aerogear-hybrid Reporter: Pavol Srna In the current state the FeedHenry import dialog list all cordova applications available in the current space. With growing number of users and projects, the list can grow very quickly and become not manageable. A good feature would be if the import dialog would offer the possibility to filter the applications by current user. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19160) Import wizard cannot be filtered by 'FeedHenry' category name

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19160?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-19160: ------------------------------- Fix Version/s: 4.2.3.Beta1 > Import wizard cannot be filtered by 'FeedHenry' category name > ------------------------------------------------------------- > > Key: JBIDE-19160 > URL: https://issues.jboss.org/browse/JBIDE-19160 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: Pavol Srna > Fix For: 4.2.3.Beta1 > > Attachments: Screenshot 2015-02-04 09.49.28.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19153) Unable to use hibernate console when DTD is not accessible (hibernate.org down)

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19153?page=com.atlassian.jira.plugi... ] Jiri Peterka updated JBIDE-19153: --------------------------------- Fix Version/s: 4.2.3.Beta1 Priority: Blocker (was: Major) Changed to blocker as hibernate.org is not yet accessible and this issue is blocking Hibernate Configuration usage right now. > Unable to use hibernate console when DTD is not accessible (hibernate.org down) > ------------------------------------------------------------------------------- > > Key: JBIDE-19153 > URL: https://issues.jboss.org/browse/JBIDE-19153 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Final > Reporter: Jiri Peterka > Priority: Blocker > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > > Inaccessible DTD causes blocking Hibernate Console usage (as DTD cannot be loaded) > If DTD is not accessible It would be more useful to disable DTD validation rather than block further usage and just show some warning. > {code} > org.hibernate.HibernateException: Could not parse configuration: C:\Users\jpeterka\workspace\tmp\hb\mvn-hibernate35\src\main\java\hibernate.cfg.xml > at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1586) > at org.hibernate.cfg.Configuration.configure(Configuration.java:1554) > at org.jboss.tools.hibernate.proxy.ConfigurationProxy.configure(ConfigurationProxy.java:94) > at org.hibernate.console.ConfigurationFactory.loadConfigurationXML(ConfigurationFactory.java:350) > at org.hibernate.console.ConfigurationFactory.configureStandardConfiguration(ConfigurationFactory.java:278) > at org.hibernate.console.ConfigurationFactory.buildConfiguration(ConfigurationFactory.java:175) > at org.hibernate.console.ConfigurationFactory.createConfiguration(ConfigurationFactory.java:97) > at org.hibernate.eclipse.console.common.HibernateExtension$5.execute(HibernateExtension.java:166) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.eclipse.console.common.HibernateExtension.execute(HibernateExtension.java:189) > at org.hibernate.eclipse.console.common.HibernateExtension.buildWith(HibernateExtension.java:163) > at org.hibernate.eclipse.console.common.HibernateExtension.build(HibernateExtension.java:134) > at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:189) > at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:43) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:98) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:233) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.dom4j.DocumentException: Server returned HTTP response code: 503 for URL: http://hibernate.org/dtd/hibernate-configuration-3.0.dtd Nested exception: Server returned HTTP response code: 503 for URL: http://hibernate.org/dtd/hibernate-configuration-3.0.dtd > at org.dom4j.io.SAXReader.read(SAXReader.java:484) > at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1576) > ... 17 more > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015