beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-810) Beam's uses of archetypes are problematic
Date Mon, 24 Oct 2016 19:29:58 GMT

     [ https://issues.apache.org/jira/browse/BEAM-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Halperin updated BEAM-810:
---------------------------------
    Description: 
* Using a version range in the archetype pom.xml is inaccurate, because we don't have a stable
API. We can't actually expect an older version to work as we make backwards-incompatible changes.

* In PR #936, a decision was made to pin the version of the archetype. This requires manual
changes to update many places (archetype-resources), which breaks the release process in a
few different ways. See [BEAM-806].

* Travis uses `mvn verify`, not `mvn install` -- so archetypes are not properly tested and
instead we're actually picking up the SNAPSHOT archetypes deployed the prior night (IIRC).

* There was some other issue with parallelizing maven where archetypes are not properly marked
as depending on "you can't test the archetype until you've installed the examples packages".

* We're not actually testing that the archetype-generated projects actually compile. [BEAM-641].

This is all pretty ugly. Suggestions wanted.

  was:
1. Using a version range in the archetype pom.xml is inaccurate, because we don't have a stable
API. We can't actually expect an older version to work as we make backwards-incompatible changes.

1. In PR #936, a decision was made to pin the version of the archetype. This requires manual
changes to update many places (archetype-resources), which breaks the release process in a
few different ways. See [BEAM-806].

1. Travis uses `mvn verify`, not `mvn install` -- so archetypes are not properly tested and
instead we're actually picking up the SNAPSHOT archetypes deployed the prior night (IIRC).

1. There was some other issue with parallelizing maven where archetypes are not properly marked
as depending on "you can't test the archetype until you've installed the examples packages".

1. We're not actually testing that the archetype-generated projects actually compile. [BEAM-641].

This is all pretty ugly. Suggestions wanted.


> Beam's uses of archetypes are problematic
> -----------------------------------------
>
>                 Key: BEAM-810
>                 URL: https://issues.apache.org/jira/browse/BEAM-810
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>    Affects Versions: Not applicable
>            Reporter: Daniel Halperin
>
> * Using a version range in the archetype pom.xml is inaccurate, because we don't have
a stable API. We can't actually expect an older version to work as we make backwards-incompatible
changes.
> * In PR #936, a decision was made to pin the version of the archetype. This requires
manual changes to update many places (archetype-resources), which breaks the release process
in a few different ways. See [BEAM-806].
> * Travis uses `mvn verify`, not `mvn install` -- so archetypes are not properly tested
and instead we're actually picking up the SNAPSHOT archetypes deployed the prior night (IIRC).
> * There was some other issue with parallelizing maven where archetypes are not properly
marked as depending on "you can't test the archetype until you've installed the examples packages".
> * We're not actually testing that the archetype-generated projects actually compile.
[BEAM-641].
> This is all pretty ugly. Suggestions wanted.



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

Mime
View raw message