Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle multiple class path resources with the same name #30

Open
hugithordarson opened this issue Oct 24, 2022 · 0 comments
Open

Handle multiple class path resources with the same name #30

hugithordarson opened this issue Oct 24, 2022 · 0 comments
Labels
resources
Milestone
0.1.0

Comments

@hugithordarson
Copy link
Collaborator

We should be using ClassLoader.getResources() instead of getResources() when locating resources. If multiple resources share the same name, there's probably not much we can do, apart from at least starting out with throwing a warning about the situation (at least until we add a way to segregate/namespace the resources).
@hugithordarson hugithordarson moved this from Todo to Selected for development in ng-objects-0.1.0 Dec 17, 2022
@hugithordarson hugithordarson moved this from Selected for development to Document in ng-objects-0.1.0 Dec 17, 2022
@hugithordarson hugithordarson moved this from Document to Testing in ng-objects-0.1.0 Jan 7, 2023
@hugithordarson hugithordarson moved this from Testing to Selected for development in ng-objects-0.1.0 Mar 12, 2023
@hugithordarson hugithordarson moved this from Selected for development to Testing in ng-objects-0.1.0 Mar 12, 2023
@hugithordarson hugithordarson added this to the 0.1.0 milestone Mar 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
resources
Projects
ng-objects-0.1.0
Status: Testing
Milestone
0.1.0
Development

No branches or pull requests
1 participant
@hugithordarson