[MGNLMIGRATION-93] ftl-Migration: New ftl-code must not come as comment Created: 08/Oct/12  Updated: 29/Mar/13  Resolved: 10/Oct/12

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: None
Affects Version/s: 1.1.3
Fix Version/s: 1.1.4

Type: Improvement Priority: Neutral
Reporter: wolf bubenik Assignee: Cesar Desales
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLMIGRATION-94 ftl-Migration: incorrect replacement ... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Actually old ftl code and suggested replacements will be inserted as comments. Having the old ftl- code as comment is very useful but the new ftl replacements will almost always be accepted. It would save a lot of work if we must not touch every ftl file just to so the result of migration.



 Comments   
Comment by Lars Fischer [ 10/Oct/12 ]

It's useful but nice to have so we'll postpone it.

Comment by Cesar Desales [ 10/Oct/12 ]

Nesting of comment tags is a potential source of FTL syntax problems, therefore comments have been removed from new FTL code.

Comment by Jan Haderka [ 29/Mar/13 ]

Closing all issues resolved and released in 1.1.x versions w/o further review. (current latest version is 1.2.2)

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