[BEAM-2327] Name yyy.version properties using the artifactId instead of an arbitrary name in all pom.xml

• Type: Improvement
• Status: Resolved
• Priority: P4
• Resolution: Abandoned
• Fix Version/s: Not applicable
• Component/s: build-system
• Labels: starter
• Assignee: Unassigned
• Reporter: Luke Cwik
• Created: 19/May/17 15:35
• Updated: 24/Jul/20 20:12
• Resolved: 22/May/19 17:00

Description

Currently we give arbitrary names to properties which store versions of dependencies instead of standardizing on naming like:
artifactId.version

For many of our artifacts this makes sense. There are a few cases where the artifactId should not be used because we are intending to provide a version lock over a set of related packages such as:

• google client libraries
• slf4j