jboss / maven-dependency-management-extension Goto Github PK

I would like to have the ability to, in the remote BOM, specify:

<properties>
        <version.org.infinispan.6>6.0.0.Final-redhat-2</version.org.infinispan.6>
</properties>

This should be read by the extension and those properties should then override any existing properties in the model. This would be extremely useful for us for

• Overriding project properties that use non-standard version formats.
• Populating the model with extra versions for when projects have two group:artifact that are the same but with different versions (See #10 ) : one could be aligned, while the other utilises the property.

It would be really helpful to have a property injected that corresponded to each dependency version this extension injects. Something with a predictable naming convention, which would allow projects to use the injected versions for filtering resources and in plugin configurations.

For instance, VMan (https://github.com/jdcasey/pom-version-manipulator) injects a property of the format:

"version." + groupId + '-' + artifactId

Currently there is
https://github.com/jboss/maven-dependency-management-extension#overriding-dependency-versions-of-a-specific-module
to override dependencies on a per module basis. However, it would be useful to block modules from being overridden. This avoids having to pass explicit versions on the command line. So we might do

mvn install -Dversion:junit:[email protected]:moduleB=

and in DepVersionOverrider::applyOverrides if the version is not set, the module would not be aligned. However if we did

mvn install -DdependencyManagement=org.foo:my-dep-pom:1.0  -Dversion:junit:[email protected]:moduleB=

org.foo.moduleA would be aligned (assuming the remote bom contains junit).

What steps will reproduce the issue?

1. Open the IntelliJ IDEA ULTIMATE 2021.3.1 (Build #IU-213.6461.79)
2. Have installed the Maven Dependency manager
3. Observe the exception thrown by the IDE

What is the expected result?
Maven dependency manager should work without throwing exceptions at IDE level.

What happens instead?
This stack trace is thrown and this affects the plugin ability to work properly.

stacktrace.txt

Please solve it...

Should the extension log exceptions as warnings (e.g. in loadRemoteDepVersionOverrides) or allow them to be propagated out and fail the Maven build) ?

When the extension is declared in the POM (instead of in the lib/ext directory), it fails when using Maven 3.1 or higher. This appears to be a classpath issue:
[WARNING] Error injecting: org.jboss.maven.extension.dependency.DependencyManagementLifecycleParticipant
java.lang.NoClassDefFoundError: Lorg/sonatype/aether/impl/ArtifactResolver;

The problem can be seen in the pom declaration integration test.

I would like to override a plugin version when building on my local machine. This works on the command line:

 mvn compile -DpluginVersion:org.codehaus.groovy:groovy-eclipse-compiler=2.9.0-01-SNAPSHOT

but this is not legal XML for ~/.m2/settings.xml because of the need for colons in the element name:

  <properties>
    <pluginVersion:org.codehaus.groovy:groovy-eclipse-compiler>2.9.0-01-SNAPSHOT</pluginVersion:org.codehaus.groovy:groovy-eclipse-compiler>
  </properties>

Could you please provide an alternative syntax where the property names are legal in XML?

When using a plugin which has optional dependencies, it would be useful to override the versions of those dependencies.

For instance, see the Groovy-Eclipse compiler plugin for Maven, which uses a dependency declaration to specify which version of groovy-eclipse-compiler to use with maven-compiler-plugin.