You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by dhalperi <gi...@git.apache.org> on 2016/12/28 22:52:02 UTC

[GitHub] beam pull request #1713: [BEAM-1227] Update archetype pom.xml to non-incubat...

GitHub user dhalperi opened a pull request:

    https://github.com/apache/beam/pull/1713

    [BEAM-1227] Update archetype pom.xml to non-incubating release

    R: @jbonofre 
    
    Since `mvn versions:set` does not update archetype pom.xml files, and we need to pin the archetype version pre-stable-api, need to do this manually every release.
    
    The new release will be called `0.4.0` with no incubating.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dhalperi/beam patch-release-0.4.0-3

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/beam/pull/1713.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1713
    
----
commit 6735ab6d1a96574e58611a1221fc685f6735a09c
Author: Dan Halperin <dh...@google.com>
Date:   2016-12-28T22:48:12Z

    Update archetype pom.xml to non-incubating release

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] beam pull request #1713: [BEAM-1227] Update archetype pom.xml to non-incubat...

Posted by dhalperi <gi...@git.apache.org>.
Github user dhalperi closed the pull request at:

    https://github.com/apache/beam/pull/1713


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---