[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-19590:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.5.x
>
> Attachments: hibernate-psf-import.mp4, oomph-installer-hibernate-codebase.png
>
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22346) NullPointerException in JaxrsResourceMethodValidatorDelegate.resolveAnnotationParamSourceRange
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22346?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22346:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> NullPointerException in JaxrsResourceMethodValidatorDelegate.resolveAnnotationParamSourceRange
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-22346
> URL: https://issues.jboss.org/browse/JBIDE-22346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Xavier Coulon
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message:
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.resolveAnnotationParamSourceRange(JaxrsResourceMethodValidatorDelegate.java:445)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.validateNoUnboundPathAnnotationTemplateParameters(JaxrsResourceMethodValidatorDelegate.java:291)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.internalValidate(JaxrsResourceMethodValidatorDelegate.java:87)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.internalValidate(JaxrsResourceMethodValidatorDelegate.java:1)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:69)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceValidatorDelegate.internalValidate(JaxrsResourceValidatorDelegate.java:67)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceValidatorDelegate.internalValidate(JaxrsResourceValidatorDelegate.java:1)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:69)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:1)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:490)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:422)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:498)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697)
> {noformat}
> Bundles:
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 |
> | org.jboss.tools.ws.jaxrs.ui | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57265dcae4b0a54983...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22950) ClassNotFoundException below ExternalProcessLauncher.launch (thrown in BundleLoader.findClassInternal)
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22950?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22950:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> ClassNotFoundException below ExternalProcessLauncher.launch (thrown in BundleLoader.findClassInternal)
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22950
> URL: https://issues.jboss.org/browse/JBIDE-22950
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Error logged from Debug UI:
> {noformat}
> java.lang.ClassNotFoundException: org.jboss.ide.eclipse.freemarker.linetracker.ConsoleLineTracker cannot be found by org.jboss.ide.eclipse.freemarker_1.5.101.v20160718-0829
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.getLineTrackers(ProcessConsoleManager.java:281)
> at org.eclipse.debug.internal.ui.views.console.ConsoleLineNotifier.connect(ConsoleLineNotifier.java:54)
> at org.eclipse.ui.internal.console.ConsolePatternMatcher.addPatternMatchListener(ConsolePatternMatcher.java:232)
> at org.eclipse.ui.console.TextConsole.addPatternMatchListener(TextConsole.java:409)
> at org.eclipse.debug.internal.ui.views.console.ProcessConsole.<init>(ProcessConsole.java:228)
> at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.launchChanged(ProcessConsoleManager.java:149)
> at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:453)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433)
> at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043)
> at org.eclipse.debug.core.Launch.fireChanged(Launch.java:393)
> at org.eclipse.debug.core.Launch.addProcess(Launch.java:355)
> at org.eclipse.debug.core.model.RuntimeProcess.<init>(RuntimeProcess.java:126)
> at org.eclipse.debug.core.DebugPlugin.newProcess(DebugPlugin.java:787)
> at org.eclipse.jdt.launching.AbstractVMRunner.newProcess(AbstractVMRunner.java:170)
> at org.eclipse.jdt.internal.launching.StandardVMRunner.run(StandardVMRunner.java:424)
> at org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:102)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.jboss.tools.browsersim.eclipse.launcher.ExternalProcessLauncher.launch(ExternalProcessLauncher.java:250)
> at org.jboss.tools.browsersim.eclipse.launcher.ExternalProcessLauncher.launchAsExternalProcess(ExternalProcessLauncher.java:81)
> at org.jboss.tools.browsersim.eclipse.launcher.BrowserSimLauncher.launchBrowserSim(BrowserSimLauncher.java:70)
> at org.jboss.tools.browsersim.eclipse.actions.RunBrowserSimAction.run(RunBrowserSimAction.java:29)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:247)
> at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:228)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$5(ActionContributionItem.java:436)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> {noformat}
> Bundles:
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.core | 3.10.100.v20160419-1720 | 3.10.100.v20160419-1720 |
> | org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 |
> | org.eclipse.jdt.launching | 3.8.100.v20160505-0636 | 3.8.100.v20160505-0636 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.osgi | 3.11.0.v20160603-1336 | 3.11.0.v20160603-1336 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 |
> | org.eclipse.ui.console | 3.6.200.v20160518-1858 | 3.6.200.v20160518-1858 |
> | org.jboss.tools.browsersim.eclipse | 3.8.1.v20160610-2137 | 3.8.1.v20160610-2137 |
> Operating Systems:
> | MacOSX | 10.11.5 | 10.11.5 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/579206b7e4b0024f7d...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-21771) Simplest java project is imported sometimes as JDT, sometimes not.
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21771?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-21771:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Simplest java project is imported sometimes as JDT, sometimes not.
> ------------------------------------------------------------------
>
> Key: JBIDE-21771
> URL: https://issues.jboss.org/browse/JBIDE-21771
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.1.CR1
> Reporter: Radim Hopp
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.5.x
>
> Attachments: PlainJavaProject
>
>
> Importing simplest java project (in attachment) gets sometimes imported as "Java, JDT" and sometimes only as "Java". I am not able to provide exact steps to reproduce, as it seems to do that randomly.
> Looking at http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles/org.eclips..., project should be detected as JDT, in case ".classpath" is found in the project. Couldn't be the issue the order of executing configurators? Like when Java configurator is called first, it creates .classpath and then JDT configurator is called and it sees the .classpath file. When the order is opposite, JDT is not configured, because .classpath is not there yet?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22951) HIDDEN below ExternalProcessLauncher.launch (thrown in DOMParser.parse)
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22951?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22951:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> HIDDEN below ExternalProcessLauncher.launch (thrown in DOMParser.parse)
> -----------------------------------------------------------------------
>
> Key: JBIDE-22951
> URL: https://issues.jboss.org/browse/JBIDE-22951
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Unable to restore classpath entry.
> {noformat}
> HIDDEN: FWK005 parse may not be called while parsing.
> at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(null:-1)
> at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(null:-1)
> at org.eclipse.jdt.launching.JavaRuntime.newRuntimeClasspathEntry(JavaRuntime.java:724)
> at org.eclipse.jdt.launching.StandardClasspathProvider.recoverRuntimePath(StandardClasspathProvider.java:102)
> at org.eclipse.jdt.launching.StandardClasspathProvider.computeUnresolvedClasspath(StandardClasspathProvider.java:66)
> at org.eclipse.jdt.launching.JavaRuntime.computeUnresolvedRuntimeClasspath(JavaRuntime.java:1246)
> at org.eclipse.jdt.launching.AbstractJavaLaunchConfigurationDelegate.getBootpathExt(AbstractJavaLaunchConfigurationDelegate.java:296)
> at org.eclipse.jdt.launching.AbstractJavaLaunchConfigurationDelegate.getVMSpecificAttributesMap(AbstractJavaLaunchConfigurationDelegate.java:563)
> at org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:69)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.jboss.tools.browsersim.eclipse.launcher.ExternalProcessLauncher.launch(ExternalProcessLauncher.java:250)
> at org.jboss.tools.browsersim.eclipse.launcher.ExternalProcessLauncher.launchAsExternalProcess(ExternalProcessLauncher.java:81)
> at org.jboss.tools.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:177)
> at org.jboss.tools.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:129)
> at org.jboss.tools.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationDelegate.launch(CordovaSimLaunchConfigurationDelegate.java:25)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.debug.core | 3.10.0.v20150303-1130 | 3.10.100.v20160419-1720 |
> | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.200.v20160518-1858 |
> | org.eclipse.jdt.launching | 3.8.0.v20150527-0946 | 3.8.100.v20160505-0636 |
> | org.jboss.tools.browsersim.eclipse | 3.7.1.Final-v20160331-0511-B89 | 3.8.0.Final-v20160609-2253-B3 |
> | org.jboss.tools.cordovasim.eclipse | 3.7.1.Final-v20160331-0435-B86 | 3.8.0.Final-v20160609-2302-B3 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/572f2d5be4b0a54983...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22285) JavaModelException below FileSet.checkType (thrown in JavaElement.openWhenClosed)
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22285?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22285:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> JavaModelException below FileSet.checkType (thrown in JavaElement.openWhenClosed)
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22285
> URL: https://issues.jboss.org/browse/JBIDE-22285
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> org.eclipse.jdt.core.JavaModelException: HIDDEN
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:556)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:590)
> at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:287)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
> at org.eclipse.jdt.internal.core.BinaryType.isAnnotation(BinaryType.java:738)
> at org.jboss.tools.batch.internal.core.scanner.FileSet.checkType(FileSet.java:81)
> at org.jboss.tools.batch.internal.core.scanner.FileSet.add(FileSet.java:51)
> at org.jboss.tools.batch.internal.core.impl.BatchBuilder.buildJars(BatchBuilder.java:226)
> at org.jboss.tools.batch.internal.core.impl.BatchBuilder.build(BatchBuilder.java:140)
> at org.jboss.tools.batch.internal.core.impl.BatchBuilder.<init>(BatchBuilder.java:73)
> at org.jboss.tools.batch.internal.core.impl.BatchProject.build(BatchProject.java:341)
> at org.jboss.tools.jst.web.kb.internal.AbstractKbProjectExtension.load(AbstractKbProjectExtension.java:163)
> at org.jboss.tools.jst.web.kb.internal.AbstractKbProjectExtension.resolveStorage(AbstractKbProjectExtension.java:154)
> at org.jboss.tools.jst.web.kb.internal.AbstractKbProjectExtension.resolve(AbstractKbProjectExtension.java:148)
> at org.jboss.tools.batch.internal.core.impl.BatchProject$BatchBuildJob.runInWorkspace(BatchProject.java:120)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> {noformat}
> Bundles:
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.10.1.v20150725-1910 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.11.2.v20160212-1500 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 |
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 |
> | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 |
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 |
> | org.jboss.tools.batch.core | 1.7.1.Final-v20160330-2256-B84 | 1.7.1.Final-v20160330-2256-B84 |
> | org.jboss.tools.common | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 |
> | org.jboss.tools.common.model | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 |
> | org.jboss.tools.jst.web | 3.7.1.Final-v20160331-0256-B96 | 3.7.1.Final-v20160331-0256-B96 |
> | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.7.1.Final-v20160331-0256-B96 |
> Operating Systems:
> | Linux | 3.13.0 | 4.4.7.fc23 |
> | MacOSX | 10.11.4 | 10.11.4 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57176467e4b032f683...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months