Skip to content

Remove --no-transfer-progress from Maven command#210

Merged
olafurpg merged 2 commits into
scip-code:mainfrom
olafurpg:no-progress
May 5, 2021
Merged

Remove --no-transfer-progress from Maven command#210
olafurpg merged 2 commits into
scip-code:mainfrom
olafurpg:no-progress

Conversation

@olafurpg

@olafurpg olafurpg commented May 5, 2021

Copy link
Copy Markdown
Contributor

Users can manually add this flag if they want to. This flag got added in
2019 and there are still builds that are using older versions that don't
support this flag. Fixes #208

olafurpg added 2 commits May 5, 2021 13:02
Users can manually add this flag if they want to. This flag got added in
2019 and there are still builds that are using older versions that don't
support this flag. Fixes scip-code#208
To ensure that repeated runs of the `index-semanticdb` command produce
identical results.
@olafurpg olafurpg self-assigned this May 5, 2021
@olafurpg olafurpg merged commit a0c290c into scip-code:main May 5, 2021
@olafurpg olafurpg deleted the no-progress branch May 5, 2021 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stop using --no-transfer-progress option with Maven

1 participant