Uploaded image for project: 'Apache Taverna'
  1. Apache Taverna
  2. TAVERNA-975

archetype integration tests fail for fresh release



    • Bug
    • Status: Done
    • Minor
    • Resolution: Done
    • engine 3.1.0
    • engine 3.1.0
    • Taverna Engine
    • None


      While building taverna-engine 3.1.0 RC1 with mvn clean install, the build is likely to fail as taverna-activity-archetype has an integration test that generates a dummy activity - this expects other taverna-enigne modules like taverna-workflowmodel-api to be present in the same version (e.g. 3.1.0-incubating).

      However the Maven build reactor does not know about this - and so builds archetype BEFORE those modules - and so they are not present in ~/.m2/repository - and crucially during a [VOTE] of a Release Candidate - neither are they available from Maven Central in that version.

      After the vote has passed, downstream users won't have this problem, as Maven Central will then include the 3.1.0-incubating release of taverna-engine - although this means a bit of silly as mvn will first download the JARs from Maven Central before replacing them with the freshly compiled ones.

      During the 3.1.0 VOTE I propose we recommend building taverna-engine with mvn clean install -Darchetype.test.skip=true to skip the maven-archetype integration test

      (Particularly interested users can then build it another time without the option to run those tests)

      And for 3.2.0 I propose we modify the pom.xml for archetype-plugin to have a <scope>test</scope> dependency in itsown pom.xml, replicating the list of its https://github.com/apache/incubator-taverna-engine/blob/master/taverna-activity-archetype/src/main/resources/archetype-resources/__rootArtifactId__-activity/pom.xml


        Issue Links



              stain Stian Soiland-Reyes
              stain Stian Soiland-Reyes
              0 Vote for this issue
              1 Start watching this issue