[JBoss JIRA] (ERT-331) NullPointerException in ImageRunSelectionModel.<init> [EBZ#497422]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-331?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston resolved ERT-331.
-------------------------------
Resolution: Done
> NullPointerException in ImageRunSelectionModel.<init> [EBZ#497422]
> ------------------------------------------------------------------
>
> Key: ERT-331
> URL: https://issues.jboss.org/browse/ERT-331
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Jeff Johnston
> Labels: 5.1.0, Docker, bzira
> Fix For: Neon.1 (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> java.lang.NullPointerException: null
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageRunSelectionModel.<init>(ImageRunSelectionModel.java:111)
> at org.eclipse.linuxtools.internal.docker.ui.launch.RunImageLaunchConfigurationTabGroup.createTabs(RunImageLaunchConfigurationTabGroup.java:48)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.createTabs(LaunchConfigurationTabGroupWrapper.java:141)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$9.run(LaunchConfigurationTabGroupViewer.java:882)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.createGroup(LaunchConfigurationTabGroupViewer.java:891)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showInstanceTabsFor(LaunchConfigurationTabGroupViewer.java:795)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:750)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:637)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:654)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:615)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:590)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:960)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:573)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:878)
> 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:173)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:875)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1244)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1270)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1.lambda$1(OpenStrategy.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528)
> Bundles:
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.linuxtools.docker.ui | 2.0.0.201606101757 | 2.0.0.201606101757 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 |
> Operating Systems:
> | Linux | 4.4.0 | 4.5.7.fc23 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/57736... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> Created on behalf of jjohnstn(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ERT-331) NullPointerException in ImageRunSelectionModel.<init> [EBZ#497422]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-331?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston reassigned ERT-331:
---------------------------------
Assignee: Jeff Johnston
> NullPointerException in ImageRunSelectionModel.<init> [EBZ#497422]
> ------------------------------------------------------------------
>
> Key: ERT-331
> URL: https://issues.jboss.org/browse/ERT-331
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Jeff Johnston
> Labels: 5.1.0, Docker, bzira
> Fix For: Neon.1 (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> java.lang.NullPointerException: null
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageRunSelectionModel.<init>(ImageRunSelectionModel.java:111)
> at org.eclipse.linuxtools.internal.docker.ui.launch.RunImageLaunchConfigurationTabGroup.createTabs(RunImageLaunchConfigurationTabGroup.java:48)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.createTabs(LaunchConfigurationTabGroupWrapper.java:141)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$9.run(LaunchConfigurationTabGroupViewer.java:882)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.createGroup(LaunchConfigurationTabGroupViewer.java:891)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showInstanceTabsFor(LaunchConfigurationTabGroupViewer.java:795)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:750)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:637)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:654)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:615)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:590)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:960)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:573)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:878)
> 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:173)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:875)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1244)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1270)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1.lambda$1(OpenStrategy.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528)
> Bundles:
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.linuxtools.docker.ui | 2.0.0.201606101757 | 2.0.0.201606101757 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 |
> Operating Systems:
> | Linux | 4.4.0 | 4.5.7.fc23 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/57736... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> Created on behalf of jjohnstn(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ERT-331) NullPointerException in ImageRunSelectionModel.<init> [EBZ#497422]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-331?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston updated ERT-331:
------------------------------
Sprint: devex #117 July 2016
> NullPointerException in ImageRunSelectionModel.<init> [EBZ#497422]
> ------------------------------------------------------------------
>
> Key: ERT-331
> URL: https://issues.jboss.org/browse/ERT-331
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: 5.1.0, Docker, bzira
> Fix For: Neon.1 (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> java.lang.NullPointerException: null
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageRunSelectionModel.<init>(ImageRunSelectionModel.java:111)
> at org.eclipse.linuxtools.internal.docker.ui.launch.RunImageLaunchConfigurationTabGroup.createTabs(RunImageLaunchConfigurationTabGroup.java:48)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.createTabs(LaunchConfigurationTabGroupWrapper.java:141)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$9.run(LaunchConfigurationTabGroupViewer.java:882)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.createGroup(LaunchConfigurationTabGroupViewer.java:891)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showInstanceTabsFor(LaunchConfigurationTabGroupViewer.java:795)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:750)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:637)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:654)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:615)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:590)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:960)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:573)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:878)
> 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:173)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:875)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1244)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1270)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1.lambda$1(OpenStrategy.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528)
> Bundles:
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.linuxtools.docker.ui | 2.0.0.201606101757 | 2.0.0.201606101757 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 |
> Operating Systems:
> | Linux | 4.4.0 | 4.5.7.fc23 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/57736... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> Created on behalf of jjohnstn(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19081:
------------------------------------
With this successfully applied in Base, but nowhere else...
is the plan to roll that out to all the projects? Maybe we want to split the jira into 15 child tasks, one per project?
then when everyone has reviewed if they're better/worse after the change, and everyone has done it, we can move the change into parent pom instead of being controlled at the per-project level
[~fbricon] [~akazakov] wdyt?
> Use simpler Surefire include/exclude pattern in parent pom
> ----------------------------------------------------------
>
> Key: JBIDE-19081
> URL: https://issues.jboss.org/browse/JBIDE-19081
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.4.x
>
>
> 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude:
> {code}
> include = *Test*, *Test, *TestCase
> exclude = *Abstract*
> {code}
> 2. If that causes test failures because running incorrectly named
> abstract stuff, they can refactor, add their own root pom overrides, use
> a TestSuite, or use @Ignore in test classes.
> 3. If the count of tests run suddenly DROPS because the pattern isn't
> running the correct # of tests, they can add their own root pom
> overrides, or use a TestSuite.
> Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22696) jbosstools and devstudio sites / installer use old timestamps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22696?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22696 at 7/7/16 12:29 PM:
-------------------------------------------------------------
Looks like our config for forcing certain artifacts to use the CURRENT timestamp instead of github timestamp is incorrect.
This should fix it for Base/Foundation: https://github.com/jbosstools/jbosstools-base/pull/518
{code}
$➔ ll site/target/repository/plugins/ | grep AM1
-rw-rw-r-- 1 nboldt nboldt 81K Jul 7 12:19 org.jboss.tools.foundation.core.source_1.3.1.AM1-v20160707-1617.jar
-rw-rw-r-- 1 nboldt nboldt 104K Jul 7 12:19 org.jboss.tools.foundation.core_1.3.1.AM1-v20160707-1617.jar
{code}
Updated PRs for jbosstools-build-sites and jbdevstudio-product, too.
was (Author: nickboldt):
Looks like our config for forcing certain artifacts to use the CURRENT timestamp instead of github timestamp is incorrect.
This should fix it for Base/Foundation: https://github.com/jbosstools/jbosstools-base/pull/518
Updated PRs for jbosstools-build-sites and jbdevstudio-product, too.
> jbosstools and devstudio sites / installer use old timestamps
> -------------------------------------------------------------
>
> Key: JBIDE-22696
> URL: https://issues.jboss.org/browse/JBIDE-22696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.4.1.AM2
>
> Attachments: devstudio10.01.png, jbt441.png
>
>
> Build id of devstudio installers contains old timestamp. E.g. latest build 2016-07-05_17-10-13-B5634 contains timestamp 20160613-2041 although the build which is producing bits is 20160705-5634.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22696) jbosstools and devstudio sites / installer use old timestamps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22696?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22696 at 7/7/16 12:22 PM:
-------------------------------------------------------------
With the amended PRs, I now get filenames like this for the devstudio installer:
{code}
mvn clean install -DBUILD_NUMBER=460000 -P hudson
...
devstudio-10.0.1.AM1-v20160707-1612-B460000-installer-standalone.jar{code}
And the update site is again correctly versioned:
{code}Latest Build 10.0.1-SNAPSHOT (AM1-v20160707-1612-B460000){code}
was (Author: nickboldt):
With the amended PRs, I now get filenames like this for the devstudio installer:
{code}
mvn clean install -DBUILD_NUMBER=460000 -P hudson
...
devstudio-10.0.1.AM1-v20160707-1612-B460000-installer-standalone.jar{code}
> jbosstools and devstudio sites / installer use old timestamps
> -------------------------------------------------------------
>
> Key: JBIDE-22696
> URL: https://issues.jboss.org/browse/JBIDE-22696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.4.1.AM2
>
> Attachments: devstudio10.01.png, jbt441.png
>
>
> Build id of devstudio installers contains old timestamp. E.g. latest build 2016-07-05_17-10-13-B5634 contains timestamp 20160613-2041 although the build which is producing bits is 20160705-5634.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22696) jbosstools and devstudio sites / installer use old timestamps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22696?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22696:
------------------------------------
With the amended PRs, I now get filenames like this for the devstudio installer:
{code}
mvn clean install -DBUILD_NUMBER=460000 -P hudson
...
devstudio-10.0.1.AM1-v20160707-1612-B460000-installer-standalone.jar{code}
> jbosstools and devstudio sites / installer use old timestamps
> -------------------------------------------------------------
>
> Key: JBIDE-22696
> URL: https://issues.jboss.org/browse/JBIDE-22696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.4.1.AM2
>
> Attachments: devstudio10.01.png, jbt441.png
>
>
> Build id of devstudio installers contains old timestamp. E.g. latest build 2016-07-05_17-10-13-B5634 contains timestamp 20160613-2041 although the build which is producing bits is 20160705-5634.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months