[TAVERNA-569] Each activity needs its own version number parameter

• Type: Bug
• Status: To Do
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Stian Soiland-Reyes
• Created: 18/Jun/14 15:56
• Updated: 28/Apr/15 11:42

Description

Now that activities no longer need to be updated every time Taverna is the are allowed to differ in version numbers.

Therefor <t2.activities.version> in
https://github.com/taverna/taverna-maven-parent/blob/maintenance/pom.xml

Needs to be split into different parameter for each activity.

Issue Links

• relates to: TAVERNA-567 Activity poms can no longer use ${project.version}