beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-2183) Maven-archetypes should depend on all Beam modules that their sources compile against
Date Fri, 05 May 2017 21:11:04 GMT

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

ASF GitHub Bot commented on BEAM-2183:
--------------------------------------

Github user asfgit closed the pull request at:

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


> Maven-archetypes should depend on all Beam modules that their sources compile against
> -------------------------------------------------------------------------------------
>
>                 Key: BEAM-2183
>                 URL: https://issues.apache.org/jira/browse/BEAM-2183
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Daniel Halperin
>            Assignee: Daniel Halperin
>             Fix For: First stable release
>
>
> The archetypes in {{sdks/java/maven-archetypes/*}} compile and run tests for source code
that depends on various Beam modules. The dependencies are reflected in the *inner* pom.xml
inside {{src/main/resources/archetype-resources/pom.xml}}.
> The outer module needs to have the same Beam dependencies to force the Maven Reactor
build order to process those modules first. Otherwise, a simple run of {{mvn install}} (e.g.,)
, even without parallelism, may run the {{maven-archetypes}} step before it install the dependent
modules. This means that the code may run against a previous nightly snapshot or other non-up-to-date-copy
of those modules.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message