Bug 579222 - java.io.FileNotFoundException: org.eclipse.equinox.simpleconfigurator/bundles.info
Summary: java.io.FileNotFoundException: org.eclipse.equinox.simpleconfigurator/bundles...
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 4.23   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2022-03-11 06:55 EST by Christian Dietrich CLA
Modified: 2024-03-07 01:05 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Dietrich CLA 2022-03-11 06:55:44 EST
jdt.junit logs 
java.io.FileNotFoundException: org.eclipse.equinox.simpleconfigurator/bundles.info
all the time

java.io.FileNotFoundException: org.eclipse.equinox.simpleconfigurator/bundles.info (No such file or directory)
at java.base/java.io.FileInputStream.open0(Native Method)
at java.base/java.io.FileInputStream.open(FileInputStream.java:219)
at java.base/java.io.FileInputStream.<init>(FileInputStream.java:157)
at java.base/java.io.FileInputStream.<init>(FileInputStream.java:112)
at java.base/sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:86)
at java.base/sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:184)
at java.base/java.net.URL.openStream(URL.java:1140)
at org.eclipse.equinox.internal.simpleconfigurator.manipulator.SimpleConfiguratorManipulatorImpl.loadConfiguration(SimpleConfiguratorManipulatorImpl.java:370)
at org.eclipse.jdt.internal.junit.buildpath.P2Utils.findBundle(P2Utils.java:93)
at org.eclipse.jdt.internal.junit.buildpath.BuildPathSupport$JUnitPluginDescription.getBundleLocation(BuildPathSupport.java:88)
at org.eclipse.jdt.internal.junit.buildpath.BuildPathSupport$JUnitPluginDescription.getBundleLocation(BuildPathSupport.java:84)
at org.eclipse.jdt.internal.junit.buildpath.BuildPathSupport$JUnitPluginDescription.getLibraryEntry(BuildPathSupport.java:213)
at org.eclipse.jdt.internal.junit.buildpath.BuildPathSupport.getJUnitJupiterApiLibraryEntry(BuildPathSupport.java:415)
at org.eclipse.jdt.internal.junit.buildpath.JUnitContainerInitializer.getNewContainer(JUnitContainerInitializer.java:125)

at org.eclipse.jdt.internal.junit.buildpath.JUnitContainerInitializer.initialize(JUnitContainerInitializer.java:101)
Comment 1 Christian Dietrich CLA 2022-03-11 06:58:44 EST
https://git.eclipse.org/r/c/jdt/eclipse.jdt.ui/+/191706
Comment 2 Andrey Loskutov CLA 2022-03-11 09:04:31 EST
Isn't that PDE bug? Shouldn't this file be there?
Can you explain what are you doing, what effect the exception has on what you are doing and if this is a regression?
Comment 3 Christian Dietrich CLA 2022-03-11 10:19:14 EST
No this is an old problem to my knowledge
Comment 4 Christian Dietrich CLA 2022-03-11 11:01:28 EST
and i dont know if this is a p2 problem or a jdt problem.
Comment 5 Jeff Johnston CLA 2022-03-16 17:54:57 EDT
(In reply to Christian Dietrich from comment #4)
> and i dont know if this is a p2 problem or a jdt problem.

I don't see this problem running JUnit tests on Linux (JDT tests or JUnit 5 sample tests).  I don't see this as a JDT problem since it is just reporting the exception. It has something to do with your set-up and removing the log is not the right solution.

I will re-route to PDE to see if someone can clarify the source of the issue.
Comment 6 Christian Dietrich CLA 2022-03-17 02:38:05 EDT
@Jeff this happens when you programmtically create a java project in tycho based tests.
Comment 7 Christian Dietrich CLA 2022-03-17 03:50:10 EDT
please find a reproducer at 
https://github.com/cdietrich/bug_579222
Comment 8 Eclipse Genie CLA 2024-03-07 01:05:29 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.