[JBoss JIRA] (JBIDE-20636) Push changes: Deployment wont get performed, management interface wont come up
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20636?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20636:
-------------------------------------
Summary: Push changes: Deployment wont get performed, management interface wont come up (was: trouble performing the deployment in jboss management interface by Eclipse using )
> Push changes: Deployment wont get performed, management interface wont come up
> ------------------------------------------------------------------------------
>
> Key: JBIDE-20636
> URL: https://issues.jboss.org/browse/JBIDE-20636
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Labels: openshift_v2
> Fix For: 4.3.1.Final
>
>
> Reference: https://github.com/openshift/origin/issues/4502
> {code}
> Preparing build for deployment Deployment id is f2c69660 Activating deployment Starting PHPMyAdmin cartridge Starting MySQL 5.5 cartridge Deploying JBoss Starting jbossas cartridge Found 127.3.158.129:8080 listening port Found 127.3.158.129:9999 listening port CLIENT_MESSAGE: Could not connect to JBoss management interface, skipping deployment verification ------------------------- Git Post-Receive Result: success Activation status: success Deployment completed with status: success
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20754) org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path - part 2
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20754?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-20754:
--------------------------------------
Martin - is this also a problem in CR1?
> org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path - part 2
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20754
> URL: https://issues.jboss.org/browse/JBIDE-20754
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.Beta2
> Environment: Windows 7 x64, Eclipse Mars (4.5.0), Java 1.8.0u51
> Reporter: Daniel Atallah
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.Final
>
>
> org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore:97 should either use the Runtime.getRuntime().exec(String[]) method to deal with Java installation locations containing spaces.
> In my case the {{java.home}} system property points to {{"C:\Program Files\Java\jdk1.8.0_51"}}, which I think would be pretty normal on Windows.
> {noformat}
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at java.lang.Runtime.exec(Runtime.java:620)
> at java.lang.Runtime.exec(Runtime.java:450)
> at java.lang.Runtime.exec(Runtime.java:347)
> at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:97)
> at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64)
> at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:135)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
> at java.lang.ProcessImpl.start(ProcessImpl.java:137)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> ... 7 more
> {noformat}
> I'm note sure what the impact is - I don't necessarily notice anything not working.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20754) org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path - part 2
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20754?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20754:
-----------------------------------
Fix Version/s: 4.3.1.Final
(was: 4.3.x)
> org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path - part 2
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20754
> URL: https://issues.jboss.org/browse/JBIDE-20754
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.Beta2
> Environment: Windows 7 x64, Eclipse Mars (4.5.0), Java 1.8.0u51
> Reporter: Daniel Atallah
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.Final
>
>
> org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore:97 should either use the Runtime.getRuntime().exec(String[]) method to deal with Java installation locations containing spaces.
> In my case the {{java.home}} system property points to {{"C:\Program Files\Java\jdk1.8.0_51"}}, which I think would be pretty normal on Windows.
> {noformat}
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at java.lang.Runtime.exec(Runtime.java:620)
> at java.lang.Runtime.exec(Runtime.java:450)
> at java.lang.Runtime.exec(Runtime.java:347)
> at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:97)
> at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64)
> at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:135)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
> at java.lang.ProcessImpl.start(ProcessImpl.java:137)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> ... 7 more
> {noformat}
> I'm note sure what the impact is - I don't necessarily notice anything not working.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20636) trouble performing the deployment in jboss management interface by Eclipse using
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20636?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20636:
-------------------------------------
Labels: openshift_v2 (was: )
> trouble performing the deployment in jboss management interface by Eclipse using
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-20636
> URL: https://issues.jboss.org/browse/JBIDE-20636
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Labels: openshift_v2
> Fix For: 4.3.1.Final
>
>
> Reference: https://github.com/openshift/origin/issues/4502
> {code}
> Preparing build for deployment Deployment id is f2c69660 Activating deployment Starting PHPMyAdmin cartridge Starting MySQL 5.5 cartridge Deploying JBoss Starting jbossas cartridge Found 127.3.158.129:8080 listening port Found 127.3.158.129:9999 listening port CLIENT_MESSAGE: Could not connect to JBoss management interface, skipping deployment verification ------------------------- Git Post-Receive Result: success Activation status: success Deployment completed with status: success
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20753) Text flickering when selecting server types in New Server wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20753?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20753:
-----------------------------------
Fix Version/s: 4.3.1.Final
(was: 4.3.0.Final)
> Text flickering when selecting server types in New Server wizard
> ----------------------------------------------------------------
>
> Key: JBIDE-20753
> URL: https://issues.jboss.org/browse/JBIDE-20753
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: regression
> Fix For: 4.3.1.Final
>
>
> When you open the New Server wizard and select a server type, There will be some elements rendered for a fraction of a second. It's Server Runtime Environment and a dropdown menu - it will disappear again, but it's not nice to see something quickly appear and disappear again. You can keep selecting server types and it will keep happening. All of this is on the first page of the dialog.
> I checked and this did not happen in Beta2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20759) Add project name validation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20759?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20759:
-----------------------------------
Fix Version/s: 4.3.x
> Add project name validation
> ---------------------------
>
> Key: JBIDE-20759
> URL: https://issues.jboss.org/browse/JBIDE-20759
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Fix For: 4.3.x
>
>
> We have validation of a project name just for its length which is supposed to be between 2 and 63 characters. But we have no validation on the form of a project name which has to be matching regex [a-z0-9]([-a-z0-9]*[a-z0-9]. Currently it is possible to type name e.g. "myProject" and there is no validation although it is not a valid name and creation fails.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20758) NullPointerException when creating new artifact from Properties view
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20758?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20758:
-----------------------------------
Fix Version/s: 4.3.1.Final
4.4.0.Alpha1
> NullPointerException when creating new artifact from Properties view
> --------------------------------------------------------------------
>
> Key: JBIDE-20758
> URL: https://issues.jboss.org/browse/JBIDE-20758
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.CR1
> Reporter: Lucia Jelinkova
> Priority: Critical
> Fix For: 4.3.1.Final, 4.4.0.Alpha1
>
>
> When I try to create new artifact from suggestion box in Properties view, I get the following NullPointerException. It happens only if the ref field is empty, it does not happen if there is something written.
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.batch.ui.editor.internal.action.OpenOrCreateArtifactActionDelegate.run(OpenOrCreateArtifactActionDelegate.java:139)
> at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDialog$1.linkActivated(PropertyEditorAssistDialog.java:146)
> at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText.activateLink(SapphireFormText.java:1583)
> at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText.handleMouseClick(SapphireFormText.java:1374)
> at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText.access$16(SapphireFormText.java:1345)
> at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText$6.mouseUp(SapphireFormText.java:445)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.sapphire.ui.forms.swt.Popup.open(Popup.java:250)
> at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDecorator.openAssistDialog(PropertyEditorAssistDecorator.java:407)
> at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDecorator.access$3(PropertyEditorAssistDecorator.java:385)
> at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDecorator$6.mouseUp(PropertyEditorAssistDecorator.java:285)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20756) Touch events for BrowserSim are not set properly
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20756?page=com.atlassian.jira.plugi... ]
Ilya Buziuk reassigned JBIDE-20756:
-----------------------------------
Assignee: Konstantin Marmalyukov (was: Ilya Buziuk)
> Touch events for BrowserSim are not set properly
> ------------------------------------------------
>
> Key: JBIDE-20756
> URL: https://issues.jboss.org/browse/JBIDE-20756
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.3.0.CR1
> Environment: JBDS 9.0.0.CR1-v20150918-0257-B105 Fedora 22 KDE 64bit
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.x
>
>
> 1. Create HTML page with this content:
> {code:html}
> <!DOCTYPE html>
> <html>
> <head>
> <title>sample</title>
> <script type="text/javascript">
> function window_onload() {
> document.getElementById('touchable').addEventListener('touchstart', function(ev) {
> alert('touchstart')}, false);
> document.getElementById('touchable').addEventListener('touchend', function(ev) {
> alert('touchend')}, false);
> document.getElementById('touchable').addEventListener('touchmove', function(ev) {
> alert('touchmove')}, false);
> }
> </script>
> </head>
> <body onload='window_onload();'>
> <div id='touchable'>This element is touchable.</div>
> </body>
> </html>
> {code}
> 2. Open this page in BrowserSim
> 3. Enable touch events for BrowserSim
> 4. Click somewhere within the page in BrowserSim
> ERROR:
> {noformat}
> !JavaScript WARN: Converting `ontouchstart` property to event listener.
> !JavaScript ERROR: TypeError: Unable to delete property. on line 118 for file:///.../jboss-touchevents/src/main/webapp/index.html
> !JavaScript WARN: Converting `ontouchend` property to event listener.
> !JavaScript ERROR: TypeError: Unable to delete property. on line 118 for file:///.../jboss-touchevents/src/main/webapp/index.html
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20758) NullPointerException when creating new artifact from Properties view
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20758?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20758:
--------------------------------------
Assignee: Viacheslav Kabanovich
> NullPointerException when creating new artifact from Properties view
> --------------------------------------------------------------------
>
> Key: JBIDE-20758
> URL: https://issues.jboss.org/browse/JBIDE-20758
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.CR1
> Reporter: Lucia Jelinkova
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.3.1.Final, 4.4.0.Alpha1
>
>
> When I try to create new artifact from suggestion box in Properties view, I get the following NullPointerException. It happens only if the ref field is empty, it does not happen if there is something written.
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.batch.ui.editor.internal.action.OpenOrCreateArtifactActionDelegate.run(OpenOrCreateArtifactActionDelegate.java:139)
> at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDialog$1.linkActivated(PropertyEditorAssistDialog.java:146)
> at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText.activateLink(SapphireFormText.java:1583)
> at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText.handleMouseClick(SapphireFormText.java:1374)
> at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText.access$16(SapphireFormText.java:1345)
> at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText$6.mouseUp(SapphireFormText.java:445)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.sapphire.ui.forms.swt.Popup.open(Popup.java:250)
> at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDecorator.openAssistDialog(PropertyEditorAssistDecorator.java:407)
> at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDecorator.access$3(PropertyEditorAssistDecorator.java:385)
> at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDecorator$6.mouseUp(PropertyEditorAssistDecorator.java:285)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months