November 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18459) MacBook Pro Retina Display Font

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18459?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18459: ------------------------------ Fix Version/s: 4.2.x 4.3.x (was: 4.3.0.Alpha1) (was: 4.2.1.Final) > MacBook Pro Retina Display Font > ------------------------------- > > Key: JBIDE-18459 > URL: https://issues.jboss.org/browse/JBIDE-18459 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, central, forge, jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.CR1 > Environment: MacBook Pro 15" mid-2014 Retina set at "Best for Display" (default) > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 4.2.x, 4.3.x > > Attachments: Screenshot 2014-09-30 13.58.59.png, Screenshot 2014-09-30 14.04.34.png, Screenshot 2014-10-03 16.44.07.png > > > Some fonts are "fuzzy". > Screenshot 1 > - under "JBoss Buzz" > - under "Start from a sample" and Portal Applications > - the open cheatsheet.xml (AngularJS Forge) > Screenshot 2 > - jQuery Mobile and Ionic Palettes -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18414) Forge 'New Project' wizard - 'From Archetype' option broken

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18414?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18414: ------------------------------ Fix Version/s: 4.2.x (was: 4.2.1.Final) > Forge 'New Project' wizard - 'From Archetype' option broken > ----------------------------------------------------------- > > Key: JBIDE-18414 > URL: https://issues.jboss.org/browse/JBIDE-18414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Environment: OS X > Reporter: Michelle Murray > Fix For: 4.2.x, 4.3.x > > > Forge 2 New Project wizard fails for project type 'From Archetype' > * Ctrl+4 > * New Project > * Project name: blah > * Project type: From Archetype > * Archetype Group Id: org.jboss.aerogear.archetypes > * Archetype Artifact Id: jboss-html5-mobile-archetype > * Archetype Version: 7.1.3.Final > * Archetype Repository: http://repo1.maven.org/maven2/ > or > * Archetype Group Id: org.jboss.archetype.wfk > * Archetype Artifact Id: jboss-html5-mobile-archetype > * Archetype Version: 2.6.0.Final > * Archetype Repository: http://repository.jboss.org/nexus/content/groups/public > Wizard fails with message in Error Log: > {noformat} > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.RuntimeException: org.codehaus.plexus.util.xml.pull.XmlPullParserException: expected START_TAG or END_TAG not TEXT (position: TEXT seen ... version of the JBoss EAP components we want to use -->\n <v... @50:11) ) > at org.eclipse.swt.SWT.error(SWT.java:4441) > at org.eclipse.swt.SWT.error(SWT.java:4356) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:209) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:156) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:4721) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardHelper.onFinish(ForgeWizardHelper.java:56) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:115) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > Caused by: java.lang.RuntimeException: org.codehaus.plexus.util.xml.pull.XmlPullParserException: expected START_TAG or END_TAG not TEXT (position: TEXT seen ... version of the JBoss EAP components we want to use -->\n <v... @50:11) > at org.jboss.forge.addon.maven.resources.MavenModelResourceImpl.initialize(MavenModelResourceImpl.java:120) > at org.jboss.forge.addon.maven.resources.MavenModelResourceImpl.getCurrentModel(MavenModelResourceImpl.java:96) > at org.jboss.forge.addon.maven.projects.MavenFacetImpl.getModel(MavenFacetImpl.java:124) > at sun.reflect.GeneratedMethodAccessor154.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103) > at org.jboss.forge.addon.maven.projects.MavenFacetImpl_$$_javassist_55122075-0c11-493f-a1ca-83e805ea5320.getModel(MavenFacetImpl_$$_javassist_55122075-0c11-493f-a1ca-83e805ea5320.java) > at org.jboss.forge.addon.maven.projects.facets.MavenMetadataFacet.getProjectName(MavenMetadataFacet.java:50) > 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:606) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103) > at org.jboss.forge.addon.maven.projects.facets.MavenMetadataFacet_$$_javassist_2cf3fcd2-cfbc-4910-bfb8-de40dd12cabf.getProjectName(MavenMetadataFacet_$$_javassist_2cf3fcd2-cfbc-4910-bfb8-de40dd12cabf.java) > 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:606) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) > at org.jboss.forge.addon.facets.Facet_$$_javassist_718e47d0-0ab5-4306-98e5-0a8169186093.getProjectName(Facet_$$_javassist_718e47d0-0ab5-4306-98e5-0a8169186093.java) > at org.jboss.tools.forge.ui.internal.ext.importer.ImportEclipseProjectListener.doImport(ImportEclipseProjectListener.java:48) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardHelper.importNewProjects(ForgeWizardHelper.java:102) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardHelper.access$0(ForgeWizardHelper.java:100) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardHelper$1.run(ForgeWizardHelper.java:59) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3983) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:175) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:390) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1059) > at org.jboss.tools.forge.ui.internal.ext.dialog.ForgeCommandDialog.run(ForgeCommandDialog.java:56) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard.performFinish(ForgeWizard.java:97) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard.performFinish(ForgeWizard.java:87) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > 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:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:205) > at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:102) > at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:232) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:322) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:312) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents$6.mouseUp(QuickAccessContents.java:461) > 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:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > 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:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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) > Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: expected START_TAG or END_TAG not TEXT (position: TEXT seen ... version of the JBoss EAP components we want to use -->\n <v... @50:11) > at org.codehaus.plexus.util.xml.pull.MXParser.nextTag(MXParser.java:1121) > at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2178) > at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:3807) > at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:557) > at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:571) > at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:600) > at org.jboss.forge.addon.maven.resources.MavenModelResourceImpl.initialize(MavenModelResourceImpl.java:115) > ... 90 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18415) Forge New Project wizard - no Archetype catalogues listed

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18415?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18415: ------------------------------ Fix Version/s: 4.2.x 4.3.x (was: 4.3.0.Alpha1) (was: 4.2.1.Final) > Forge New Project wizard - no Archetype catalogues listed > --------------------------------------------------------- > > Key: JBIDE-18415 > URL: https://issues.jboss.org/browse/JBIDE-18415 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Michelle Murray > Assignee: George Gastaldi > Fix For: 4.2.x, 4.3.x > > > Forge 2 New Project wizard lists no catalogs for 'From Archetype Catalog' project option. > * Ctrl+4 > * New Project > * Project name: blah > * Project type: From Archetype Catalog >> no options for Catalog or Archetype > Could this list be populated by Preferences > Maven > Archetypes > Archetype Catalog Table? And have a link in the wizard to this preference page for users to quickly add another catalog? (Like the OpenShift wizard has a link to SSH Preferences for adding private key to IDE in middle of wizard.) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18240) Show in Forge Console should ask to start forge if forge is not started

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18240?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18240: ------------------------------ Fix Version/s: 4.2.x 4.3.x (was: 4.3.0.Alpha1) (was: 4.2.1.Final) > Show in Forge Console should ask to start forge if forge is not started > ----------------------------------------------------------------------- > > Key: JBIDE-18240 > URL: https://issues.jboss.org/browse/JBIDE-18240 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Fix For: 4.2.x, 4.3.x > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17683) When running using Cmd-4 in Eclipse, log the actual forge commands used to an Eclipse console

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17683?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17683: ------------------------------ Fix Version/s: 4.2.x 4.3.x (was: 4.3.0.Alpha1) (was: 4.2.1.Final) > When running using Cmd-4 in Eclipse, log the actual forge commands used to an Eclipse console > --------------------------------------------------------------------------------------------- > > Key: JBIDE-17683 > URL: https://issues.jboss.org/browse/JBIDE-17683 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Pete Muir > Assignee: George Gastaldi > Fix For: 4.2.x, 4.3.x > > > It would be great to log all Forge commands that Cmd-4 executes to an eclipse console > Allow this log to be exported to a .fsh file -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12532) Open command doesn't open URLs in JBoss Tools

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12532?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-12532: ------------------------------ Fix Version/s: 4.2.x (was: 4.2.1.Final) > Open command doesn't open URLs in JBoss Tools > --------------------------------------------- > > Key: JBIDE-12532 > URL: https://issues.jboss.org/browse/JBIDE-12532 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 3.3.1.Final > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.2.x, 4.3.x > > > As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. > To reproduce, type the following in the Forge console: > {code} > open http://forge.jboss.org > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-557) Servers How To: Deploy Apps to Local Servers from the IDE

by Aakanksha Singh (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-557?page=com.atlassian.jira.plug... ] Aakanksha Singh commented on TOOLSDOC-557: ------------------------------------------ Supriya's feedback incorporated. Section on Server Adapter removed from the Article > Servers How To: Deploy Apps to Local Servers from the IDE > --------------------------------------------------------- > > Key: TOOLSDOC-557 > URL: https://issues.jboss.org/browse/TOOLSDOC-557 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Reporter: Michelle Murray > Assignee: Aakanksha Singh > Fix For: 4.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-557) Servers How To: Deploy Apps to Local Servers from the IDE

by Aakanksha Singh (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-557?page=com.atlassian.jira.plug... ] Aakanksha Singh commented on TOOLSDOC-557: ------------------------------------------ Submitting for Michelle's peer-review > Servers How To: Deploy Apps to Local Servers from the IDE > --------------------------------------------------------- > > Key: TOOLSDOC-557 > URL: https://issues.jboss.org/browse/TOOLSDOC-557 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Reporter: Michelle Murray > Assignee: Aakanksha Singh > Fix For: 4.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on JBDS-3199: ---------------------------------------- [~manaRH] I understand that. It's related to < archetypeExpressionReplaceValues/> at https://github.com/jboss-developer/jboss-wfk-archetypes/blob/2.7.x-develo.... We should add "Kitchensink" and "kitchensink" as expressions to be replaced. If you have any issues or doubts fixing it, you can forward that to me since i'm kind responsible for that also. Thanks. > Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3199 > URL: https://issues.jboss.org/browse/JBDS-3199 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, upstream > Affects Versions: 8.0.0.GA > Reporter: Len DiMaggio > Assignee: Fred Bricon > > These "kitchensink" strings are retained: > grep -ir kitchen * > main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source> > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS" > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true" > test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS" > test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source> -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-556) MobileDev How To: Create Your First Mobile Web App

by Aakanksha Singh (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-556?page=com.atlassian.jira.plug... ] Aakanksha Singh commented on TOOLSDOC-556: ------------------------------------------ Supriya feedbacks comments incorporated. Awaiting Michelle's peer-review feedback > MobileDev How To: Create Your First Mobile Web App > -------------------------------------------------- > > Key: TOOLSDOC-556 > URL: https://issues.jboss.org/browse/TOOLSDOC-556 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Reporter: Michelle Murray > Assignee: Aakanksha Singh > Fix For: 4.2.0.Final > > > Instructions to cover in this How To: > 1. Create a HTML5 Project > 2. Build and Deploy the Application > 3. View the Application with BrowserSim > 4. Enable LiveReload for BrowserSim > 5. Change the Application -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2014