[
https://issues.apache.org/jira/browse/BEAM-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846053#comment-16846053
]
Luke Cwik commented on BEAM-2327:
---------------------------------
The task could still apply to Gradle since the naming here:
[https://github.com/apache/beam/blob/74d87274da03044163652b5d740d19dc70c63073/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L407]
is relatively arbitrary.
But I'm going to close it since it is has been open for two years with no
takers and doesn't really improve the project much.
> Name yyy.version properties using the artifactId instead of an arbitrary name
> in all pom.xml
> --------------------------------------------------------------------------------------------
>
> Key: BEAM-2327
> URL: https://issues.apache.org/jira/browse/BEAM-2327
> Project: Beam
> Issue Type: Improvement
> Components: build-system
> Reporter: Luke Cwik
> Priority: Trivial
> Labels: starter
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
