March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-560) We should add an illustration of the RESTFUL output

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-560?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-560: ------------------------------------------ Thanks [~mlabuda]!! > We should add an illustration of the RESTFUL output > --------------------------------------------------- > > Key: TOOLSDOC-560 > URL: https://issues.jboss.org/browse/TOOLSDOC-560 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Affects Versions: 4.2.0.Final > Environment: Build Name: 22960, Start Developing-8.0 > Build Date: 22-10-2014 11:29:36 > Topic ID: 13785-717269 [Latest] > Reporter: Len DiMaggio > Assignee: Misha Ali > Priority: Minor > Fix For: 4.2.3.Beta1 > > > Title: Add a RESTful Web Service > Describe the issue: > The final step in this section reads: > Open a new Web Browser and in the address bar of the Web Browser enter http://localhost:8080/ticket-monster/rest/events. This shows the output of the new RESTful endpoint. > Suggestions for improvement: > We should add test explaining to the reader that the output should look like this: > [{"id":2,"version":1,"name":"Rock concert of the decade","description":"Get ready to rock...","major":true,"picture":null},{"id":1,"version":1,"name":"Shane's Sock Puppets","description":"This critically acclaimed masterpiece...","major":true,"picture":null}] > Additional information: -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-594) Offline Install does not mention the Target Platform zip

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-594?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-594: ------------------------------------------ [~nickboldt] - perfect, thanks! > Offline Install does not mention the Target Platform zip > -------------------------------------------------------- > > Key: TOOLSDOC-594 > URL: https://issues.jboss.org/browse/TOOLSDOC-594 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Affects Versions: 4.2.2.Final > Environment: Build Name: 22661, Install Red Hat JBoss Developer Studio-8.0 > Build Date: 25-11-2014 14:18:18 > Topic ID: 41914-716354 [Latest] > Reporter: Nick Boldt > Assignee: Michelle Murray > Priority: Blocker > Fix For: 4.2.3.Final > > > Title: Install JBoss Developer Studio BYOE when Offline > Describe the issue: > See JBDS-3361. User cannot install from JBDS zip alone because some eclipse dependencies are unavailable in that zip. > > Suggestions for improvement: > TP zip should be linked from CSP, jboss.org, and devstudio.redhat.com. > Doc (in CSP and on access.redhat.com) should tell users about the target platform zip, too. > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > Additional information: -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19394) NullPointerException in TempMarkerManager

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-19394: --------------------------------------------- Summary: NullPointerException in TempMarkerManager Key: JBIDE-19394 URL: https://issues.jboss.org/browse/JBIDE-19394 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.3.0.Alpha2 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.3.0.Alpha2 {code} java.lang.NullPointerException at org.jboss.tools.common.validation.TempMarkerManager$1.runInUIThread(TempMarkerManager.java:358) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:97) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3793) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3431) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) {code} Exception happens in {code} getId().equals(annotation.getAttributes().get(VALIDATOR_ID_ATTRIBUTE)) {code} because annotation.getAttributes() may return null. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19342) Update code to cope with generics added to org.eclipse.core.runtime package API

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19342?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-19342: --------------------------------- Fix Version/s: 4.3.x > Update code to cope with generics added to org.eclipse.core.runtime package API > -------------------------------------------------------------------------------- > > Key: JBIDE-19342 > URL: https://issues.jboss.org/browse/JBIDE-19342 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid, archives, batch, bean-validation, birt, browsersim, build, cdi, cdi-extensions, central, common/jst/core, cordovasim, discovery, forge, freemarker, hibernate, integration-platform, jmx, jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Reporter: Fred Bricon > Fix For: 4.3.x > > > We need to detect and address any part of our code affected by generics added to the org.eclipse.core.runtime package API. > From https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11590.html : > {quote} > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021 > Markus Keller wrote up an nice summary of what consumers should do to fix any warnings that may be caused by this change at https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25 > Here is a copy of the recommendations if you are going to compile against the latest version of org.eclipse.equinox.common: > 1. In MANIFEST.MF, update your Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.11.0,4.0.0)", or org.eclipse.equinox.common;bundle-version="[3.7.0,4.0.0)", or update your Import-Package: org.eclipse.core.runtime; version="[3.5,4.0)" > 2. If your bundle re-exports one of these bundles, then you also have to make sure the minor version is incremented. > 3. Remove unnecessary casts (Clean Up, or Problems view > Quick Fix > Select All) > 4. Update implementations of IAdaptable#getAdapter(Class<T>), unless you override another implementation of that method that still uses the old signature. > Typical change: > Old: > {code} > public Object getAdapter(Class adapter) { > if (ICompilationUnit.class.equals(adapter)) > return getCompilationUnit(); > return null; > } > {code} > New: > {code} > public <T> T getAdapter(Class<T> adapter) { > if (ICompilationUnit.class.equals(adapter)) > return adapter.cast(getCompilationUnit()); > return null; > } > {code} > 5. Update implementations of IAdapterFactory > Hint for 4. & 5.: > - Open Type Hierarchy on IAdaptable, etc. > - In the view menu, select a working set that contains your projects > - In the methods list of the Type Hierarchy view, select the methods, and then click the first toolbar button (Lock View and Show Members in Hierarchy) > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.... ] Gorkem Ercan updated JBDS-3244: ------------------------------- Component/s: jsp/jsf/xml/html source editing > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html source editing > Reporter: Max Rydahl Andersen > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19393) Multiple Error Annotations are shown on a valid JavaScript file in JavaScript Editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19393?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19393: -------------------------------------- Assignee: Victor Rubezhny > Multiple Error Annotations are shown on a valid JavaScript file in JavaScript Editor > ------------------------------------------------------------------------------------ > > Key: JBIDE-19393 > URL: https://issues.jboss.org/browse/JBIDE-19393 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.2.Final > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.3.0.Beta1 > > Attachments: hybrid4001.zip, JavaScriptParserError.png > > > Multiple Error Annotations are shown on a valid JavaScript file in JavaScript Editor: > {code} > Multiple markers at this line > - Syntax error on token "Invalid Character", delete this token > - Missing semicolon > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19393) Multiple Error Annotations are shown on a valid JavaScript file in JavaScript Editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19393?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19393: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > Multiple Error Annotations are shown on a valid JavaScript file in JavaScript Editor > ------------------------------------------------------------------------------------ > > Key: JBIDE-19393 > URL: https://issues.jboss.org/browse/JBIDE-19393 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.2.Final > Reporter: Victor Rubezhny > Fix For: 4.3.0.Beta1 > > Attachments: hybrid4001.zip, JavaScriptParserError.png > > > Multiple Error Annotations are shown on a valid JavaScript file in JavaScript Editor: > {code} > Multiple markers at this line > - Syntax error on token "Invalid Character", delete this token > - Missing semicolon > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19391) Properties File editor does not work properly

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19391?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-19391: ----------------------------------------------- That means that these files are not recognized as .properties files by the internal model used in the editor (only please make sure that it is 'Project Explorer', not 'Package Explorer'). Please look into Error Log after you push 'Add' button in Properties tab. There should be message like: "Cannot find action CreateActions.CreateProperty in entity %entityName%". Please add this message with your %entityName% to the issue description. > Properties File editor does not work properly > --------------------------------------------- > > Key: JBIDE-19391 > URL: https://issues.jboss.org/browse/JBIDE-19391 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Reporter: Ali Hopyar > Assignee: Viacheslav Kabanovich > Fix For: 4.3.x > > Attachments: messages_en.properties > > > On eclipse luna, I can not use JBoss editor for properties files. When I clicked add button nothing happens. When I click source tab and try to add some property, it is disappears when saved. Also if I open a property file that has been written before, also its content disappears. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3360: ---------------------------------- Therefore we would have: * a composite of JBDS (8.0, 8.0.1, 8.0.2, 8.1), but only one version of Central (the latest one for 8.1) inside /updates/8.0/ ; * a discovery plugin which referenced connectors specific to 8.1 (ie., the HMT/CS one would include FeedHenry); and * a URL from which content is resolved = /updates/8.0/ as defined by ide-config.properties. Does that sound correct? I think we're agreeing here... just want to make sure I understand your restatement, because you said "no" then repeated what I said. :D > Align bits offered in JBoss Central with installed version of JBDS > ------------------------------------------------------------------ > > Key: JBDS-3360 > URL: https://issues.jboss.org/browse/JBDS-3360 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, updatesite > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Fix For: 8.1.0.CR1 > > > The problem in JBDS-3359 shows a broader issue. > (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.) > Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites: > https://devstudio.redhat.com/updates/8.0/ > Initially this update site contained JBDS 8.0.0 core + 8.0.0 central. > But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users: > 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits > 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits) > Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also. > I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3360: ------------------------------------------- no, the user exposed updatesite(s) should have the combined content, but the discovery site would be what is in jbds 8.1 I would think. Since that is not actually listing updatesite nor specific versions it should be fine imo. > Align bits offered in JBoss Central with installed version of JBDS > ------------------------------------------------------------------ > > Key: JBDS-3360 > URL: https://issues.jboss.org/browse/JBDS-3360 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, updatesite > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Fix For: 8.1.0.CR1 > > > The problem in JBDS-3359 shows a broader issue. > (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.) > Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites: > https://devstudio.redhat.com/updates/8.0/ > Initially this update site contained JBDS 8.0.0 core + 8.0.0 central. > But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users: > 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits > 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits) > Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also. > I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 March 2015