You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the java archive extractor, we add location paths that's within the jar file and does not exist on the filesystem. We should determine how we can mark those paths as such.
Some options are:
Two options here:
Just account for the common case and assume that it's unlikely to have a directory : in the file path, so we can add /:/ as a separator between the jar file and the internal path. E.g. /path/to/item.jar/:/internal/path/pom.properties
Escape the : character in the path (maybe just doubling it ::). This seems extra tough to do with the current architecture, as every extractor directly fills out the Location field.
Maybe something to look into for the new API.
The text was updated successfully, but these errors were encountered:
For the java archive extractor, we add location paths that's within the jar file and does not exist on the filesystem. We should determine how we can mark those paths as such.
Some options are:
Two options here:
:
in the file path, so we can add /:/ as a separator between the jar file and the internal path. E.g./path/to/item.jar/:/internal/path/pom.properties
Maybe something to look into for the new API.
The text was updated successfully, but these errors were encountered: