[JBoss JIRA] (JBIDE-21235) Incorrect updating Runtime Enfironment input in server editor
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21235?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21235:
-----------------------------------------------
[~rob.stryker] please take a look.
> Incorrect updating Runtime Enfironment input in server editor
> -------------------------------------------------------------
>
> Key: JBIDE-21235
> URL: https://issues.jboss.org/browse/JBIDE-21235
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Priority: Minor
>
> 1. Create in preferences several server runtime environments for the same JBoss runtime type.
> 2. Create a server for one of them and open it in the server editor.
> 3. Select another 'Runtime Environment' and save the change.
> 4. Open preferences and add one more new runtime environment for the same runtime type.
> 5. In server editor 'Runtime Environment' returned to the original choice - failure.
> 6. Close/reopen server editor - 'Runtime Environment' shows correct choice saved before.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21285) NPE when opening in editor a server that has no runtime.
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21285?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21285:
-----------------------------------------------
[~rob.stryker] please take a look.
> NPE when opening in editor a server that has no runtime.
> --------------------------------------------------------
>
> Key: JBIDE-21285
> URL: https://issues.jboss.org/browse/JBIDE-21285
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
>
> 1. Create a server. Do not open it in editor yet.
> 2. In preferences, rename its runtime environment.
> As a result, server lost reference to renamed runtime. (related to JBIDE-21199)
> 3. Open context menu and try Open server in editor - NPE:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.getAS7StyleServerTempFolder(LocalDeploymentOptionsController.java:104)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.getTempDeployFolder(LocalDeploymentOptionsController.java:93)
> at org.jboss.tools.as.core.server.controllable.systems.AbstractJBossDeploymentOptionsController.getDeploymentsTemporaryFolder(AbstractJBossDeploymentOptionsController.java:89)
> at org.jboss.ide.eclipse.as.ui.editor.internal.JBossDeploymentOptionsComposite.updateWidgets(JBossDeploymentOptionsComposite.java:465)
> at org.jboss.ide.eclipse.as.ui.editor.internal.JBossDeploymentOptionsComposite.createDefaultComposite(JBossDeploymentOptionsComposite.java:217)
> at org.jboss.ide.eclipse.as.ui.editor.internal.JBossDeploymentOptionsComposite.<init>(JBossDeploymentOptionsComposite.java:98)
> at org.jboss.ide.eclipse.as.ui.editor.internal.StandardDeploymentPageController.createServerDeploymentOptions(StandardDeploymentPageController.java:242)
> at org.jboss.ide.eclipse.as.ui.editor.internal.StandardDeploymentPageController.addDeploymentLocationControls(StandardDeploymentPageController.java:194)
> at org.jboss.ide.eclipse.as.ui.editor.internal.StandardDeploymentPageController.createPartControl(StandardDeploymentPageController.java:144)
> at org.jboss.ide.eclipse.as.ui.editor.DeploymentPage.createPartControl(DeploymentPage.java:138)
> at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:244)
> at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:214)
> at org.eclipse.wst.server.ui.internal.editor.ServerEditor.createPages(ServerEditor.java:247)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:363)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:341)
> at sun.reflect.GeneratedMethodAccessor149.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:898)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:879)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:121)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:345)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:104)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:73)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:55)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:971)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:640)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:99)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4633)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:85)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:494)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:458)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:724)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:396)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1166)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3234)
> at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3149)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3131)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3126)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3090)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3071)
> at org.eclipse.wst.server.ui.internal.ServerUIPlugin.editServer(ServerUIPlugin.java:443)
> at org.eclipse.wst.server.ui.internal.ServerUIPlugin.editServer(ServerUIPlugin.java:426)
> at org.eclipse.wst.server.ui.internal.view.servers.OpenAction.perform(OpenAction.java:36)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.run(AbstractServerAction.java:64)
> at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:229)
> at org.eclipse.ui.navigator.CommonNavigatorManager$2.open(CommonNavigatorManager.java:191)
> at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
> at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:854)
> 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.viewers.StructuredViewer.fireOpen(StructuredViewer.java:851)
> at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1168)
> at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:449)
> at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1275)
> at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278)
> at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21268) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Server]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21268?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-21268.
-------------------------------
Resolution: Done
Branched
> For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Server]
> ----------------------------------------------------
>
> Key: JBIDE-21268
> URL: https://issues.jboss.org/browse/JBIDE-21268
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Server]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), 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.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT).
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta1x
> git push origin jbosstools-4.3.1.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and
> * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 Server 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)
10 years, 4 months
[JBoss JIRA] (JBIDE-21296) failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21296?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21296:
-------------------------------
Labels: testfailure (was: )
> failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
> --------------------------------------------------------------------------
>
> Key: JBIDE-21296
> URL: https://issues.jboss.org/browse/JBIDE-21296
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, seam2
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Labels: testfailure
>
> {code}
> 18:17:13 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
> com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-seam-gen)
> on project org.jboss.tools.seam.core.test: IO Error
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 18:17:13 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 18:17:13 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 18:17:13 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 18:17:13 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 18:17:13 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 18:17:13 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:17:13 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 18:17:13 at java.lang.reflect.Method.invoke(Method.java:497)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 18:17:13 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:260)
> 18:17:13 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:17:13 ... 19 more
> 18:17:13 Caused by: java.io.EOFException
> 18:17:13 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335)
> 18:17:13 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)
> 18:17:13 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
> 18:17:13 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
> 18:17:13 at com.googlecode.DownloadCache.loadIndex(DownloadCache.java:103)
> 18:17:13 at com.googlecode.DownloadCache.install(DownloadCache.java:80)
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:252)
> 18:17:13 ... 21 more
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21298?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21298:
-----------------------------------
Summary: 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component (was: 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component)
> 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component
> ----------------------------------------------------------------------
>
> Key: JBIDE-21298
> URL: https://issues.jboss.org/browse/JBIDE-21298
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Critical
> Labels: testfailure
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component:*
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m...
> # [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds)
> [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for usage component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds)
>
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths}
> <case>
> <age>5</age>
> <className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className>
> <duration>0.0050</duration>
> <errorDetails>/qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1></errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.TestCase.assertEquals(TestCase.java:401)
> at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73)
> </errorStackTrace>
> <failedSince>58</failedSince>
> <name>testLoadSaveRuntimePaths</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21298?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21298:
-----------------------------------
Description:
*1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component:*
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m...
# [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds)
[Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for runtime-detection component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
-----
* {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds)
{code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths}
<case>
<age>5</age>
<className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className>
<duration>0.0050</duration>
<errorDetails>/qa/services/hudson/jboss-runtimes
expected:<0> but was:<1></errorDetails>
<errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes
expected:<0> but was:<1>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.TestCase.assertEquals(TestCase.java:401)
at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73)
</errorStackTrace>
<failedSince>58</failedSince>
<name>testLoadSaveRuntimePaths</name>
<skipped>false</skipped>
<status>FAILED</status>
</case>
{code}
was:
*1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component:*
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m...
# [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds)
[Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for usage component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
-----
* {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds)
{code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths}
<case>
<age>5</age>
<className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className>
<duration>0.0050</duration>
<errorDetails>/qa/services/hudson/jboss-runtimes
expected:<0> but was:<1></errorDetails>
<errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes
expected:<0> but was:<1>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.TestCase.assertEquals(TestCase.java:401)
at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73)
</errorStackTrace>
<failedSince>58</failedSince>
<name>testLoadSaveRuntimePaths</name>
<skipped>false</skipped>
<status>FAILED</status>
</case>
{code}
> 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component
> ----------------------------------------------------------------------
>
> Key: JBIDE-21298
> URL: https://issues.jboss.org/browse/JBIDE-21298
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Critical
> Labels: testfailure
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component:*
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m...
> # [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds)
> [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for runtime-detection component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds)
>
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths}
> <case>
> <age>5</age>
> <className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className>
> <duration>0.0050</duration>
> <errorDetails>/qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1></errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.TestCase.assertEquals(TestCase.java:401)
> at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73)
> </errorStackTrace>
> <failedSince>58</failedSince>
> <name>testLoadSaveRuntimePaths</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21298?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21298:
--------------------------------------
Assignee: Rob Stryker
> 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component
> ----------------------------------------------------------
>
> Key: JBIDE-21298
> URL: https://issues.jboss.org/browse/JBIDE-21298
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Critical
> Labels: testfailure
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component:*
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m...
> # [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds)
> [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for usage component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds)
>
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths}
> <case>
> <age>5</age>
> <className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className>
> <duration>0.0050</duration>
> <errorDetails>/qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1></errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.TestCase.assertEquals(TestCase.java:401)
> at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73)
> </errorStackTrace>
> <failedSince>58</failedSince>
> <name>testLoadSaveRuntimePaths</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21298?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21298:
-----------------------------------
Fix Version/s: 4.3.1.Beta1
4.4.0.Alpha1
> 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component
> ----------------------------------------------------------
>
> Key: JBIDE-21298
> URL: https://issues.jboss.org/browse/JBIDE-21298
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Critical
> Labels: testfailure
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component:*
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m...
> # [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds)
> [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for usage component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds)
>
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths}
> <case>
> <age>5</age>
> <className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className>
> <duration>0.0050</duration>
> <errorDetails>/qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1></errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.TestCase.assertEquals(TestCase.java:401)
> at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73)
> </errorStackTrace>
> <failedSince>58</failedSince>
> <name>testLoadSaveRuntimePaths</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21268) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Server]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21268?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-21268:
----------------------------------
Assignee: Rob Stryker
> For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Server]
> ----------------------------------------------------
>
> Key: JBIDE-21268
> URL: https://issues.jboss.org/browse/JBIDE-21268
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Server]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), 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.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT).
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta1x
> git push origin jbosstools-4.3.1.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and
> * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 Server 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)
10 years, 4 months
[JBoss JIRA] (JBIDE-21297) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21297?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21297:
-----------------------------------
Fix Version/s: 4.3.1.Beta1
4.3.1.Beta2
4.4.0.Alpha1
> 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component
> --------------------------------------------------------------------
>
> Key: JBIDE-21297
> URL: https://issues.jboss.org/browse/JBIDE-21297
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Labels: testfailure
> Fix For: 4.3.1.Beta1, 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component:*
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.m...
> # [org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest|https://jenkins.mw.lab.en...] (failing for 8 builds)
> [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest : testJstJsdtTernCAOnEcma5{color} (failing for 8 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.mars/68/testReport/org.jboss.tools.jst.jsdt.test/JstJsdtTernCATest/testJstJsdtTernCAOnEcma5}
> <case>
> <age>8</age>
> <className>org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest</className>
> <duration>1.777</duration>
> <errorDetails>Content Assistant returned no proposals</errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: Content Assistant returned no proposals
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79)
> at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:61)
> </errorStackTrace>
> <failedSince>61</failedSince>
> <name>testJstJsdtTernCAOnEcma5</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months