As a user, I can launch the activation workflow so that I can do the review process
(MGNLWORKFLOW-43)
|
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 5.0 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Daniel Lipp | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Sprint: | Alpha 3, Iteration 2013-12, Iteration 2013-13, Iteration 2013-14, Iteration 2013-15, Iteration 2013-16 |
| Description |
|
magnolia_main and magnolia_ui modules have different lifecycle - hence we have to use two separate properties for those versions in our poms:
<magnoliaVersion>5.0-SNAPSHOT</magnoliaVersion>
<magnoliaUiVersion>5.0-SNAPSHOT</magnoliaUiVersion>
Workflow pom currently only defines the first of these properties but uses it as version for ui modules - that's wrong:
<dependency>
<groupId>info.magnolia</groupId>
<artifactId>magnolia-core</artifactId>
<version>${magnoliaVersion}</version>
</dependency>
<dependency>
<groupId>info.magnolia.ui</groupId>
<artifactId>magnolia-ui-model</artifactId>
<version>${magnoliaVersion}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>info.magnolia.ui</groupId>
<artifactId>magnolia-ui-admincentral</artifactId>
<version>${magnoliaVersion}</version>
<scope>provided</scope>
</dependency>
|