Closed
Description
After putting further thought into the semantics for getPath()
in ClassPathResource
, I realized the following.
- Several tests were previously misusing
getPath()
, and I rectified that in commit 1688bec. - My updates to the Javadoc for
getPath()
make it clear that the semantics are very inconsistent. See current Javadoc. - If we switch
getPath()
to returnthis.absolutePath
, the entire test suite passes exceptClassPathResourceTests.preserveLeadingSlashForClassRelativeAccess()
. Yet, I would argue that's not a valid use case.
In light of the above, I'm wondering if we should:
- Switch
getPath()
to return the absolute path consistently without a leading slash. - Return the Javadoc for
getPath()
to its previous state (prior to Introduce getAbsolutePath() in ClassPathResource #29094). - Remove the newly introduced
getAbsolutePath()
method (i.e., revert Introduce getAbsolutePath() in ClassPathResource #29094).