beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davor Bonaci (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-641) Need to test the generated archetypes projects
Date Mon, 14 Nov 2016 18:12:58 GMT

    [ https://issues.apache.org/jira/browse/BEAM-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664581#comment-15664581
] 

Davor Bonaci commented on BEAM-641:
-----------------------------------

We should double-check this -- I believe this is already bound properly to the "install" phase
of the top-level build.

> Need to test the generated archetypes projects
> ----------------------------------------------
>
>                 Key: BEAM-641
>                 URL: https://issues.apache.org/jira/browse/BEAM-641
>             Project: Beam
>          Issue Type: Test
>          Components: testing
>            Reporter: Pei He
>            Assignee: Pei He
>            Priority: Critical
>             Fix For: 0.4.0-incubating
>
>
> Travis and Jenkins pre-submits don't test building the generated archetypes projects.
> Currently, changes to archetypes have to be manually verified by:
> mvn archetype:generate \
> -DarchetypeArtifactId=beam-sdks-java-maven-archetypes-examples \
> -DarchetypeGroupId=org.apache.beam \
> -DarchetypeVersion=0.3.0-incubating-SNAPSHOT \
> -DgroupId=com.example \
> -DartifactId=first-beam \
> -Dversion="0.3.0-incubating-SNAPSHOT" \
> -DinteractiveMode=false \
> -Dpackage=org.apache.beam.examples
> and did "mvn clean install" in first-beam project.



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

Mime
View raw message