[JBoss JIRA] (JBIDE-17732) javaee7 samples require groovy compiler plugin
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17732?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17732:
----------------------------------------
Sprint: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015)
> javaee7 samples require groovy compiler plugin
> ----------------------------------------------
>
> Key: JBIDE-17732
> URL: https://issues.jboss.org/browse/JBIDE-17732
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Reporter: Xavier Coulon
> Assignee: Max Rydahl Andersen
> Fix For: 4.3.0.Beta2
>
>
> Java EE7 samples (https://github.com/javaee-samples/javaee7-samples/) require the Eclipse Groovy Compiler in order to be imported without any error.
> We should see
> - if the goovy compiler has been released for Luna
> - document how to import the samples in Eclipse in the README.md file on github, so that users know how to import and get started with the samples on Eclipse / JBoss Tools.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18846?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18846:
----------------------------------------
Sprint: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015)
> create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18846
> URL: https://issues.jboss.org/browse/JBIDE-18846
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, website
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as:
> builds (nightly, staging, dev, stable)
> updates (nightly, staging, dev, stable)
> Jenkins jobs
> discovery sites (nightly, staging, dev, stable)
> target platforms
> etc.
> And for each component, we can list:
> build
> update
> Jenkins job
> etc.
> The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html
> Unsure whether generated HTML (via script) or simple .adoc is better for this.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19451) LiveReload stops working after a few reloads with asciidoc.js preview
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19451?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19451:
----------------------------------------
Sprint: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015)
> LiveReload stops working after a few reloads with asciidoc.js preview
> ---------------------------------------------------------------------
>
> Key: JBIDE-19451
> URL: https://issues.jboss.org/browse/JBIDE-19451
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload, upstream
> Affects Versions: 4.2.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: 4.3.0.Beta2
>
>
> I have not found a direct pattern yet, but during eclipsecon demos and talks livereload just stopped working after a few reloads. Was using html5 preview while doing so in case that affects something.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-16540) IStructuredDocumentRegion management failed when generating Page from Palette
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16540?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16540:
----------------------------------------
Sprint: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015)
> IStructuredDocumentRegion management failed when generating Page from Palette
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16540
> URL: https://issues.jboss.org/browse/JBIDE-16540
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Alpha2
> Reporter: Lucia Jelinkova
> Assignee: Daniel Azarov
> Priority: Minor
> Fix For: 4.3.0.Beta2
>
> Attachments: .log, screencast.ogv
>
>
> When creating a Page on html page, the following exception is written to error log:
> {code}org.eclipse.wst.xml.core.internal.document.StructuredDocumentRegionManagementException: IStructuredDocumentRegion management failed.
> at org.eclipse.wst.xml.core.internal.document.XMLModelParser.removeStructuredDocumentRegion(XMLModelParser.java:2265)
> at org.eclipse.wst.xml.core.internal.document.XMLModelParser.removeStructuredDocumentRegion(XMLModelParser.java:2288)
> at org.eclipse.wst.xml.core.internal.document.XMLModelParser.replaceStructuredDocumentRegions(XMLModelParser.java:2339)
> at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.nodesReplaced(DOMModelImpl.java:737)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:600)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1198)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1979)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.writeBuffer(MobilePaletteInsertHelper.java:124)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertNode(MobilePaletteInsertHelper.java:150)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertJsCss(MobilePaletteInsertHelper.java:381)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.modify(MobilePaletteInsertHelper.java:103)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.isMobile(MobilePaletteInsertHelper.java:86)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.JSPPaletteInsertHelper.modify(JSPPaletteInsertHelper.java:45)
> at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:121)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.FileDropCommand.run(FileDropCommand.java:67)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2333)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2315)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:133)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteDropCommand.execute(PaletteDropCommand.java:117)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:94)
> at org.jboss.tools.jst.web.ui.palette.html.jquery.wizard.NewJQueryWidgetWizard.doPerformFinish(NewJQueryWidgetWizard.java:106)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:78)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:465)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:373)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1055)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:82)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:851)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:437)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:633)
> 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:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPTextEditor$3.run(JSPTextEditor.java:740)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPTextEditor.runDropCommand(JSPTextEditor.java:759)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.runDropCommand(JSPMultiPageEditor.java:864)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> at org.jboss.tools.common.model.ui.views.palette.PaletteCreator.dropIntoEditor(PaletteCreator.java:187)
> at org.jboss.tools.common.model.ui.views.palette.PaletteCreator.insertIntoEditor(PaletteCreator.java:141)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.PalettePageImpl.insertIntoEditor(PalettePageImpl.java:128)
> at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:72)
> at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:67)
> at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:393)
> at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206)
> at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175)
> at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140)
> at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27)
> at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506)
> at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179)
> at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466)
> at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$GTKToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:142)
> at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200)
> at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574)
> at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301)
> at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380)
> at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548)
> 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:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3191:
--------------------------------------
Sprint: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015)
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Fred Bricon
> Fix For: 9.0.0.CR1
>
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associate.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19192) provide option for disable html preview
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19192?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19192:
----------------------------------------
Sprint: Sprint #1 April 2015, Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #1 April 2015, Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015)
> provide option for disable html preview
> ---------------------------------------
>
> Key: JBIDE-19192
> URL: https://issues.jboss.org/browse/JBIDE-19192
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.2.Final
> Environment: win8.1 64 eclipse luna 4.4.0 jboss 4.2.2
> Reporter: jim harber
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.3.x
>
> Attachments: Clipboard01.png
>
>
> when i use tween.js to create a html page,i create an array,here is the problem:
> var eles = [];
> //push such as 500 elements into eles;
> ..
> then i need call a function to update every element in eles,when these two line:
> requestAnimationFrame(animate);
> TWEEN.update();
> already in the function,i can't see a change in preview and it makes eclipse shutdown,so i put this two line when i finish the other codes,this time preview become normal.
> every time when i type to for(var i=0;i<eles.length;i) eclipse gets stuck. so i wonder is thers any chance i can shutdown living view,i checked preferences panel i didn't find anything.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19259) JSF or HTML5 support choosing issues
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19259?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19259:
----------------------------------------
Sprint: Sprint #1 April 2015, Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #1 April 2015, Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015)
> JSF or HTML5 support choosing issues
> ------------------------------------
>
> Key: JBIDE-19259
> URL: https://issues.jboss.org/browse/JBIDE-19259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.3.0.Alpha1
> Environment: Fedora 20 GNOME 64 bit, Open JDK 7, Alpha2-v20150212-0919-B9496
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Beta2
>
>
> # -GKT2 + xulrunner loaded + JSF support enabled: HTML5 page not rendered - visual part of VPE should contain similar message as in case HTML5 support is enabled for XHTML page informing users about possibility to enable HTML5 suppport-(won't fix)
> # -VPE Preference page should contain checkbox 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"-(fixed)
> # 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
> # -With GTK3 "Visual Editor Browser Engine" group within VPE prefrences page is hidden it would be more user friendly just disable it and add some label why it's disabled?.The same way as selecting of GTK for BrowserSim/CordovaSim works.-(fixed)
> # Confusing scenario #1:
> ## Set HTML5 support
> ## Open .xhtml page and say "Stay with HTML5"
> ## Open .html page
> ## Restart Eclipse
> ## 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.
> # Confusing scenario #2:
> ## Set HTML5 support
> ## Open .xhtml page and say "Stay with HTML5"
> ## Restart Eclipse
> ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed before workspace window appears. This dialog should be displayed once worspace is visible and user actually can see page he is going to open.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months