beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <>
Subject [jira] [Resolved] (BEAM-810) Beam's uses of archetypes are problematic
Date Fri, 02 Dec 2016 19:49:58 GMT


Daniel Halperin resolved BEAM-810.
       Resolution: Information Provided
    Fix Version/s: Not applicable

Information Provided -- issues are known and generally worked around. Some will be solved
only once we have a stable API. This issue can serve as a placeholder with info, but need
not remain open.

> Beam's uses of archetypes are problematic
> -----------------------------------------
>                 Key: BEAM-810
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>    Affects Versions: Not applicable
>            Reporter: Daniel Halperin
>             Fix For: Not applicable
> * 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
> * 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.
> This is all pretty ugly. Suggestions wanted.

This message was sent by Atlassian JIRA

View raw message