[BEAM-2183] Maven-archetypes should depend on all Beam modules that their sources compile against

• Type: Bug
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Component/s: sdk-java-core
• Labels: Done
• Assignee: Dan Halperin
• Reporter: Dan Halperin
• Created: 05/May/17 17:14
• Updated: 06/Oct/20 21:56
• Resolved: 05/May/17 21:17

Description

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.

Issue Links

• links to: GitHub Pull Request #2916