Bug 581302 - resources Folder missing on Jar-In-Jar Classpath
Summary: resources Folder missing on Jar-In-Jar Classpath
Status: NEW
Alias: None
Product: Incubator
Classification: Eclipse Project
Component: e4 (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: E4 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-09 03:55 EST by DaveLaw CLA
Modified: 2023-01-09 04:18 EST (History)
1 user (show)

See Also:


Attachments
Eclipse Project Structure (9.36 KB, image/png)
2023-01-09 03:55 EST, DaveLaw CLA
no flags Details
Eclipse Project target/classes Folder (2.92 KB, image/png)
2023-01-09 03:56 EST, DaveLaw CLA
no flags Details
Exported Jar-In-Jar Root Folder (6.95 KB, image/png)
2023-01-09 03:57 EST, DaveLaw CLA
no flags Details
Exported Jar-In-Jar resources Folder (4.24 KB, image/png)
2023-01-09 03:57 EST, DaveLaw CLA
no flags Details
Exported Jar-In-Jar MANIFEST (212 bytes, application/octet-stream)
2023-01-09 04:01 EST, DaveLaw CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description DaveLaw CLA 2023-01-09 03:55:16 EST
Created attachment 288910 [details]
Eclipse Project Structure
Comment 1 DaveLaw CLA 2023-01-09 03:56:30 EST
Created attachment 288911 [details]
Eclipse Project target/classes Folder
Comment 2 DaveLaw CLA 2023-01-09 03:57:19 EST
Created attachment 288912 [details]
Exported Jar-In-Jar Root Folder
Comment 3 DaveLaw CLA 2023-01-09 03:57:51 EST
Created attachment 288913 [details]
Exported Jar-In-Jar resources Folder
Comment 4 DaveLaw CLA 2023-01-09 04:01:17 EST
Created attachment 288914 [details]
Exported Jar-In-Jar MANIFEST
Comment 5 DaveLaw CLA 2023-01-09 04:13:51 EST
When running a Class from the Eclipse Project, the CONTENTS of the resources Folder are copied to the target/classes Folder.

When the project is exported using the "Export/Runnable Jar File" wizard, the resources FOLDER is copied to the output Jar but is not added to the Classpath.

Resources loaded via Thread.currentThread().getContextClassLoader() are therefore not found in the Jar-In-Jar.