December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-17895) Update to Luna SR2 for synchronization bug

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17895?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17895: -------------------------------- Fix Version/s: 4.2.2.Final (was: 4.2.1.Final) > Update to Luna SR2 for synchronization bug > ------------------------------------------ > > Key: JBIDE-17895 > URL: https://issues.jboss.org/browse/JBIDE-17895 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, server, target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.2.Final > > Attachments: jbds_plugins.txt > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=437351 > The patch build currently lives at http://build.eclipse.org/webtools/committers/patches-R3.6.0-P/20140701141... > However, I'm not sure that's the ultimate location for the future. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3200: ------------------------------ Priority: Blocker (was: Minor) > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 8.0.2.GA, 9.0.0.Alpha1 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18572) NPE while calling a diff between 2 versions of a JS file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18572?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18572: ----------------------------------- Priority: Critical (was: Blocker) > NPE while calling a diff between 2 versions of a JS file > -------------------------------------------------------- > > Key: JBIDE-18572 > URL: https://issues.jboss.org/browse/JBIDE-18572 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.CR1 > Reporter: Xavier Coulon > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.1.Final > > > Not sure if the error is related {{summarry}}, but here's the stacktrace: > I did compare my current JS file with the first version in my history, which was an empty file, then I called the diff with the next version and I got this error. I kept having this error when comparing the current version with any other version of the file (if that can help to reproduce/identify the problem) > {code} > java.lang.NullPointerException > at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:572) > at org.jboss.tools.vpe.preview.editor.VpvEditor.access$0(VpvEditor.java:551) > at org.jboss.tools.vpe.preview.editor.VpvEditor$EditorListener.partInputChanged(VpvEditor.java:674) > at org.eclipse.ui.internal.WorkbenchPage$28.run(WorkbenchPage.java:5151) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.WorkbenchPage.firePartInputChanged(WorkbenchPage.java:5148) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$4.propertyChanged(CompatibilityPart.java:369) > at org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:132) > at org.eclipse.compare.internal.CompareEditor.doSetInput(CompareEditor.java:313) > at org.eclipse.compare.internal.CompareEditor.setInput(CompareEditor.java:254) > at org.eclipse.compare.internal.CompareUIPlugin$1.run(CompareUIPlugin.java:546) > at org.eclipse.compare.internal.CompareUIPlugin.syncExec(CompareUIPlugin.java:1413) > at org.eclipse.compare.internal.CompareUIPlugin.internalOpenEditor(CompareUIPlugin.java:567) > at org.eclipse.compare.internal.CompareUIPlugin.openEditorInBackground(CompareUIPlugin.java:537) > at org.eclipse.compare.internal.CompareUIPlugin.openCompareEditor(CompareUIPlugin.java:526) > at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:199) > at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:180) > at org.eclipse.team.internal.ui.actions.CompareRevisionAction.openInCompare(CompareRevisionAction.java:139) > at org.eclipse.team.internal.ui.actions.CompareRevisionAction.run(CompareRevisionAction.java:102) > at org.eclipse.team.internal.ui.history.LocalHistoryPage$9.open(LocalHistoryPage.java:414) > at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) > at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:853) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178) > at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:850) > at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1142) > at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1249) > at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278) > at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272) > at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > 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:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:484) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3200: ------------------------------ Fix Version/s: 8.0.2.GA (was: 8.0.1.GA) > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 8.0.2.GA, 9.0.0.Alpha1 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18497) Importing PicketLink quickstart raises error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18497?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18497: -------------------------------- Fix Version/s: (was: 4.2.1.Final) > Importing PicketLink quickstart raises error > -------------------------------------------- > > Key: JBIDE-18497 > URL: https://issues.jboss.org/browse/JBIDE-18497 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.CR1 > Java 1.7 - OpenJDK > RHEL6 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha1 > > > Steps to recreate issue: > * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap > * Install JBDS8.0.CR1 > * Import-> Existing Maven Projects - select the quickstart > The error is: > jboss-picketlink-sts > Referenced file contains errors (http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-wsse-server.xml /jboss-picketlink-sts/src/main/webapp/WEB-INF line 1 XML Problem -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18527) "rm -rf project" in Forge Console doesn't delete project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18527?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18527: ------------------------------------- Proposed solution wipes all orphaned eclipse projects. I think it's debatable. I'd rather prefer Forge Tools limits its housecleaning scope to the project that was just deleted > "rm -rf project" in Forge Console doesn't delete project > -------------------------------------------------------- > > Key: JBIDE-18527 > URL: https://issues.jboss.org/browse/JBIDE-18527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR2 > Reporter: Pavol Srna > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > {code} > org.eclipse.core.internal.resources.ResourceException: Errors occurred while refreshing resources with the local file system. > at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:923) > at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:904) > at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshRoot(FileSystemResourceManager.java:951) > at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:897) > at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1705) > at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.refreshResource(CommandLineListener.java:315) > at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.refresh(CommandLineListener.java:129) > at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.access$2(CommandLineListener.java:126) > at org.jboss.tools.forge.ui.internal.cli.CommandLineListener$1.run(CommandLineListener.java:86) > 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:3774) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3412) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > 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:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > 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) > Contains: The project description file (.project) for 'jboss-as-kitchensink-html5-mobile' is missing. This file contains important information about the project. The project will not function properly until this file is restored. > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18667) Fixing SWT issues in Luna SR2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18667?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18667: ------------------------------------- None of these issues has been fixed in Luna SR1. Punting to 4.2.2, hoping for a fix in Luna SR2 > Fixing SWT issues in Luna SR2 > ----------------------------- > > Key: JBIDE-18667 > URL: https://issues.jboss.org/browse/JBIDE-18667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Reporter: Jiri Peterka > Fix For: 4.2.2.Final > > > Unresolved issues in Luna SR1 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431421 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431423 > https://issues.jboss.org/browse/JBIDE-16879 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431425 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=434898 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18667) Fixing SWT issues in Luna SR1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18667?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18667: -------------------------------- Fix Version/s: 4.2.2.Final (was: 4.2.1.Final) > Fixing SWT issues in Luna SR1 > ----------------------------- > > Key: JBIDE-18667 > URL: https://issues.jboss.org/browse/JBIDE-18667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Reporter: Jiri Peterka > Fix For: 4.2.2.Final > > > Unresolved issues in Luna SR1 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431421 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431423 > https://issues.jboss.org/browse/JBIDE-16879 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431425 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=434898 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18667) Fixing SWT issues in Luna SR2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18667?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18667: -------------------------------- Summary: Fixing SWT issues in Luna SR2 (was: Fixing SWT issues in Luna SR1) > Fixing SWT issues in Luna SR2 > ----------------------------- > > Key: JBIDE-18667 > URL: https://issues.jboss.org/browse/JBIDE-18667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Reporter: Jiri Peterka > Fix For: 4.2.2.Final > > > Unresolved issues in Luna SR1 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431421 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431423 > https://issues.jboss.org/browse/JBIDE-16879 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431425 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=434898 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18711) Cordova plugin addition and removal fails when config.xml is in a linked folder

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18711?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-18711. ------------------------------------ Resolution: Done [~vpakan] please open a separate issue. I'm resolving this one. > Cordova plugin addition and removal fails when config.xml is in a linked folder > ------------------------------------------------------------------------------- > > Key: JBIDE-18711 > URL: https://issues.jboss.org/browse/JBIDE-18711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Final > Environment: Oracle JDK 1.8.0_05, Mac OS X Mavericks > Reporter: Vineet Reynolds > Assignee: Gorkem Ercan > Fix For: 4.2.1.CR1 > > > When config.xml is present in an Eclipse Linked folder (not in a symbolic link), then attempting to add or remove plugins (and possibly other operations on config.xml) fails with a spurious NullPointerException (without a stacktrace). > This pretty much means that the Hybrid Mobile application project with a linked folder for 'www' is in a read-only state for plugin addition/removal. If any plugin should be added or removed, the linked folder must be dropped, converted to an ordinary folder (or symbolic link), and then re-created after modifications. > To verify > 1. create a new project > 2. copy www folder to an alternate location > 3. remove www folder > 4.add www folder from alternate location as a linked folder (New Folder > Advanced> Link to alternate location) > 5. add cordova plugins to the project. [Check they are added] -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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 December 2014