We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
v0.9.1
package command exports the module to directory dictated by -path option. In the directory the command creates following items:
package
-path
If the directory already exists and contains e.g. class files those files are silently included into the actual exported package tarball.
So currently the directory should not be reused blindly but it is user's responsibility to make sure -path is good to go.
I find this is surprising and unexpected and undocumented behavior.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
v0.9.1
package
command exports the module to directory dictated by-path
option. In the directory the command creates following items:If the directory already exists and contains e.g. class files those files are silently included into the actual exported package tarball.
So currently the directory should not be reused blindly but it is user's responsibility to make sure
-path
is good to go.I find this is surprising and unexpected and undocumented behavior.
The text was updated successfully, but these errors were encountered: