Radai Rosenblatt opened MNG-5600 and commented

suppose i have a multi-module project that uses spring, and so have this in dependency-managements in a parent pom:

<dependency>
	<groupId>org.springframework</groupId>
	<artifactId>spring-framework-bom</artifactId>
	<version>${org.springframework.version}</version>
	<type>pom</type>
	<scope>import</scope>	
</dependency>

spring artifacts (or at least a lot of them) have a dependency on commons-logging. right now, if i want to exclude commons-logging i have to add an exclusion to every spring dependency in every module of my project, which is actually more XML overall than giving up on using the bom dependency altogether and listing all spring dependencies with excludes once in the parent dependency management.

I'd like to be able to do this:

<dependency>
	<groupId>org.springframework</groupId>
	<artifactId>spring-framework-bom</artifactId>
	<version>${org.springframework.version}</version>
	<type>pom</type>
	<scope>import</scope>
	<exclusions>
		<exclusion>
			<artifactId>commons-logging</artifactId>
			<groupId>commons-logging</groupId>
		</exclusion>
	</exclusions>
</dependency>

Issue Links:

• MNG-1977 Global dependency exclusions

• MNG-7843 Allow glob patterns in dependency exclusions

• MNG-5227 The 'optional' flag of a dependency should be manageable.

Remote Links:

• Page
  
• GitHub Pull Request #30
  
• GitHub Pull Request #133
  
• GitHub Pull Request #148
  
• GitHub Pull Request #269
  
• GitHub Pull Request #30
  
• GitHub Pull Request #59
  
• GitHub Pull Request #1155
  
• GitHub Pull Request #133
  
• GitHub Pull Request #148
  
• GitHub Pull Request #295
  

Backported to: 4.0.0-alpha-7

20 votes, 36 watchers