Didier Loiseau created MRESOLVER-602:
----------------------------------------

             Summary: Documentation for aether.priority.<class> has disappeared
                 Key: MRESOLVER-602
                 URL: https://issues.apache.org/jira/browse/MRESOLVER-602
             Project: Maven Resolver
          Issue Type: Bug
          Components: Resolver
    Affects Versions: 2.0.1
            Reporter: Didier Loiseau


Property {{aether.priority.<class>}} is not documented any more [in v2.0.1 of 
the 
documentation|https://maven.apache.org/resolver-archives/resolver-2.0.1/configuration.html],
 but it was [in version 
1.9|https://maven.apache.org/resolver-archives/resolver-1.9.22/configuration.html].

This change appears to be coming from commit 
[7318c95|https://github.com/apache/maven-resolver/commit/7318c95ae28df9a49d962a1a2c748d628f512ae2]
 which has regenerated the documentation (according to commit message).

Note that the previous documentation was not very good already, since it did 
not give any pointers to what are the possible {{<class>}} values, nor what 
kind of values it expects:
{quote}The priority to use for a certain extension class. {{class}} can either 
be the fully qualified name or the simple name stands for fully qualified class 
name. If the class name ends with {{Factory}} that suffix could optionally be 
left out.
{quote}
For resolver 1.9, I found some possible values 
[here|https://github.com/apache/maven/blob/a98d530e338b54dadefc45b37c40094a84d12ae7/maven-core/src/main/java/org/apache/maven/internal/aether/DefaultRepositorySystemSessionFactory.java#L111-L117],
 more specifically {{WagonTransporterFactory}} has a default priority of -1 and 
{{HttpTransporterFactory}} has 5 (more transporters are available in 
maven-resolver 2.x). I also found that {{DefaultTransporterProvider}} will log 
the used transporter class name when running maven with {{{}-X{}}}, using a 
message like
{quote}Using transporter WagonTransporter with priority 1000.0
{quote}
Expected values appear to be float numbers.

I didn’t check if other properties are missing (I wouldn’t know if they are 
still be relevant in 2.x anyway).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to