beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Wegner (JIRA)" <j...@apache.org>
Subject [jira] [Created] (BEAM-339) Archetype project version shouldn't be coupled to Beam version
Date Mon, 13 Jun 2016 16:07:20 GMT
Scott Wegner created BEAM-339:
---------------------------------

             Summary: Archetype project version shouldn't be coupled to Beam version
                 Key: BEAM-339
                 URL: https://issues.apache.org/jira/browse/BEAM-339
             Project: Beam
          Issue Type: Bug
          Components: sdk-java-extensions
            Reporter: Scott Wegner
            Assignee: Scott Wegner
            Priority: Minor


tl;dr: The maven-archetype project has a version reference of 0.1-SNAPSHOT. This is for the
user project and shouldn't be tied to Beam versions.
 
In the maven-archetype projects, we have a test which injects property values and verify that
the generated project matches the expected. One of the injected properties is "version", which
is currently set to "0.1-snapshot" to match the Beam project versions. The version property
represents the version of the user project being created and thus shouldn't be tied to the
Beam versioning. We should change it such that the intended usage is more clear and to test
that the version isn't being set from the Beam version.

See: https://github.com/apache/incubator-beam/pull/444/files/ba55042275bd9b525ee8716e4e1007b7924a647f#r66819150



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message