[JBoss JIRA] (JBIDE-18485) NPE if repository definition doesnt contain <releases> or <snapshots>
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18485?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-18485.
---------------------------------
Resolution: Done
Applied https://github.com/jbosstools/jbosstools-central/pull/302 in master and 4.2.x
> NPE if repository definition doesnt contain <releases> or <snapshots>
> ---------------------------------------------------------------------
>
> Key: JBIDE-18485
> URL: https://issues.jboss.org/browse/JBIDE-18485
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.CR1
> Reporter: Rastislav Wagner
> Assignee: Rastislav Wagner
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.maven.ui.wizard.AddRepositoryDialog.updateRepository(AddRepositoryDialog.java:624)
> at org.jboss.tools.maven.ui.wizard.AddRepositoryDialog.selectProfile(AddRepositoryDialog.java:957)
> at org.jboss.tools.maven.ui.wizard.AddRepositoryDialog.createDialogArea(AddRepositoryDialog.java:306)
> at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:161)
> at org.eclipse.jface.window.Window.create(Window.java:435)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101)
> at org.eclipse.jface.window.Window.open(Window.java:797)
> at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.openEditRepositoryDialog(ConfigureMavenRepositoriesWizardPage.java:1287)
> at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.access$9(ConfigureMavenRepositoriesWizardPage.java:1268)
> at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage$5.widgetSelected(ConfigureMavenRepositoriesWizardPage.java:407)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.jboss.tools.maven.ui.preferences.ConfiguratorPreferencePage$2.widgetSelected(ConfiguratorPreferencePage.java:156)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:221)
> at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:66)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> 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:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18485) NPE if repository definition doesnt contain <releases> or <snapshots>
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18485?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18485:
--------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-central/pull/299, https://github.com/jbosstools/jbosstools-central/pull/302 (was: https://github.com/jbosstools/jbosstools-central/pull/299)
> NPE if repository definition doesnt contain <releases> or <snapshots>
> ---------------------------------------------------------------------
>
> Key: JBIDE-18485
> URL: https://issues.jboss.org/browse/JBIDE-18485
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.CR1
> Reporter: Rastislav Wagner
> Assignee: Rastislav Wagner
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.maven.ui.wizard.AddRepositoryDialog.updateRepository(AddRepositoryDialog.java:624)
> at org.jboss.tools.maven.ui.wizard.AddRepositoryDialog.selectProfile(AddRepositoryDialog.java:957)
> at org.jboss.tools.maven.ui.wizard.AddRepositoryDialog.createDialogArea(AddRepositoryDialog.java:306)
> at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:161)
> at org.eclipse.jface.window.Window.create(Window.java:435)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101)
> at org.eclipse.jface.window.Window.open(Window.java:797)
> at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.openEditRepositoryDialog(ConfigureMavenRepositoriesWizardPage.java:1287)
> at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.access$9(ConfigureMavenRepositoriesWizardPage.java:1268)
> at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage$5.widgetSelected(ConfigureMavenRepositoriesWizardPage.java:407)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.jboss.tools.maven.ui.preferences.ConfiguratorPreferencePage$2.widgetSelected(ConfiguratorPreferencePage.java:156)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:221)
> at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:66)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> 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:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3159) Usage dialog is not displayed for user after initial install
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3159?page=com.atlassian.jira.plugin.... ]
Len DiMaggio closed JBDS-3159.
------------------------------
> Usage dialog is not displayed for user after initial install
> ------------------------------------------------------------
>
> Key: JBDS-3159
> URL: https://issues.jboss.org/browse/JBDS-3159
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: usage
> Affects Versions: 8.0.0.CR1
> Reporter: Len DiMaggio
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 8.0.0.CR2
>
>
> I'm seeing this after an install - and after opening a new workspace - no usage dialog and:
> grep -r usage_reporting_enabled *
> studio/configuration/org.eclipse.osgi/5/0/.cp/plugin_customization.ini:org.tigris.subversion.subclipse.tools.usage/usage_reporting_enabled=false
> I am not seeing this problem with JBT and CR1.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18451) JMX Navigator pollutes error log with NullPointerException on Update Timer Cancel event
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18451?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18451.
---------------------------------
I don't see this in the error view, so I'm gonna close this. But to be honest I haven't seen it before either. So, [~dgolovin], feel free to reopen if you still see it. Verified in JBDS 8.0.0.CR2 B286
> JMX Navigator pollutes error log with NullPointerException on Update Timer Cancel event
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-18451
> URL: https://issues.jboss.org/browse/JBIDE-18451
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.2.0.CR1
> Environment: Fedora 20 x86_64, Java 7, Gnome 3
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
>
> I see a lot of exceptions in JBDS log like one below:
> {code}java.lang.NullPointerException
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.findHomeDirectoryToAddToClasspath(Tools.java:669)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.configureClassPathAndLibraryPath(Tools.java:691)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.<init>(Tools.java:77)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.getInstance(Tools.java:89)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:93)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:73)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505){code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18259) Refresh MBean section keeps blinking in the status bar
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18259?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18259.
---------------------------------
I verified that by default, the refresh period is now 5000 ms. It's still not ideal, but much better than before. Verified in JBDS 8.0.0.CR2 B286
> Refresh MBean section keeps blinking in the status bar
> ------------------------------------------------------
>
> Key: JBIDE-18259
> URL: https://issues.jboss.org/browse/JBIDE-18259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
> Attachments: refresh-mbean.png
>
>
> When you connect to a local process in the JMX Navigator and then check out some mbeans in the Properties view, there will be a "Refresh MBean section" message blinking in the status bar at the bottom of Eclipse every second or so.
> Screenshot:
> !refresh-mbean.png!
> Screencast:
> http://screencast.com/t/Tyc0isAane
> I understand that the tooling must keep refreshing the mbeans list (probably), but it's annoying to keep blinking in the status bar like this. We should probably remove that message.
> A minor issue is that the wording seems odd. Shouldn't it be "Refreshing MBean section..." or something like that? I'm not sure what the convention is here.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (TOOLSDOC-521) Review JIRA queries in Release Notes
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-521?page=com.atlassian.jira.plug... ]
Len DiMaggio commented on TOOLSDOC-521:
---------------------------------------
Is there a way in JIRA to save a static set of query results?
> Review JIRA queries in Release Notes
> ------------------------------------
>
> Key: TOOLSDOC-521
> URL: https://issues.jboss.org/browse/TOOLSDOC-521
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Components: Release Notes
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Michelle Murray
> Fix For: 4.2.0.Final
>
>
> When reviewing RNs for JBDS 8.0.0.CR1, we came to the conclusion that the JIRA queries may need updating.
> For reference, here's is discussion between me and Michelle on the subject:
> {quote}
> 01:23 mmalina: mmurray: I have a question about RN - resolved issues: (project in (JBDS) AND affectedVersion < "8.0.0.CR1" AND fixVersion in ("8.0.0.CR1") OR project in (JBIDE) AND affectedVersion < "4.2.0.CR1" AND fixVersion in ("4.2.0.CR1")) AND type in (Bug) AND resolution in (Done)
> 01:24 mmalina: mmurray: why have the fixVersion there? any special reason?
> 01:24 mmalina: mmurray: because it's 130 issues vs. 200 without it
> 01:24 maxandersen: don't use the < > comparisons. they unforatunely dont work reliably ;/
> 01:26 mmalina: maxandersen: the problem here is there are many jiras without affectedVersion
> 01:26 mmalina: *the main problem
> 01:26 mmalina: + what you say
> 01:27 maxandersen: mmalina: ah yeah. historically affectedVersion is only rarely used.
> 01:27 maxandersen: mmalina: only when we got very scifci issues where its important.
> 01:30 mmalina: mmurray: my only guess why you have it there is that you wanted to avoid jiras found in CR1 and fixed in CR1 - the thinking being that these would be new in CR1 and not present previously, thus you shouldn't list them in "what's fixed since the previous release". but that reasoning doesn't really work - 90 % bugs found in CR1 were already there before previously ;) any other reason to have it there?
> {quote}
> Michelle wrote:
> {quote}
> The search query is a best effort.
> The affects version is as you said, to avoid picking up internally identified bugs from QE/team testing CR1respinA that were fixed in CR1respinB, say. The customer doesn't need to know or care about these.
> The fixed version is a bit more complicated. The problem is that this query goes into the doc and the search results effectively have to remain static for all time - the doc could be hosted for years to come. This CR1 RNs doc should only list the bugs fixed in the CR1 release. If I leave the fixversion out then when bugs identified in <8.0.0.CR1 get resolved for CR2 or GA or even 9.1.0 they will show up in this query and that screws up the doc. The CR1 RNs doc we get replaced with a GA version so it isn't so important for this one but it is for the GA copy and it's easier to keep basically the same query as I iterate the doc towards GA.
> Regards using < and >, they are working effectively from what I can see. To make the comparisons work it just needs the versions to be listed in chronological order on the JBIDE and JBDS jira project pages.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-14001) First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14001?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-14001.
---------------------------------
This was verified as part of JBIDE-18287 verification. Closing.
> First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14001
> URL: https://issues.jboss.org/browse/JBIDE-14001
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.0.1.Final
> Environment: Windows 7
> Reporter: David Stephan
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
>
> After Marking a jar as deployable and deploying to EAP server, the jar is deployed correctly.
> Then, after restarting JBDS, then restarting the app server from within JBDS, the deployed jar is deleted.
> After restarting the server again, the jar is deployed, and subsequent restarts don't remove the jar.
> Possibly related, when you first mark the jar as deployable and deploy to a server, the context menu item changes to "Unmark as Deployable." After a restart of JBDS, this context menu item is back to "Mark as Deployable".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months