March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25727) Arquillian New and Noteworthy for 4.5.3.AM2

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25727?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-25727. ----------------------------------- Resolution: Rejected No changes for N&N. > Arquillian New and Noteworthy for 4.5.3.AM2 > --------------------------------------------------- > > Key: JBIDE-25727 > URL: https://issues.jboss.org/browse/JBIDE-25727 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Jeff MAURY > Assignee: Snjezana Peco > Priority: Critical > Labels: task > Fix For: 4.5.3.AM2 > > > Snjezana Peco, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Arquillian JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Arquillian, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Arquillian by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25708 #comment Create N&N for Arquillian 4.5.3.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Arquillian for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25727) Arquillian New and Noteworthy for 4.5.3.AM2

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25727?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-25727. --------------------------------- > Arquillian New and Noteworthy for 4.5.3.AM2 > --------------------------------------------------- > > Key: JBIDE-25727 > URL: https://issues.jboss.org/browse/JBIDE-25727 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Jeff MAURY > Assignee: Snjezana Peco > Priority: Critical > Labels: task > Fix For: 4.5.3.AM2 > > > Snjezana Peco, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Arquillian JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Arquillian, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Arquillian by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25708 #comment Create N&N for Arquillian 4.5.3.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Arquillian for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25759) CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25759?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-25759: ------------------------------------- I like that one best. !JBIDE-25759_v2.png! +100 about using "skip registration when starting" and "skip unregistration when stopping" instead of blabbing about flags > CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-25759 > URL: https://issues.jboss.org/browse/JBIDE-25759 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: JBIDE-25759.png, JBIDE-25759_v2.png, screenshot-1.png > > > The layout for the checkboxes to skip the registration/unregistration are not well horizontally aligned with the "Registration:" label. They are pushed to the bottom by 1 line: > !screenshot-1.png! > And then one could wonder if simply using "skip registration when starting" and "skip unregistration when stopping" are more easily understood than "add --skip-registration flag when starting" and "add --skip-unregistration flag when stopping" . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25759) CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25759?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25759: ------------------------------------- I've attached two files. In the first, the first option (for both environment variables or registration) are next to the category label, and the second is below it. In the second option, both categories skip a line and indent the options. There could also be a third option: Both categories skip a line and do not indent. This would bring the registration section in line with the current behavior of the Environment Variables. Please tell me which one is best. > CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-25759 > URL: https://issues.jboss.org/browse/JBIDE-25759 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: JBIDE-25759.png, JBIDE-25759_v2.png, screenshot-1.png > > > The layout for the checkboxes to skip the registration/unregistration are not well horizontally aligned with the "Registration:" label. They are pushed to the bottom by 1 line: > !screenshot-1.png! > And then one could wonder if simply using "skip registration when starting" and "skip unregistration when stopping" are more easily understood than "add --skip-registration flag when starting" and "add --skip-unregistration flag when stopping" . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25759) CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25759?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25759: -------------------------------- Attachment: JBIDE-25759_v2.png > CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-25759 > URL: https://issues.jboss.org/browse/JBIDE-25759 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: JBIDE-25759.png, JBIDE-25759_v2.png, screenshot-1.png > > > The layout for the checkboxes to skip the registration/unregistration are not well horizontally aligned with the "Registration:" label. They are pushed to the bottom by 1 line: > !screenshot-1.png! > And then one could wonder if simply using "skip registration when starting" and "skip unregistration when stopping" are more easily understood than "add --skip-registration flag when starting" and "add --skip-unregistration flag when stopping" . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25759) CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25759?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25759: -------------------------------- Attachment: JBIDE-25759.png > CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-25759 > URL: https://issues.jboss.org/browse/JBIDE-25759 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: JBIDE-25759.png, screenshot-1.png > > > The layout for the checkboxes to skip the registration/unregistration are not well horizontally aligned with the "Registration:" label. They are pushed to the bottom by 1 line: > !screenshot-1.png! > And then one could wonder if simply using "skip registration when starting" and "skip unregistration when stopping" are more easily understood than "add --skip-registration flag when starting" and "add --skip-unregistration flag when stopping" . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25711) Docker New and Noteworthy for 4.5.3.AM2

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25711?page=com.atlassian.jira.plugi... ] Jeff Johnston closed JBIDE-25711. --------------------------------- Resolution: Rejected 4.5.3.AM2 is based on Oxygen.3 which is a bug-fix only release. > Docker New and Noteworthy for 4.5.3.AM2 > --------------------------------------------------- > > Key: JBIDE-25711 > URL: https://issues.jboss.org/browse/JBIDE-25711 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Jeff Johnston > Priority: Critical > Labels: task > Fix For: 4.5.3.AM2 > > > Jeff Johnston, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Docker JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Docker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Docker by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25708 #comment Create N&N for Docker 4.5.3.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Docker for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25759) CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25759?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25759: ------------------------------------- Should I also be removing the newline from the Environment Variables: section as well? > CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-25759 > URL: https://issues.jboss.org/browse/JBIDE-25759 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: screenshot-1.png > > > The layout for the checkboxes to skip the registration/unregistration are not well horizontally aligned with the "Registration:" label. They are pushed to the bottom by 1 line: > !screenshot-1.png! > And then one could wonder if simply using "skip registration when starting" and "skip unregistration when stopping" are more easily understood than "add --skip-registration flag when starting" and "add --skip-unregistration flag when stopping" . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25759) CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25759?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-25759: --------------------------------------- I agree with Andre. In general we usually try to explain options in plain english as opposed to using cmd line arguments. Also, the new line seems unnecessary. > CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-25759 > URL: https://issues.jboss.org/browse/JBIDE-25759 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: screenshot-1.png > > > The layout for the checkboxes to skip the registration/unregistration are not well horizontally aligned with the "Registration:" label. They are pushed to the bottom by 1 line: > !screenshot-1.png! > And then one could wonder if simply using "skip registration when starting" and "skip unregistration when stopping" are more easily understood than "add --skip-registration flag when starting" and "add --skip-unregistration flag when stopping" . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25765) OpenShift: java.time.format.DateTimeParseException

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25765?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-25765: ---------------------------------------- Assignee: Dmitrii Bocharov > OpenShift: java.time.format.DateTimeParseException > -------------------------------------------------- > > Key: JBIDE-25765 > URL: https://issues.jboss.org/browse/JBIDE-25765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM2 > Environment: F27, console.engint.openshift.com also on CDK 3.3.0, and on Win10 + Java9 > Red Hat JBoss Developer Studio > Version: 11.3.0.AM2 > Build id: AM2-v20180301-1142-B2132 > Build date: 20180301-1142 > Reporter: Josef Kopriva > Assignee: Dmitrii Bocharov > Priority: Blocker > Fix For: 4.5.3.AM2 > > > {code:java} > eclipse.buildId=11.3.0.AM2-v20180301-1142-B2132 > java.version=1.8.0_161 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.ui.views.properties.tabbed > Error > Thu Mar 01 15:53:13 CET 2018 > Problems occurred when invoking code from plug-in: "org.eclipse.ui.views.properties.tabbed". > java.time.format.DateTimeParseException: Text '2018-03-01T14:52:48Z' could not be parsed: Unable to obtain ZonedDateTime from TemporalAccessor: {MicroOfSecond=0, InstantSeconds=1519915968, NanoOfSecond=0, MilliOfSecond=0},ISO of type java.time.format.Parsed > at java.time.format.DateTimeFormatter.createError(DateTimeFormatter.java:1920) > at java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1855) > at java.time.ZonedDateTime.parse(ZonedDateTime.java:597) > at org.jboss.tools.openshift.internal.common.ui.utils.DateTimeUtils.formatSince(DateTimeUtils.java:57) > at org.jboss.tools.openshift.internal.common.ui.utils.DateTimeUtils.formatSince(DateTimeUtils.java:49) > at org.jboss.tools.openshift.internal.ui.property.BuildPropertySource.getPropertyValue(BuildPropertySource.java:53) > at org.eclipse.ui.views.properties.PropertySheetEntry.refreshValues(PropertySheetEntry.java:584) > at org.eclipse.ui.views.properties.PropertySheetEntry.createChildEntries(PropertySheetEntry.java:252) > at org.eclipse.ui.views.properties.PropertySheetEntry.getChildEntries(PropertySheetEntry.java:339) > at org.eclipse.ui.views.properties.PropertySheetViewer.updateCategories(PropertySheetViewer.java:1086) > at org.eclipse.ui.views.properties.PropertySheetViewer.updateChildrenOf(PropertySheetViewer.java:1254) > at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:978) > at org.eclipse.ui.views.properties.PropertySheetPage.refresh(PropertySheetPage.java:539) > at org.jboss.tools.openshift.internal.common.ui.explorer.DefaultPropertySection.refresh(DefaultPropertySection.java:53) > at org.eclipse.ui.views.properties.tabbed.TabContents$6.run(TabContents.java:211) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.ui.views.properties.tabbed.TabContents.refresh(TabContents.java:214) > at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage$SelectionChangedListener.selectionChanged(TabbedPropertySheetPage.java:221) > at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:155) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:152) > at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2180) > at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1717) > at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:380) > at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.setInput(TabbedPropertySheetPage.java:747) > at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.selectionChanged(TabbedPropertySheetPage.java:555) > at org.eclipse.ui.views.properties.PropertySheet.showSelectionAndDescription(PropertySheet.java:498) > at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:478) > at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:239) > at org.eclipse.ui.internal.e4.compatibility.SelectionService.handlePostSelectionChanged(SelectionService.java:113) > at org.eclipse.ui.internal.e4.compatibility.SelectionService.lambda$2(SelectionService.java:68) > at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$4.run(SelectionAggregator.java:166) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyPostListeners(SelectionAggregator.java:163) > at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$8(SelectionAggregator.java:161) > at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8$1.run(SelectionAggregator.java:271) > at org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(RunAndTrack.java:56) > at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8.changed(SelectionAggregator.java:268) > at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:114) > at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:355) > at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:370) > at org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setPostSelection(SelectionServiceImpl.java:36) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.lambda$2(CompatibilityPart.java:125) > at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:872) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:869) > at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1238) > at org.eclipse.ui.navigator.CommonViewer.handlePostSelect(CommonViewer.java:457) > at org.eclipse.jface.viewers.StructuredViewer.lambda$0(StructuredViewer.java:1261) > at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:81) > at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:261) > at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:256) > at org.eclipse.jface.util.OpenStrategy$1.lambda$1(OpenStrategy.java:426) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4577) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4186) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151) > 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:653) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) > at org.eclipse.equinox.launcher.Main.run(Main.java:1499) > at org.eclipse.equinox.launcher.Main.main(Main.java:1472) > Caused by: java.time.DateTimeException: Unable to obtain ZonedDateTime from TemporalAccessor: {MicroOfSecond=0, InstantSeconds=1519915968, NanoOfSecond=0, MilliOfSecond=0},ISO of type java.time.format.Parsed > at java.time.ZonedDateTime.from(ZonedDateTime.java:565) > at java.time.format.Parsed.query(Parsed.java:226) > at java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1851) > ... 83 more > Caused by: java.time.DateTimeException: Unable to obtain ZoneId from TemporalAccessor: {MicroOfSecond=0, InstantSeconds=1519915968, NanoOfSecond=0, MilliOfSecond=0},ISO of type java.time.format.Parsed > at java.time.ZoneId.from(ZoneId.java:466) > at java.time.ZonedDateTime.from(ZonedDateTime.java:553) > ... 85 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 March 2018