Added ability to provide arbitrary dependencies to properties mojo

[treilhes]

This PR allows providing arbitrary dependencies to project properties through the plugin’s declared dependencies.
My main use case for this feature is the ability to patch a Java module with a dependency that is outside of the project’s dependency tree (mainly to solve duplicate package name).

See sample below

    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-dependency-plugin</artifactId>
                <executions>
                    <execution>
                        <id>resolve-jar-path</id>
                        <goals>
                            <goal>properties</goal>
                        </goals>
                    </execution>
                </executions>
                <dependencies>
                    <dependency>
                        <groupId>com.somegroup</groupId>
                        <artifactId>someartifact</artifactId>
                        <version>someversion</version>
                    </dependency>
                </dependencies>
            </plugin>

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <compilerArgs>
                        <arg>--patch-module</arg>
                        <arg>module.to.patch=${com.somegroup:someartifact:jar}</arg>
                    </compilerArgs>
                </configuration>
            </plugin>
        </plugins>
    </build>

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

[desruisseaux]

It seems related to #1560, maybe a replacement?

[treilhes]

@desruisseaux
It is the same content you can safely forget about #1560

[slawekjaranowski]

I think that adding artifacts to plugin dependencies is not good idea ...
it will be added to plugin classpath - that is not needed.

I would prefer add a new parameters for additional artifact, next artifact can be resolved and file path can be added to properties

[github-actions]

This pull request is stale because it has been waiting for feedback for 60 days. Remove the stale label or comment on this PR, or it will be automatically closed in 30 days.

[treilhes]

Hello @slawekjaranowski

Updated as requested, now you may use the plugin as follow:

    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-dependency-plugin</artifactId>
                <executions>
                    <execution>
                        <id>resolve-jar-path</id>
                        <goals>
                            <goal>properties</goal>
                        </goals>
                    </execution>
                </executions>
                <configuration>
                    <extraArtifacts>
                        <extraArtifact>
                            <groupId>com.somegroup</groupId>
                            <artifactId>someartifact</artifactId>
                            <version>someversion</version>
                        </extraArtifact>
                    </extraArtifacts>
                </configuration>
            </plugin>

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <compilerArgs>
                        <arg>--patch-module</arg>
                        <arg>module.to.patch=${com.somegroup:someartifact:jar}</arg>
                    </compilerArgs>
                </configuration>
            </plugin>
        </plugins>
    </build>

[slawekjaranowski]

@treilhes thanks