van-vliet commented on pull request #133: URL: https://github.com/apache/maven-dependency-plugin/pull/133#issuecomment-852882664
@michael-o I am not sure how to describe the cruciality to you. I can describe the impact of not seeing this change released: My colleagues and I have a couple of projects that encounter this issue. Without an official release, we have the following options: 1. Change our CI pipeline so it does not use go-offline 1. Re-release dependencies that have a classifier with a new name and no classifier 1. Release a forked version of the maven-dependency-plugin and use that in our CI pipeline. Option 1 is a huge task that will affect all of our builds and will require a lot of work. Option 2 is possible since we have only seen this issue with a single dependency so far. Version bumps and other dependencies with classifiers will make this option unsustainable in the long term. Option 3 would fix the issue, but would require maintenance until we can switch back to an official release. We have no interest in maintaining a fork with just a single bugfix. Neither options are good for us. They all require a significant amount of effort to implement. Without an official release, we implement the least effort workaround, which is probably is option 3. [MDEP-739](https://issues.apache.org/jira/projects/MDEP/issues/MDEP-739?filter=allopenissues) was reported by someone else, so at least one other person has encountered the issue and would benefit from the change. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
