[JBoss JIRA] (JBIDE-18572) NPE while calling a diff between 2 versions of a JS file
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18572?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18572:
------------------------------------------------
I analyze stacktrace more carefully. Looks like listener "somehow" was not removed. But this error actually happens in dead code, which was already removed from master and 4.2.x. So it will not be reproduced again.
> 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.2.Final, 4.3.0.Alpha1
>
>
> 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
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3208:
-------------------------------------
Under updates like
* /\{mars,9.0}/
** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
*** /*updates*/
**** /\{*targetplatforms*,core,coretests,webtools,hibernatetools,discovery,central,earlyaccess,integration-stack,integration-stack-earlyaccess}/
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> {code}
> download.jboss.org
> <earlyaccess,updates,discovery>/mars
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/mars/stable is a pointer back into updates/mars)
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last 2 builds
> targetplatforms/<type>/<version>
> {code}
> and
> {code}
> devstudio.redhat.com
> <earlyaccess,updates,discovery>/9.0
> /snapshots
> /staging
> /development
> /stable (updates/9.0/stable is a pointer back into updates/9.0)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last 2 builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18873) Hibernate versions should be listed most recent version first
by Koen Aers (JIRA)
Koen Aers created JBIDE-18873:
---------------------------------
Summary: Hibernate versions should be listed most recent version first
Key: JBIDE-18873
URL: https://issues.jboss.org/browse/JBIDE-18873
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: hibernate
Affects Versions: 4.2.0.Final
Reporter: Koen Aers
Assignee: Koen Aers
Fix For: 4.3.0.Alpha1
When creating a console configuration the most recent hibernate version should be listed on top. Currently the order is alphabetical, it should be reversed.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-13835) Improve publish script (split? Move to maven?)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13835?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13835 at 12/4/14 12:14 PM:
--------------------------------------------------------------
Yes, and if we're OK with "no installers on devstudio.redhat.com because they go to GoldenGate/CSP/www.jboss.org" then we can have TWO publishing steps for JBDS:
a) generic "update site publish" script, which also publishes the update site zip / target platform zips
b) specific-to-JBDS internal only "installer folder publish" script
With the proposed changes in JBDS-3208, making the update site publish script more generic for both JBT/JBDS/IS will be easier. [~maxandersen] [~mickael_istria] can we get some +1s and quorum on that? I'd like to start moving stuff around for Mars.
was (Author: nickboldt):
Yes, and if we're OK with "no installers on devstudio.redhat.com because they go to GoldenGate/CSP/www.jboss.org" then we can have TWO publishing steps for JBDS:
a) generic "push update site" script, which also publishes the update site zip / target platform zips
b) specific-to-JBDS internal only "copy build folder w/ installers onto www.qa" script
> Improve publish script (split? Move to maven?)
> ----------------------------------------------
>
> Key: JBIDE-13835
> URL: https://issues.jboss.org/browse/JBIDE-13835
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Fix For: 4.3.x
>
>
> Publish script deals with a lot of different and not-always-related things. It makes it difficult to maintain it. We should think about some improvements such as
> * different conventions from different stream
> * components vs aggregate
> * devstudio vs jbosstools.
> Or,
> * Make publishing part of a "mvn deploy" step.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-13835) Improve publish script (split? Move to maven?)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13835?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13835:
------------------------------------
Yes, and if we're OK with "no installers on devstudio.redhat.com because they go to GoldenGate/CSP/www.jboss.org" then we can have TWO publishing steps for JBDS:
a) generic "push update site" script, which also publishes the update site zip / target platform zips
b) specific-to-JBDS internal only "copy build folder w/ installers onto www.qa" script
> Improve publish script (split? Move to maven?)
> ----------------------------------------------
>
> Key: JBIDE-13835
> URL: https://issues.jboss.org/browse/JBIDE-13835
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Fix For: 4.3.x
>
>
> Publish script deals with a lot of different and not-always-related things. It makes it difficult to maintain it. We should think about some improvements such as
> * different conventions from different stream
> * components vs aggregate
> * devstudio vs jbosstools.
> Or,
> * Make publishing part of a "mvn deploy" step.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBTIS-358) Use wrapper features to simplify the install and clean up the Marketplace UI?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-358?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-358 at 12/4/14 12:07 PM:
------------------------------------------------------------
These features are simply there to facilitate using the Marketplace UI -- instead of 29 features on the marketplace entry, we'd have 5. They're not there to restrict installation or enforce updateability. They're just there to encourage installation of the correct groups of features, including causing parts of JBT or JBDS to be co-installed (central, usage, project examples).
So, like with the JBDS update site, I'd expect these features WOULD be categorized. And then instead of listing all the child features in JBoss Central we could list the container features so that marketplace == central.
was (Author: nickboldt):
These features are simply there to facilitate using the Marketplace UI -- instead of 29 features on the marketplace entry, we'd have 5. They're not there to restrict installation or enforce updateability. They're just there to encourage installation of the correct groups of features, including causing parts of JBT or JBDS to be co-installed (central, usage, project examples).
> Use wrapper features to simplify the install and clean up the Marketplace UI?
> -----------------------------------------------------------------------------
>
> Key: JBTIS-358
> URL: https://issues.jboss.org/browse/JBTIS-358
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 7.0.3.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.GA-JBDSIS
>
> Attachments: is-marketplace1.png, is-marketplace2.png
>
>
> For 7.1.0, could consider having wrapper features to simplify the install and clean up the Marketplace UI. Doing so would mean instead of a laundry list of features in the UI, we could list only 3 features.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBTIS-358) Use wrapper features to simplify the install and clean up the Marketplace UI?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-358?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-358:
----------------------------------
These features are simply there to facilitate using the Marketplace UI -- instead of 29 features on the marketplace entry, we'd have 5. They're not there to restrict installation or enforce updateability. They're just there to encourage installation of the correct groups of features, including causing parts of JBT or JBDS to be co-installed (central, usage, project examples).
> Use wrapper features to simplify the install and clean up the Marketplace UI?
> -----------------------------------------------------------------------------
>
> Key: JBTIS-358
> URL: https://issues.jboss.org/browse/JBTIS-358
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 7.0.3.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.GA-JBDSIS
>
> Attachments: is-marketplace1.png, is-marketplace2.png
>
>
> For 7.1.0, could consider having wrapper features to simplify the install and clean up the Marketplace UI. Doing so would mean instead of a laundry list of features in the UI, we could list only 3 features.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18527) "rm -rf project" in Forge Console doesn't delete project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18527?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18527:
---------------------------------------------
oooh - didn't notice that sideeffect [~fbricon] ...thats not nice. -1 for this fix until forge can provide enough context to say which folders disappeared.
> "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