[AVRO-1947] Inconsistent maven profile activation

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8.1
• Fix Version/s: 1.9.0
• Component/s: build, java
• Hadoop Flags: Reviewed
• Assignee: Gabor Szadovszky
• Reporter: Gabor Szadovszky
• Created: 03/Nov/16 16:38
• Updated: 05/Nov/16 20:20
• Resolved: 04/Nov/16 10:28

Description

The profiles hadoop1 and hadoop2 can be activated by setting the property hadoop.version. Currently it is implemented in a way that hadoop2 is activated by default (if the property is not set) and hadoop1 is activated if the property is set to 1. BUT if the property is set to any other value (including 2!) none of these profiles will be activated.

Easily reproducible by using the following commands:

• mvn help:active-profiles
• mvn help:active-profiles -Dhadoop.version=2
• mvn help:active-profiles -Dhadoop.version=1

Issue Links

• links to: GitHub Pull Request #150