Clarify description of JDK Transport modules#1767
Conversation
|
For me also the names and artifactIds are confusing. Should IMHO contain "http". Otherwise it is hard to separate from transport-file (which is jdk/jre only as well). Also not sure about JDK vs JRE. For me this should be rather the latter as this is no feature exclusive to the JDK, so I would propose artifactId Also |
|
We followed the module naming from old Resolver 1.x and I did not want to change them (the GAVs). For naming in POM, I agree but don't find it relevant. Finally, we have 4 transports capable of HTTP, so this will make really long (and hard to distinguish) module names like |
|
Any concerns with just changing the descriptions for now (i.e. merge the PR as is)? |
Following this checklist to help us incorporate your
contribution quickly and easily:
Note that commits might be squashed by a maintainer on merge.
This may not always be possible but is a best-practice.
mvn verifyto make sure basic checks pass.A more thorough check will be performed on your pull request automatically.
mvn -Prun-its verify).If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.