July 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-325) Incorrect supported JDK matrix

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-325?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-325: ------------------------------------------ Apologies, I made changes to the book after posting the link (specifically moving the JDK procedures to an appendix). For future reference, [2] should have been http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos... > Incorrect supported JDK matrix > ------------------------------ > > Key: TOOLSDOC-325 > URL: https://issues.jboss.org/browse/TOOLSDOC-325 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Installation Guide > Affects Versions: 4.1.0 > Reporter: Pavol Srna > Assignee: Martin Malina > Fix For: 4.1.0 > > > Hi Michelle, > the Supported Combinations of Operating Systems and Java Developer Kits seems to be wrong. We don't support Fedora 16,17 - instead we support f18,f19. > We also dropped ubuntu 11.10 and added Ubuntu 13. > For all supported *linux* distros we support openJDK and OracleJDK 1.6 and 1.7. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15263) Create Datasource Dialog/Wizard usability

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15263?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-15263: ------------------------------------- Yes! :-) > Create Datasource Dialog/Wizard usability > ----------------------------------------- > > Key: JBIDE-15263 > URL: https://issues.jboss.org/browse/JBIDE-15263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: common/jst/core > Affects Versions: 4.1.0.Beta2 > Reporter: Burr Sutter > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha1 > > Attachments: 2013-07-19_1034.png > > > The current Create Datasource dialog has a few usability "gotchas": > 1) It is located under the "JBoss Tools Web" category - when it is more appropriate to be under the "JBoss Tools" category, closer to the Forge wizards - where you need it. > 2) It defaults to AS5, not AS7 - it should default to EAP6/AS7 > 3) It defaults to register in persistence.xml - it is unclear to me how cleanly this injects into the current persistence.xml provided by the Forge wizards, I tend to uncheck it to be safe - then manually tweak up the persistence.xml to reference the same resource. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15286) Increment service version of jbosstools-base/usage submodule

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15286?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-15286: --------------------------------------- it cannot be 1.2.2. There should be gap between current released version from 4.1.x stream and version in next dev stream, so we would be able to release update to 1.2.1 only. according to: {quote}When to change the service segment The service segment number must be incremented whenever there have been changes to a plug-in between releases that are not visible in its API. For example, a bug has been fixed in the code, the plug-in manifest has changed, documentation has changed, compiler settings have changed. In general, if that change happens in a service (a.k.a. maintenance) release, then 1 is added. If it happens for the next official release, 100 has to be added. As a result, the service segment number for official releases normally ends with a zero (0, 100, 200, etc.). If that is not true for whatever reason, then one must not add 100 but instead set the service segment number to the next number that is divisible by 100, so that the normal numbering scheme is restored. This practice makes it easy to manage one line of descent after a release and still guarantee that plug-ins coming in the next release will have a higher version number than ones from maintenance releases (thus enabling the usage of update manager from maintenance releases to the new releases).{quote} new version in dev N+1 stream should be 1.2.100. Then if we need deliver update for 4.1.0 as 4.1.1.Final usage would get updated version 1.2.2, which means this update could be installed only for 4.1.0.Final, but not for 4.2.0 stream where usage version is 1.2.100, because 1.2.1<1.2.2<1.2.100. > Increment service version of jbosstools-base/usage submodule > ------------------------------------------------------------ > > Key: JBIDE-15286 > URL: https://issues.jboss.org/browse/JBIDE-15286 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: usage > Affects Versions: 4.2.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.0.Alpha1 > > > Internal classes only were changed since creating 4.1.x branch. Service version should be changed from 1.2.1 to 1.2.100 according http://wiki.eclipse.org/Version_Numbering. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15286) Increment service version of jbosstools-base/usage submodule

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15286?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15286: ---------------------------------- Description: Internal classes only were changed since creating 4.1.x branch. Service version should be changed from 1.2.1 to 1.2.100 according http://wiki.eclipse.org/Version_Numbering. (was: Internal classes only were changed since creating 4.1.x branch. Service version should be changed from 1.2.1 to 1.2.200 according http://wiki.eclipse.org/Version_Numbering.) > Increment service version of jbosstools-base/usage submodule > ------------------------------------------------------------ > > Key: JBIDE-15286 > URL: https://issues.jboss.org/browse/JBIDE-15286 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: usage > Affects Versions: 4.2.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.0.Alpha1 > > > Internal classes only were changed since creating 4.1.x branch. Service version should be changed from 1.2.1 to 1.2.100 according http://wiki.eclipse.org/Version_Numbering. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-4523) Visual Page Editor doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed)

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4523?page=com.atlassian.jira.plugin... ] Yahor Radtsevich updated JBIDE-4523: ------------------------------------ Fix Version/s: 4.2.x (was: 4.1.x) > Visual Page Editor doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-4523 > URL: https://issues.jboss.org/browse/JBIDE-4523 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor core > Affects Versions: 3.1.0.M1 > Environment: Mac OSX 10.5.7, Eclipse 3.5 JEE Cocoa, JBoss Tools 3.1.0.M1 > Reporter: CÃ©sar PÃ©rez > Assignee: Yahor Radtsevich > Labels: cocoa, new_and_noteworthy, osx, vpe > Fix For: 4.2.x > > > The Visual Page Editor does not work under the final version of Eclipse 3.5 JEE Cocoa for Mac OSX and JBoss Tools 3.1.0.M1, the error is due to a missing cocoa version of XUL runner as you can see in the following stacktrace: > org.jboss.tools.vpe.xulrunner.XulRunnerException: Bundle org.mozilla.xulrunner.cocoa.macosx is not found. > at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.getXulRunnerPath(XulRunnerBrowser.java:219) > at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.initXulRunner(XulRunnerBrowser.java:114) > at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:85) > at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135) > at org.jboss.tools.vpe.editor.mozilla.MozillaPreview$1.<init>(MozillaPreview.java:59) > at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.createPartControl(MozillaPreview.java:59) > at org.jboss.tools.vpe.editor.VpeEditorPart.createPreviewBrowser(VpeEditorPart.java:921) > at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:248) > at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart$2.widgetSelected(JSPMultiPageEditorPart.java:106) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076) > at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3256) > at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2045) > at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:323) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3440) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3099) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) > at org.eclipse.equinox.launcher.Main.run(Main.java:1311) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-4523) Visual Page Editor doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed)

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4523?page=com.atlassian.jira.plugin... ] Yahor Radtsevich updated JBIDE-4523: ------------------------------------ Summary: Visual Page Editor doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed) (was: Visual Page Editor doesn't work with Eclipse 3.5 OSX Cocoa) > Visual Page Editor doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-4523 > URL: https://issues.jboss.org/browse/JBIDE-4523 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor core > Affects Versions: 3.1.0.M1 > Environment: Mac OSX 10.5.7, Eclipse 3.5 JEE Cocoa, JBoss Tools 3.1.0.M1 > Reporter: CÃ©sar PÃ©rez > Assignee: Yahor Radtsevich > Labels: cocoa, new_and_noteworthy, osx, vpe > Fix For: 4.1.x > > > The Visual Page Editor does not work under the final version of Eclipse 3.5 JEE Cocoa for Mac OSX and JBoss Tools 3.1.0.M1, the error is due to a missing cocoa version of XUL runner as you can see in the following stacktrace: > org.jboss.tools.vpe.xulrunner.XulRunnerException: Bundle org.mozilla.xulrunner.cocoa.macosx is not found. > at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.getXulRunnerPath(XulRunnerBrowser.java:219) > at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.initXulRunner(XulRunnerBrowser.java:114) > at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:85) > at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135) > at org.jboss.tools.vpe.editor.mozilla.MozillaPreview$1.<init>(MozillaPreview.java:59) > at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.createPartControl(MozillaPreview.java:59) > at org.jboss.tools.vpe.editor.VpeEditorPart.createPreviewBrowser(VpeEditorPart.java:921) > at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:248) > at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart$2.widgetSelected(JSPMultiPageEditorPart.java:106) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076) > at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3256) > at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2045) > at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:323) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3440) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3099) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) > at org.eclipse.equinox.launcher.Main.run(Main.java:1311) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13744) BrowserSim: Create ripple plugin to support barcode simulation

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13744?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-13744: ------------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > BrowserSim: Create ripple plugin to support barcode simulation > -------------------------------------------------------------- > > Key: JBIDE-13744 > URL: https://issues.jboss.org/browse/JBIDE-13744 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Max Rydahl Andersen > Assignee: Yahor Radtsevich > Fix For: 4.2.x > > > Support barcode scanner. > Allow to type in value in ripple and simulator will be able to pick it up via the barcode.js API (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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13743) BrowserSim: Can we support ChildBrowser plugin in cordovasim

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13743?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-13743: ------------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > BrowserSim: Can we support ChildBrowser plugin in cordovasim > ------------------------------------------------------------ > > Key: JBIDE-13743 > URL: https://issues.jboss.org/browse/JBIDE-13743 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Max Rydahl Andersen > Assignee: Yahor Radtsevich > Fix For: 4.2.x > > > Is it even technically possible with Ripple? > Any alternatives? -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14506) CordovaSim: need to implement Phonegap's Card Reader plugin

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14506?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-14506: ------------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > CordovaSim: need to implement Phonegap's Card Reader plugin > ----------------------------------------------------------- > > Key: JBIDE-14506 > URL: https://issues.jboss.org/browse/JBIDE-14506 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.x > > > Here is a description of card.io iOS plug-in for PhoneGap (plugin is IOS specific) https://github.com/phonegap/phonegap-plugins/tree/master/iOS/card.io -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6501) Add possibility to change string value in the message bundle directly from the VPE.

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6501?page=com.atlassian.jira.plugin... ] Yahor Radtsevich updated JBIDE-6501: ------------------------------------ Fix Version/s: 4.2.x (was: 4.1.x) > Add possibility to change string value in the message bundle directly from the VPE. > ----------------------------------------------------------------------------------- > > Key: JBIDE-6501 > URL: https://issues.jboss.org/browse/JBIDE-6501 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Affects Versions: 3.2.x > Reporter: Denis Maliarevich > Assignee: Yahor Radtsevich > Fix For: 4.2.x > > > Add possibility to change string value in the message bundle directly from the VPE. > For instance, if there is a key value on a page like #{Message.Name} the user should be able to change the value of the key 'Name' directly from the VPE without opening a 'message.properties' file. -- 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, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2013