July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-490) Update system requirements for BrowserSim based on no Java6

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-490?page=com.atlassian.jira.plug... ] Misha Ali reassigned TOOLSDOC-490: ---------------------------------- Assignee: Misha Ali (was: Michelle Murray) > Update system requirements for BrowserSim based on no Java6 > ------------------------------------------------------------ > > Key: TOOLSDOC-490 > URL: https://issues.jboss.org/browse/TOOLSDOC-490 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: User Guide > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > Assignee: Misha Ali > Fix For: 4.2.0.Beta1 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > Writer Task: Edit topic 22864. Take text from Install Guide about BrowserSim requirements. Create new screen cap for 'BrowserSim/Cordova Pane of Preferences Window' figure with OpenJDK Java 7. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-489) Add info about jQM properties tab

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-489?page=com.atlassian.jira.plug... ] Misha Ali reassigned TOOLSDOC-489: ---------------------------------- Assignee: Misha Ali (was: Michelle Murray) > Add info about jQM properties tab > --------------------------------- > > Key: TOOLSDOC-489 > URL: https://issues.jboss.org/browse/TOOLSDOC-489 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > Assignee: Misha Ali > Fix For: 4.2.0.Beta1 > > Original Estimate: 3 hours, 15 minutes > Remaining Estimate: 3 hours, 15 minutes > > Use Case: widget wizard offers useful way for those new to jQM to edit output code snippets. But widget wizards are only for adding new items to files. So need feature to edit in widget wizard manner once in file. > Feature: Properties view has been enhanced for jQuery Mobile and HTML(5). Previously properties view was simply a table with attributes and values. Now has fields similar to those in widget wizards making it easier for those new to jQM to modify code snippets once in file. > Writer Task: Create new topic within Features section, 'Managing??' Add info about purpose of enhanced properties view and how to access and edit. Add a screen cap of a sample properties tab view. Also update 'About Features' topic with new bullet for action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-443) Simple guide to show app signing and deploying for iOS and Android

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-443?page=com.atlassian.jira.plug... ] Misha Ali reassigned TOOLSDOC-443: ---------------------------------- Assignee: Misha Ali (was: Michelle Murray) > Simple guide to show app signing and deploying for iOS and Android > ------------------------------------------------------------------ > > Key: TOOLSDOC-443 > URL: https://issues.jboss.org/browse/TOOLSDOC-443 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.1 > Reporter: Tadeas Kriz > Assignee: Misha Ali > Fix For: 4.2.0.Final > > > The documentation shows how to export "Mobile Application" in chapter 8.3.7. It says "ready-to-sign applications", but I'd be good to show, what can the user then do with the exported application, as readers of this guide might not be aware of how native packages work. > When export is made for iOS, the output is a single .app package. For Android, it's an .apk archive. It should be made clear to user what those packages are and possibly link to official documentation on given topic if it exists. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-478) Update About JBDS and User Cases of JBDS to incorporate any new features

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-478?page=com.atlassian.jira.plug... ] Misha Ali closed TOOLSDOC-478. ------------------------------ Resolution: Won't Fix > Update About JBDS and User Cases of JBDS to incorporate any new features > ------------------------------------------------------------------------ > > Key: TOOLSDOC-478 > URL: https://issues.jboss.org/browse/TOOLSDOC-478 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: General documentation issues > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.Final > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-491) JBDS user docs (user guide, install guide) should explain designations given to level of support for installable packages in Central

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-491?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-491: ------------------------------- Sprint: 20-Jul >> 02-Aug 2015-JBDS/JBT > JBDS user docs (user guide, install guide) should explain designations given to level of support for installable packages in Central > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: TOOLSDOC-491 > URL: https://issues.jboss.org/browse/TOOLSDOC-491 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 20-03-2014 22:52:59 > Topic ID: 22798-566605 [Specified] > Reporter: Len DiMaggio > Assignee: Misha Ali > Priority: Minor > Fix For: 4.2.0.Beta2 > > Attachments: Screenshot.png > > > Title: Install Software in JBoss Central > Describe the issue: > Packages that can be installed from Central are designated as: Supported, Tested, etc. These terms can be confusing to users. > Suggestions for improvement: > The user docs should explain, or at least refer to, the support levels as defined here: https://devstudio.jboss.com/updates/7.0/central/ > Additional information: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-491) JBDS user docs (user guide, install guide) should explain designations given to level of support for installable packages in Central

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-491?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-491: ------------------------------- Component/s: Installation Guide (was: User Guide) > JBDS user docs (user guide, install guide) should explain designations given to level of support for installable packages in Central > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: TOOLSDOC-491 > URL: https://issues.jboss.org/browse/TOOLSDOC-491 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 20-03-2014 22:52:59 > Topic ID: 22798-566605 [Specified] > Reporter: Len DiMaggio > Assignee: Misha Ali > Priority: Minor > Fix For: 4.2.0.Beta2 > > Attachments: Screenshot.png > > > Title: Install Software in JBoss Central > Describe the issue: > Packages that can be installed from Central are designated as: Supported, Tested, etc. These terms can be confusing to users. > Suggestions for improvement: > The user docs should explain, or at least refer to, the support levels as defined here: https://devstudio.jboss.com/updates/7.0/central/ > Additional information: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-491) JBDS user docs (user guide, install guide) should explain designations given to level of support for installable packages in Central

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-491?page=com.atlassian.jira.plug... ] Misha Ali reassigned TOOLSDOC-491: ---------------------------------- Assignee: Misha Ali (was: Michelle Murray) > JBDS user docs (user guide, install guide) should explain designations given to level of support for installable packages in Central > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: TOOLSDOC-491 > URL: https://issues.jboss.org/browse/TOOLSDOC-491 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: User Guide > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 20-03-2014 22:52:59 > Topic ID: 22798-566605 [Specified] > Reporter: Len DiMaggio > Assignee: Misha Ali > Priority: Minor > Fix For: 4.2.0.Beta2 > > Attachments: Screenshot.png > > > Title: Install Software in JBoss Central > Describe the issue: > Packages that can be installed from Central are designated as: Supported, Tested, etc. These terms can be confusing to users. > Suggestions for improvement: > The user docs should explain, or at least refer to, the support levels as defined here: https://devstudio.jboss.com/updates/7.0/central/ > Additional information: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18537) Gnome3 Classics - RHEL7 - UI is gray but working from time to time

by Jan Hellar (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18537?page=com.atlassian.jira.plugi... ] Jan Hellar commented on JBIDE-18537: ------------------------------------ Don't have this problem with JBDS. > Gnome3 Classics - RHEL7 - UI is gray but working from time to time > ------------------------------------------------------------------ > > Key: JBIDE-18537 > URL: https://issues.jboss.org/browse/JBIDE-18537 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.CR2 > Reporter: Karel Piwko > Fix For: 4.3.0.Beta2 > > Attachments: gray-jbds.png, gray-jbds.webm > > > Not sure what is the cause of this issue. Sometimes when interacting with message notifications JBDS UI stays grayed out - the same color as non-active application in clutter (aka. expose) view. > No other application is affected, so supposing this is a bug in Eclipse -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20217) JDT Debug can not connect/list VM started with suspend=y

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20217?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-20217: ---------------------------------------- Labels: new_and_noteworthy (was: ) > JDT Debug can not connect/list VM started with suspend=y > -------------------------------------------------------- > > Key: JBIDE-20217 > URL: https://issues.jboss.org/browse/JBIDE-20217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Aslak Knutsen > Assignee: Rob Stryker > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.3.0.CR1 > > > Having a VM started with suspend=y cause the following error to be logged from https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/... due to Exception thrown in ToolsCore.getJvmArgs > Seemingly JVMStat can not connect to a suspended VM. > {code} > eclipse.buildId=4.5.0.I20150603-2000 > java.version=1.8.0_45 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Command-line arguments: -os linux -ws gtk -arch x86_64 > org.jboss.tools.common.jdt.debug > Error > Wed Jul 08 17:16:00 CEST 2015 > {code} > {code} > java.lang.reflect.InvocationTargetException > 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:497) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getJvmArgs(Tools.java:780) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getJvmArgs(ToolsCore.java:98) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:166) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:145) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModels(RemoteDebugActivator.java:132) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:193) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:227) > at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator.discoverRemoteApplication(RemoteDebugUIActivator.java:137) > at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator$1.run(RemoteDebugUIActivator.java:93) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: sun.jvmstat.monitor.MonitorException: Could not synchronize with target > at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.synchWithTarget(PerfDataBuffer.java:277) > at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.buildMonitorMap(PerfDataBuffer.java:131) > at sun.jvmstat.perfdata.monitor.PerfDataBufferImpl.findByName(PerfDataBufferImpl.java:241) > at sun.jvmstat.perfdata.monitor.AbstractPerfDataBuffer.findByName(AbstractPerfDataBuffer.java:100) > at sun.jvmstat.perfdata.monitor.AbstractMonitoredVm.findByName(AbstractMonitoredVm.java:85) > at sun.jvmstat.monitor.MonitoredVmUtil.jvmArgs(MonitoredVmUtil.java:145) > ... 14 more > Root exception: > sun.jvmstat.monitor.MonitorException: Could not synchronize with target > at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.synchWithTarget(PerfDataBuffer.java:277) > at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.buildMonitorMap(PerfDataBuffer.java:131) > at sun.jvmstat.perfdata.monitor.PerfDataBufferImpl.findByName(PerfDataBufferImpl.java:241) > at sun.jvmstat.perfdata.monitor.AbstractPerfDataBuffer.findByName(AbstractPerfDataBuffer.java:100) > at sun.jvmstat.perfdata.monitor.AbstractMonitoredVm.findByName(AbstractMonitoredVm.java:85) > at sun.jvmstat.monitor.MonitoredVmUtil.jvmArgs(MonitoredVmUtil.java:145) > 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:497) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getJvmArgs(Tools.java:780) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getJvmArgs(ToolsCore.java:98) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:166) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:145) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModels(RemoteDebugActivator.java:132) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:193) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:227) > at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator.discoverRemoteApplication(RemoteDebugUIActivator.java:137) > at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator$1.run(RemoteDebugUIActivator.java:93) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-499) File repository not found

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-499?page=com.atlassian.jira.plug... ] Misha Ali closed TOOLSDOC-499. ------------------------------ Resolution: Won't Fix This is an issue that unfortunately the docs team will not have the resources to fix as it is for two major versions ago. > File repository not found > ------------------------- > > Key: TOOLSDOC-499 > URL: https://issues.jboss.org/browse/TOOLSDOC-499 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Getting Started Guide > Environment: Build Name: 22437, Getting Started Guide-7.1 > Build Date: 11-12-2013 15:10:35 > Topic ID: 13798-568341 [Latest] > Reporter: Lino Arnoldi > Assignee: Michelle Murray > Priority: Blocker > Labels: customer > > Title: Configure Maven > Maven is distributed with JBoss Developer Studio so it is not necessary to install Maven ???? > jboss-eap-6.x.y-maven-repository it's impossibile to find -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 July 2015