You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When you run your maven build and use a local maven repo at a non-standard location (not ~/.m2/repository), then dokka-maven-plugin still downloads dependencies there. If you want to keep your dependencies separate, that's not possible then.
Expected behaviour
When Maven is configured or instructed to use a specific location for the local maven repository, then the default local repo location should not be modified.
To Reproduce
A maven project with the dokka-maven-plugin added
clear your default local maven repo location (e.g. mv ~/.m2/repository ~/.m2/repository-old)
run mvn clean verify -Dmaven.repo.local=$(pwd)/m2repo
Now all dependencies should be placed into ./m2repo and ~/.m2/repository should not exist.
Describe the bug
When you run your maven build and use a local maven repo at a non-standard location (not
~/.m2/repository
), then dokka-maven-plugin still downloads dependencies there. If you want to keep your dependencies separate, that's not possible then.Expected behaviour
When Maven is configured or instructed to use a specific location for the local maven repository, then the default local repo location should not be modified.
To Reproduce
mv ~/.m2/repository ~/.m2/repository-old
)mvn clean verify -Dmaven.repo.local=$(pwd)/m2repo
Now all dependencies should be placed into
./m2repo
and~/.m2/repository
should not exist.Dokka configuration
Installation
Additional context
The path
~/.m2/repository
seems to be hard coded here:dokka/runners/maven-plugin/src/main/kotlin/DokkaMojo.kt
Line 268 in eba2508
The text was updated successfully, but these errors were encountered: