[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-18177:
-------------------------------------
Also this scenario is confusing:
1. Set HTML5 support
2. Open .xhtml page and say "Stay with HTML5"
3. Open .html page
4. Restart Eclipse
5. Close .html page
ERROR: Dialog asking to choose between HTML5 or JSF support is displayed. It's confusing to ask this when page is closed.
> Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18177
> URL: https://issues.jboss.org/browse/JBIDE-18177
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Labels: f2f2014, new_and_noteworthy, requirements
> Fix For: 4.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner)
> if he says okey - we set a flag somewhere to not start xulrunner.
> user restart - user is happy.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-18177:
-------------------------------------
I understand why page is opened before Eclipse restart but it's not really user friendly and in case of big page it could be also time consuming. Would be nicer to not open page before restart and find a way how to open it after restart.
> Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18177
> URL: https://issues.jboss.org/browse/JBIDE-18177
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Labels: f2f2014, new_and_noteworthy, requirements
> Fix For: 4.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner)
> if he says okey - we set a flag somewhere to not start xulrunner.
> user restart - user is happy.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19241) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19241?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-19241:
-------------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Arquillian]
> ---------------------------------------------------------
>
> Key: JBIDE-19241
> URL: https://issues.jboss.org/browse/JBIDE-19241
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Arquillian]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19243) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Portlet]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19243?page=com.atlassian.jira.plugi... ]
Snjezana Peco resolved JBIDE-19243.
-----------------------------------
Resolution: Rejected
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Portlet]
> ------------------------------------------------------
>
> Key: JBIDE-19243
> URL: https://issues.jboss.org/browse/JBIDE-19243
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: portal-gatein
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Portlet]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Portlet task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19243) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Portlet]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19243?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-19243:
-------------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Portlet]
> ------------------------------------------------------
>
> Key: JBIDE-19243
> URL: https://issues.jboss.org/browse/JBIDE-19243
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: portal-gatein
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Portlet]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Portlet task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18177:
------------------------------------------------
{quote}Open page > select "Change to HTML5" page is opened and immediately Eclipse is restarted, I meant opening of page before restarting Eclipse makes no sense because improper rendering engine would be used and user is not able to see results because Eclipse is restarting{quote}
Yes, but user will see the page opened with requred wisual part after restart. That's why it was implemented like this.
{quote}I'm testing it with index.html from JBoss Central > Mobile Applications > kitchensink-html5-mobile project and Visual part of VPE is completely blank{quote}
Will take a look tomorrow.
> Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18177
> URL: https://issues.jboss.org/browse/JBIDE-18177
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Labels: f2f2014, new_and_noteworthy, requirements
> Fix For: 4.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner)
> if he says okey - we set a flag somewhere to not start xulrunner.
> user restart - user is happy.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-18177 at 2/12/15 9:43 AM:
--------------------------------------------------------------
# I'm testing it with index.html from JBoss Central > Mobile Applications > kitchensink-html5-mobile project and Visual part of VPE is completely blank
# Open page > select "Change to HTML5" page is opened and immediately Eclipse is restarted, I meant opening of page before restarting Eclipse makes no sense because improper rendering engine would be used and user is not able to see results because Eclipse is restarting
# I agree checkbox would be better
was (Author: vpakan):
# I'm testing it with index.html from JBoss Central > Mobile Applications > kitchensink-html5-mobile project and Visual part of VPE is completely blank
# Open page > select "Change to HTML5" page is opened and immediately Eclipse is restarted, I meant opening of page before restarting Eclipse makes no sense because inproper rendering engine would be used and user is not able to see results becaus Eclipse is restarting
# I agree checkbox would be better
> Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18177
> URL: https://issues.jboss.org/browse/JBIDE-18177
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Labels: f2f2014, new_and_noteworthy, requirements
> Fix For: 4.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner)
> if he says okey - we set a flag somewhere to not start xulrunner.
> user restart - user is happy.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-18177:
-------------------------------------
# I'm testing it with index.html from JBoss Central > Mobile Applications > kitchensink-html5-mobile project and Visual part of VPE is completely blank
# Open page > select "Change to HTML5" page is opened and immediately Eclipse is restarted, I meant opening of page before restarting Eclipse makes no sense because inproper rendering engine would be used and user is not able to see results becaus Eclipse is restarting
# I agree checkbox would be better
> Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18177
> URL: https://issues.jboss.org/browse/JBIDE-18177
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Labels: f2f2014, new_and_noteworthy, requirements
> Fix For: 4.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner)
> if he says okey - we set a flag somewhere to not start xulrunner.
> user restart - user is happy.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18177:
------------------------------------------------
{quote}Open in Default Browser works fine either HTML Preview is rendering web page properly{quote}
So please try to open index.html from kitchensink-html5-mobile project. Smth should be rendered, but not correctly.
{quote}When support is changed page is opened and then Eclipse is restarted it would look better if page won't be opened before Eclipse is restarted. Page should be opened after restart.{quote}
Don't catch this point
{quote}VPE Preference page should contain also third Radio Box with choice: "Always ask" otherwise user will never be able to get dialog asking to choose between JSF and HTML5 support once he will check check box "Do not show this message again".{quote}
Not radio button, but checkobox. Good update, but for 4.2.3 since we will have no repsins.
> Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18177
> URL: https://issues.jboss.org/browse/JBIDE-18177
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Labels: f2f2014, new_and_noteworthy, requirements
> Fix For: 4.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner)
> if he says okey - we set a flag somewhere to not start xulrunner.
> user restart - user is happy.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19226) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19226?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19226:
------------------------------------
{code}
forge ... OK
hibernate ... OK
{code}
Still waiting on aerogear, openshift, server. And arquillian, birt, freemarker, portlet, if there are changes in those.
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch
> --------------------------------------------
>
> Key: JBIDE-19226
> URL: https://issues.jboss.org/browse/JBIDE-19226
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3346
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months