[JBoss JIRA] (JBIDE-27205) NPE in Eclipse log coming from jrebel when installing all SWT (including early access) from RH Central
by Stephane Bouchet (Jira)
[ https://issues.redhat.com/browse/JBIDE-27205?page=com.atlassian.jira.plug... ]
Stephane Bouchet commented on JBIDE-27205:
------------------------------------------
There is also errors about checkstyle.
I've also seen error about not being able to reach testng update site...
What is the JDK used?
> NPE in Eclipse log coming from jrebel when installing all SWT (including early access) from RH Central
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-27205
> URL: https://issues.redhat.com/browse/JBIDE-27205
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.15.0.Final
> Reporter: Ondrej Dockal
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 4.16.x
>
> Attachments: jbt-swt-central.log, studio-swt-central.log
>
>
> I spotted some NPE in eclipse log after installation all swt from central.
> Happened on Central CI, did not reproduce locally.
> Errors:
> {code}
> !ENTRY org.eclipse.equinox.p2.metadata.repository 4 0 2020-04-16 16:46:43.539
> !MESSAGE Unexpected error loading extension: org.eclipse.equinox.p2.metadata.repository.simpleRepository
> !STACK 0
> java.lang.NullPointerException
> at org.osgi.util.tracker.ServiceTracker.<init>(ServiceTracker.java:187)
> at org.osgi.util.tracker.ServiceTracker.<init>(ServiceTracker.java:250)
> at org.eclipse.ecf.internal.provider.filetransfer.httpclient45.Activator.getHttpClientFactory(Activator.java:239)
> at org.eclipse.ecf.internal.provider.filetransfer.httpclient45.Activator.getBrowseHttpClient(Activator.java:264)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientBrowseFileTransferFactory$1.sendBrowseRequest(HttpClientBrowseFileTransferFactory.java:57)
> at org.eclipse.ecf.provider.filetransfer.browse.MultiProtocolFileSystemBrowserAdapter.sendBrowseRequest(MultiProtocolFileSystemBrowserAdapter.java:95)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileInfoReader.sendBrowseRequest(FileInfoReader.java:184)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileInfoReader.getRemoteFiles(FileInfoReader.java:109)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileInfoReader.getRemoteFile(FileInfoReader.java:125)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileInfoReader.getLastModified(FileInfoReader.java:130)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.getLastModified(RepositoryTransport.java:249)
> at org.eclipse.oomph.p2.internal.core.CachingTransport.delegateGetLastModified(CachingTransport.java:396)
> at org.eclipse.oomph.p2.internal.core.CachingTransport.getLastModified(CachingTransport.java:345)
> at org.eclipse.equinox.internal.p2.repository.CacheManager.createCache(CacheManager.java:229)
> at org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.getLocalFile(SimpleMetadataRepositoryFactory.java:69)
> at org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.load(SimpleMetadataRepositoryFactory.java:89)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:63)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:775)
> at jdk.internal.reflect.GeneratedMethodAccessor43.invoke(Unknown Source)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:117)
> at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:423)
> at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:214)
> at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:495)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.query(AbstractRepositoryManager.java:1167)
> at org.zeroturnaround.eclipse.update.EclipsePluginLatestVersionProvider.hasRequirements(EclipsePluginLatestVersionProvider.java:86)
> at org.zeroturnaround.eclipse.update.EclipsePluginLatestVersionProvider.getLatestVersionInternal(EclipsePluginLatestVersionProvider.java:76)
> at org.zeroturnaround.eclipse.update.EclipsePluginLatestVersionProvider.getLatestVersionOnline(EclipsePluginLatestVersionProvider.java:50)
> at org.zeroturnaround.eclipse.update.EclipsePluginLatestVersionProvider.getLatestVersion(EclipsePluginLatestVersionProvider.java:42)
> at org.zeroturnaround.jrebel.client.update.PluginLatestVersion.findLatestVersion(PluginLatestVersion.java:24)
> at org.zeroturnaround.jrebel.ide.common.utils.update.JRebelPluginUpdate.getUpdateSiteVersion(JRebelPluginUpdate.java:159)
> at org.zeroturnaround.jrebel.ide.common.utils.update.JRebelPluginUpdate.checkForNewVersion(JRebelPluginUpdate.java:51)
> at org.zeroturnaround.jrebel.ide.common.utils.update.JRebelPluginUpdate.startNewVersionCheck(JRebelPluginUpdate.java:39)
> at org.zeroturnaround.jrebel.ide.common.CommonStartup.lambda$startNewVersionCheck$4(CommonStartup.java:310)
> at org.zeroturnaround.jrebel.ide.common.CommonStartup$$Lambda$10.run(CommonStartup.java)
> at org.zeroturnaround.common.util.ExecutorUtil$RunnableWrapper.run(ExecutorUtil.java:161)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
> and
> {code}
> !ENTRY org.eclipse.equinox.p2.metadata.repository 4 0 2020-04-16 16:34:14.559
> !MESSAGE Unexpected error loading extension: org.eclipse.equinox.p2.metadata.repository.compositeRepository
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.handleRemoteIndexFile(AbstractRepositoryManager.java:729)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadIndexFile(AbstractRepositoryManager.java:723)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:665)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:110)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:105)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:171)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:113)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:124)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:63)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:775)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:676)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.query(AbstractRepositoryManager.java:1167)
> at org.zeroturnaround.eclipse.update.EclipsePluginLatestVersionProvider.hasRequirements(EclipsePluginLatestVersionProvider.java:86)
> at org.zeroturnaround.eclipse.update.EclipsePluginLatestVersionProvider.getLatestVersionInternal(EclipsePluginLatestVersionProvider.java:76)
> at org.zeroturnaround.eclipse.update.EclipsePluginLatestVersionProvider.getLatestVersionOnline(EclipsePluginLatestVersionProvider.java:50)
> at org.zeroturnaround.eclipse.update.EclipsePluginLatestVersionProvider.getLatestVersion(EclipsePluginLatestVersionProvider.java:42)
> at org.zeroturnaround.jrebel.client.update.PluginLatestVersion.findLatestVersion(PluginLatestVersion.java:24)
> at org.zeroturnaround.jrebel.ide.common.utils.update.JRebelPluginUpdate.getUpdateSiteVersion(JRebelPluginUpdate.java:159)
> at org.zeroturnaround.jrebel.ide.common.utils.update.JRebelPluginUpdate.checkForNewVersion(JRebelPluginUpdate.java:51)
> at org.zeroturnaround.jrebel.ide.common.utils.update.JRebelPluginUpdate.startNewVersionCheck(JRebelPluginUpdate.java:39)
> at org.zeroturnaround.jrebel.ide.common.CommonStartup.lambda$startNewVersionCheck$4(CommonStartup.java:310)
> at org.zeroturnaround.jrebel.ide.common.CommonStartup$$Lambda$10.run(CommonStartup.java)
> at org.zeroturnaround.common.util.ExecutorUtil$RunnableWrapper.run(ExecutorUtil.java:161)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (JBIDE-27207) XHTML-files not showing when opened with JBoss Tools Html Editor in Eclipse
by Niklas G (Jira)
[ https://issues.redhat.com/browse/JBIDE-27207?page=com.atlassian.jira.plug... ]
Niklas G edited comment on JBIDE-27207 at 4/20/20 3:34 AM:
-----------------------------------------------------------
Hi, thank you for the quick answer. The scenario following what I did:
1. Install a clean Eclipse 2020-03
2. Using Eclipse Marketplace, install JBoss Tools
3. In Eclipse, import an existing project using the import wizard for existing projects
4. Double click any .xhtml-file in the project explorer
5. Effect as described.
was (Author: niklas.grunbaum):
Hi, thank you for the quick answer. The scenario following what I did:
1. Install a clean Exlipse 2020-03
2. Using Eclipse Marketplace, install JBoss Tools
3. In Eclipse, import an existing project using the import wizard for existing projects
4. Double click any .xhtml-file in the project explorer
5. Effect as described.
> XHTML-files not showing when opened with JBoss Tools Html Editor in Eclipse
> ---------------------------------------------------------------------------
>
> Key: JBIDE-27207
> URL: https://issues.redhat.com/browse/JBIDE-27207
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.14.0.Final
> Reporter: Niklas G
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.16.x
>
>
> In Eclipse, when opening (existing or creating a fresh one) an XHTML-file with JBoss Tools Html Editor, the edior does not show the file. In the editor pane, an invisible editor is opened only noticable when hovering the mouse arrow over the expected place for the close tab marker. Otherwise not showing.
> Using Eclipse 2020-03
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (JBIDE-27207) XHTML-files not showing when opened with JBoss Tools Html Editor in Eclipse
by Niklas G (Jira)
[ https://issues.redhat.com/browse/JBIDE-27207?page=com.atlassian.jira.plug... ]
Niklas G commented on JBIDE-27207:
----------------------------------
Hi, thank you for the quick answer. The scenario following what I did:
1. Install a clean Exlipse 2020-03
2. Using Eclipse Marketplace, install JBoss Tools
3. In Eclipse, import an existing project using the import wizard for existing projects
4. Double click any .xhtml-file in the project explorer
5. Effect as described.
> XHTML-files not showing when opened with JBoss Tools Html Editor in Eclipse
> ---------------------------------------------------------------------------
>
> Key: JBIDE-27207
> URL: https://issues.redhat.com/browse/JBIDE-27207
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.14.0.Final
> Reporter: Niklas G
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.16.x
>
>
> In Eclipse, when opening (existing or creating a fresh one) an XHTML-file with JBoss Tools Html Editor, the edior does not show the file. In the editor pane, an invisible editor is opened only noticable when hovering the mouse arrow over the expected place for the close tab marker. Otherwise not showing.
> Using Eclipse 2020-03
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (JBIDE-27207) XHTML-files not showing when opened with JBoss Tools Html Editor in Eclipse
by Jeff MAURY (Jira)
[ https://issues.redhat.com/browse/JBIDE-27207?page=com.atlassian.jira.plug... ]
Jeff MAURY commented on JBIDE-27207:
------------------------------------
Please note that JBoss Tools 4.14.0.Final is validated against 2019-12, not 2020-03. Can you describe the scenario so that we can validate it against the next 4.15.0.Final that is going out in a few days and that is 2020-03 compatible.
> XHTML-files not showing when opened with JBoss Tools Html Editor in Eclipse
> ---------------------------------------------------------------------------
>
> Key: JBIDE-27207
> URL: https://issues.redhat.com/browse/JBIDE-27207
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.14.0.Final
> Reporter: Niklas G
> Priority: Major
> Fix For: 4.16.x
>
>
> In Eclipse, when opening (existing or creating a fresh one) an XHTML-file with JBoss Tools Html Editor, the edior does not show the file. In the editor pane, an invisible editor is opened only noticable when hovering the mouse arrow over the expected place for the close tab marker. Otherwise not showing.
> Using Eclipse 2020-03
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (JBIDE-27207) XHTML-files not showing when opened with JBoss Tools Html Editor in Eclipse
by Niklas G (Jira)
Niklas G created JBIDE-27207:
--------------------------------
Summary: XHTML-files not showing when opened with JBoss Tools Html Editor in Eclipse
Key: JBIDE-27207
URL: https://issues.redhat.com/browse/JBIDE-27207
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.14.0.Final
Reporter: Niklas G
In Eclipse, when opening (existing or creating a fresh one) an XHTML-file with JBoss Tools Html Editor, the edior does not show the file. In the editor pane, an invisible editor is opened only noticable when hovering the mouse arrow over the expected place for the close tab marker. Otherwise not showing.
Using Eclipse 2020-03
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (JBIDE-26475) Update lucene version in target platform
by Stephane Bouchet (Jira)
[ https://issues.redhat.com/browse/JBIDE-26475?page=com.atlassian.jira.plug... ]
Stephane Bouchet reassigned JBIDE-26475:
----------------------------------------
Assignee: Stephane Bouchet
> Update lucene version in target platform
> ----------------------------------------
>
> Key: JBIDE-26475
> URL: https://issues.redhat.com/browse/JBIDE-26475
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, target-platform
> Affects Versions: 4.10.0.AM1
> Reporter: Josef Kopriva
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 4.15.0.Final
>
>
> Investigate and identify why do we multiple version of org.apache.lucene.8 packages in target plaform(e.g. in eclipse TP is version 7.5, but in target platform is 7.1).
> It would be also nice, if comments would be added in target file to know why we have different versions.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months