[JBoss JIRA] (JBIDE-22307) XML validation exclude group accidentally not working
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22307?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22307:
-----------------------------------
Fix Version/s: 4.4.x
> XML validation exclude group accidentally not working
> -----------------------------------------------------
>
> Key: JBIDE-22307
> URL: https://issues.jboss.org/browse/JBIDE-22307
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, upstream
> Environment: Eclipse Mars.2
> Reporter: Leonid Rozenblyum
> Fix For: 4.4.x
>
>
> The problem started to occur after recent JBoss Tools update:
> Windows -> Preferences -> Validation -> XML,
> Add a directory to exclude group.
> A directory contains a lot of xml files.
> Accidentally after SVN update or anything else the XML files inside the directory become validated and therefor a lot of XML errors are shown in Markers view.
> The problem is not stable to reproduce, however occurs rather often.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22307) XML validation exclude group accidentally not working
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22307?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22307:
----------------------------------------
Yes, details could help. But anyway this is an Eclipse upstream issue and should be reported in Eclipse bugzilla - https://bugs.eclipse.org
> XML validation exclude group accidentally not working
> -----------------------------------------------------
>
> Key: JBIDE-22307
> URL: https://issues.jboss.org/browse/JBIDE-22307
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, upstream
> Environment: Eclipse Mars.2
> Reporter: Leonid Rozenblyum
>
> The problem started to occur after recent JBoss Tools update:
> Windows -> Preferences -> Validation -> XML,
> Add a directory to exclude group.
> A directory contains a lot of xml files.
> Accidentally after SVN update or anything else the XML files inside the directory become validated and therefor a lot of XML errors are shown in Markers view.
> The problem is not stable to reproduce, however occurs rather often.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22417) Eclipse will not run with java9 - NoClassDefFoundError
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22417?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22417:
-------------------------------
Fix Version/s: 4.4.x
> Eclipse will not run with java9 - NoClassDefFoundError
> ------------------------------------------------------
>
> Key: JBIDE-22417
> URL: https://issues.jboss.org/browse/JBIDE-22417
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.4.0.Alpha2
> Reporter: Martin Malina
> Fix For: 4.4.x
>
>
> As of the latest build of Oracle JDK 9, Eclipse Neon M7 will not start.
> Java version:
> {code}
> $ java -version
> java version "9-ea"
> Java(TM) SE Runtime Environment (build 9-ea+118)
> Java HotSpot(TM) 64-Bit Server VM (build 9-ea+118, mixed mode)
> {code}
> Error log:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2016-05-19 11:14:42.241
> !MESSAGE Application error
> !STACK 1
> org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:386)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:490)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:504)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:203)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:626)
> 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 jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:531)
> 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)
> Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375)
> ... 22 more
> Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:394)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(java.base@9-ea/ClassLoader.java:419)
> ... 24 more
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2016-05-19 11:14:42.248
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> java.lang.NoClassDefFoundError: javax/annotation/PreDestroy
> at org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:426)
> at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:154)
> at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:78)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.handleInvalid(TrackableComputationExt.java:74)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:175)
> at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:106)
> at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:139)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:903)
> 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.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213)
> at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120)
> at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112)
> at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:156)
> at org.eclipse.osgi.container.Module.publishEvent(Module.java:476)
> at org.eclipse.osgi.container.Module.doStop(Module.java:634)
> at org.eclipse.osgi.container.Module.stop(Module.java:498)
> at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:191)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165)
> at java.lang.Thread.run(java.base@9-ea/Thread.java:804)
> Caused by: java.lang.ClassNotFoundException: javax.annotation.PreDestroy cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:394)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(java.base@9-ea/ClassLoader.java:419)
> ... 21 more
> {code}
> Upstream issue - targeted for Neon.1:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=493761
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22303) Server Adapter: Manually set pod deployment path is ignored
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22303?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22303.
---------------------------------
Verified in Red Hat Developer Studio with build id: Alpha1-v20160520-0424-B5396.
> Server Adapter: Manually set pod deployment path is ignored
> -----------------------------------------------------------
>
> Key: JBIDE-22303
> URL: https://issues.jboss.org/browse/JBIDE-22303
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha2
>
>
> When creating a new OpenShift 3 server adapter, manually filled Pod deployment path is ignored by the server adapter and still inferred one is used for publishing changes between eclipse workspace project and remote OpenShift application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22005) Log console: Unexpected EOF in pod log
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22005.
---------------------------------
> Log console: Unexpected EOF in pod log
> --------------------------------------
>
> Key: JBIDE-22005
> URL: https://issues.jboss.org/browse/JBIDE-22005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha2
>
>
> I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log.
> Last lines from console (output of application pod log)
> {code}
> ...
> [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe...
> error: unexpected EOF
> {code}
> I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22268) Server adapter wizard: create unit tests
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22268?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22268.
---------------------------------
Closing, nothing to verify.
> Server adapter wizard: create unit tests
> ----------------------------------------
>
> Key: JBIDE-22268
> URL: https://issues.jboss.org/browse/JBIDE-22268
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: server_adapter_wizard
> Fix For: 4.4.0.Alpha2
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> The server adapter wizard should be unit tested. Given it's implemented using databinding and a presentation model (ServerSettingsWizardPageModel) the model can be unit tested (ex. #setService and then test all it's states: source path, deploy project etc.).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months