Skip to content

Handle multiple class path resources with the same name #30

Open

Description

@hugithordarson

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).

Activity

  1. moved this from Todo to Selected for development in ng-objects-0.1.0on Dec 17, 2022
  2. moved this from Selected for development to Document in ng-objects-0.1.0on Dec 17, 2022
  3. moved this from Document to Testing in ng-objects-0.1.0on Jan 7, 2023
  4. moved this from Testing to Selected for development in ng-objects-0.1.0on Mar 12, 2023
  5. moved this from Selected for development to Testing in ng-objects-0.1.0on Mar 12, 2023
  6. added this to the 0.1.0 milestone on Mar 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions