You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by "Stian Soiland-Reyes (JIRA)" <ji...@apache.org> on 2016/05/31 15:31:12 UTC
[jira] [Updated] (TAVERNA-975) archetype integration tests fail for
fresh release
[ https://issues.apache.org/jira/browse/TAVERNA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stian Soiland-Reyes updated TAVERNA-975:
----------------------------------------
Description:
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|http://maven.apache.org/archetype/maven-archetype-plugin/integration-test-mojo.html]
(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
was:
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 with {{mvn clean install -Darchetype.test.skip=true}} to skip the [maven-archetype integration test|http://maven.apache.org/archetype/maven-archetype-plugin/integration-test-mojo.html]
(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
> archetype integration tests fail for fresh release
> --------------------------------------------------
>
> Key: TAVERNA-975
> URL: https://issues.apache.org/jira/browse/TAVERNA-975
> Project: Apache Taverna
> Issue Type: Bug
> Components: Taverna Engine
> Affects Versions: engine 3.1.0
> Reporter: Stian Soiland-Reyes
> Assignee: Stian Soiland-Reyes
> Priority: Minor
> Fix For: engine 3.2.0
>
>
> 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|http://maven.apache.org/archetype/maven-archetype-plugin/integration-test-mojo.html]
> (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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)