September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4041) cygwin installer fails to start with EBUSY error in install.log

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4041?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4041. ----------------------------- No longer replicable on build 130, so the fix seems to have worked. Closing. > cygwin installer fails to start with EBUSY error in install.log > --------------------------------------------------------------- > > Key: JBDS-4041 > URL: https://issues.jboss.org/browse/JBDS-4041 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > This easy to replicate when Virtualbox and OpenJDK detected. In this case installer starts cygwin.exe right after download without additional delay related to waiting for other components to install. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install

by Václav Kadlčík (JIRA)

[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ] Václav Kadlčík commented on JBDS-3981: -------------------------------------- Hi Nick, thanks to the pointer to the SPEC file. When you build the devstudio.rpm, do you produce its src.rpm as well? If yes, can you upload it next to the devstudio.rpm itself? Or, even better, can point me to the corresponding rpmbuild directory so I could find all the data myself? Why am I asking? I'd like to put devstudio through the same basic tests that every RHEL RPM passes (enforced by Errata Tool but we are going to skip the tool completely). I may not succeed (at least within reasonable time), because the tests seem to be hardcoded around Brew builds, but I'd like to try anyway... > Build a new feature that omits features available from RPM install > ------------------------------------------------------------------ > > Key: JBDS-3981 > URL: https://issues.jboss.org/browse/JBDS-3981 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.GA > > Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, rheclipse_20160901_0937.log.txt, rheclipse_20160901_0950.log.txt, rheclipse_20160901_1720.log.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png > > > What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4026) Bundled binaries sha256 is not verified after download in online installer

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4026?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4026. ----------------------------- All the mentioned downloads failed when I tampered with their expected sha, so the checks are working. Closing. > Bundled binaries sha256 is not verified after download in online installer > -------------------------------------------------------------------------- > > Key: JBDS-4026 > URL: https://issues.jboss.org/browse/JBDS-4026 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.1.0.GA > > > sha256 checksum verification was not implemented for 'bundled' binaries, that affects: > # OpenJDK > # DevStudio > # CDK > # Virtualbox.box -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23028) Update Hibernate Tools dependency to 5.2.0.Beta1

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23028?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23028. ------------------------------------ verified in Devstudio 10.1.0.GA-v20160901-1658-B5921 > Update Hibernate Tools dependency to 5.2.0.Beta1 > ------------------------------------------------ > > Key: JBIDE-23028 > URL: https://issues.jboss.org/browse/JBIDE-23028 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.AM3 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.1.Final > > > This also implies an update of the Hibernate Core dependency to 5.2.2.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22993) Update RedDeer in TP for JBT 4.4.1.Final

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22993?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-22993. ------------------------------------ verified. RedDeer 1.1.0.Final is in 4.60.1.Final TP > Update RedDeer in TP for JBT 4.4.1.Final > ---------------------------------------- > > Key: JBIDE-22993 > URL: https://issues.jboss.org/browse/JBIDE-22993 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > For JBoss Tools 4.4.1.Final, we would like to include RedDeer 1.1.0.Final which will be released on Tuesday, August 16 in the TP. > I will update this JIRA once the bits are ready. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23094) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata when image is in the Docker daemon

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23094?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23094: ------------------------------------ In order to reproduce the image must be pulled before in the docker daemon so this is the main difference with JBIDE-22916. I'm able to reproduce on my side. > Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata when image is in the Docker daemon > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23094 > URL: https://issues.jboss.org/browse/JBIDE-23094 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Fix For: 4.4.2.AM1 > > > ASSERT: Have an OpenShift 3 connection with a project. > ASSERT: Have a docker connection in docker explorer. > EXEC: Select a context menu item Deploy Docker Image in context menu of a project. > EXEC: Browse docker image name e.g. docker.io/openshift/hello-openshift (the image must be available in the Docker daemon). > EXEC: Proceed to next wizard page(s). > RESULT: There are no prefetched and processed metadata of the image. > EXPECTED RESULT: Metadata are correctly processed and shown. > Description -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23067) Clean up unused local variable in org.jboss.tools.hibernate.runtime.v_5_1.internal.ServiceImpl.newSchemaExport()

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23067?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23067. ------------------------------------ verified in git > Clean up unused local variable in org.jboss.tools.hibernate.runtime.v_5_1.internal.ServiceImpl.newSchemaExport() > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23067 > URL: https://issues.jboss.org/browse/JBIDE-23067 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.AM3 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22997) Generating mapping xml file fails for hb >= 5.0

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22997?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-22997. ------------------------------------ verified in Devstudio 10.1.0.GA-v20160901-1658-B5921 > Generating mapping xml file fails for hb >= 5.0 > ----------------------------------------------- > > Key: JBIDE-22997 > URL: https://issues.jboss.org/browse/JBIDE-22997 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.1.AM2 > Reporter: Rastislav Wagner > Assignee: Koen Aers > Fix For: 4.4.1.Final > > Attachments: java-hb-mapping-prj.zip > > > Im positive that this worked before (see Steps to reproduce). I think this might be caused by JBIDE-21769 > When I create JPA project with HB4.3, generating xml mapping file works. For >= 5.0 it does not > Exception in log: > {code} > org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment] > at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:264) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:228) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:207) > at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:51) > at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:94) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:207) > at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.handleTypes(MetadataBuildingProcess.java:352) > at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:111) > at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.build(MetadataBuildingProcess.java:83) > at org.hibernate.boot.internal.MetadataBuilderImpl.build(MetadataBuilderImpl.java:418) > at org.hibernate.boot.internal.MetadataBuilderImpl.build(MetadataBuilderImpl.java:87) > at org.hibernate.boot.MetadataSources.buildMetadata(MetadataSources.java:183) > at org.hibernate.tool.util.MetadataHelper.buildFromMetadataSources(MetadataHelper.java:49) > at org.hibernate.tool.util.MetadataHelper.getMetadata(MetadataHelper.java:21) > at org.jboss.tools.hibernate.runtime.v_5_2.internal.ConfigurationFacadeImpl.getMetadata(ConfigurationFacadeImpl.java:168) > at org.jboss.tools.hibernate.runtime.v_5_2.internal.ConfigurationFacadeImpl.buildMappings(ConfigurationFacadeImpl.java:106) > at org.jboss.tools.hibernate.runtime.v_5_2.internal.ConfigurationFacadeImpl.createMappings(ConfigurationFacadeImpl.java:100) > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.createConfiguration(ConfigurationActor.java:171) > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.createConfigurations(ConfigurationActor.java:120) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.createConfigurations(NewHibernateMappingFileWizard.java:559) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.getPlaces2Gen(NewHibernateMappingFileWizard.java:316) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.handlePageChanging(NewHibernateMappingFileWizard.java:172) > at org.eclipse.jface.wizard.WizardDialog$7.run(WizardDialog.java:1540) > 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.wizard.WizardDialog.firePageChanging(WizardDialog.java:1537) > at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:890) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1177) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:876) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:419) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:353) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:155) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) > at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set > at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100) > at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54) > at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137) > at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35) > at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:88) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:254) > ... 86 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23074) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Integration Tests]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23074?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23074: --------------------------------------- PR to update pom to 4.4.1.Final-SNAPSHOT created: https://github.com/jbosstools/jbosstools-integration-tests/pull/1602 > For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Integration Tests] > ------------------------------------------------------------------------------ > > Key: JBIDE-23074 > URL: https://issues.jboss.org/browse/JBIDE-23074 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Friendly Jira Robot > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.4.1.Final > > > For JBIDE 4.4.1.Final [Integration Tests]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA > [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch: > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.4.1.x > git push origin jbosstools-4.4.1.x > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too. > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 5. Close (do not resolve) this JIRA when done. > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4042) Div element of error message is not wrapped

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBDS-4042: ----------------------------------- Summary: Div element of error message is not wrapped Key: JBDS-4042 URL: https://issues.jboss.org/browse/JBDS-4042 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 1.1.0.GA Environment: Win 10 x86_64, devsuite-1.1.0-GA-20160902-131-bundle-installer.exe Reporter: Ondrej Dockal Assignee: Denis Golovin Attachments: platform_installer.PNG Error message used when user name contains space in his name is not wrapped. See attachment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 September 2016