[MGNLWORKFLOW-241] resourcePath should start with leading slash Created: 23/May/14  Updated: 05/Jun/14  Resolved: 05/Jun/14

Status: Closed
Project: Magnolia Workflow Module
Component/s: None
Affects Version/s: 5.4
Fix Version/s: 5.4

Type: Improvement Priority: Minor
Reporter: Natascha Desmarais Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 5.3-m4
workflow 5.4-m2


Attachments: PNG File Screen Shot 2014-05-23 at 3.09.56 PM.png    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

To ensure the consistency with other mechanisms in place already (e.g. in templating, templateScript property), the resourcePath pointing to the BPMN definition should start with a leading slash.



 Comments   
Comment by Espen Jervidalo [ 05/Jun/14 ]

The leading slash in the resource path is removed in info.magnolia.cms.util.ClasspathResourcesUtil#getResource

So the configuration supports both. Apart from this it has been like this since version 5.0. I don't see much benefit in this change. Feel free to re-open, but it won't go in to 5.4 final for now.

Generated at Mon Feb 12 10:08:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.