[MGNLTAGS-41] Duplicate i18n keys Created: 12/Jun/14  Updated: 17/Jun/14  Resolved: 17/Jun/14

Status: Closed
Project: Marketing Tags Manager
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.0

Type: Bug Priority: Major
Reporter: Federico Grilli Assignee: Cheng Hu
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLTAGS-42 Make module EE Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Since CE build#4288 triggered by the usage of the newest milestone of magnolia-marketing-tags module, 1.0-m6 during startup Magnolia is logging several warns about duplicate i18n keys.
e.g.

Found duplicate key [marketing-tags.tag-properties.activeAuthor.description] at file [/mgnl-i18n/app-marketing-tags-messages_en.properties].

See full log here http://jenkins.magnolia-cms.com/job/magnolia-bundle_trunk/4288/console



 Comments   
Comment by Cheng Hu [ 17/Jun/14 ]

This issue was most likely caused by renaming the artifact ID of marketing tags and then not changing the artifact ID of the dependency in STK, causing marketing tags to be included twice in the build.

This issue has been solved as a side-effect of removing STK's dependency on marketing tags in a separate issue.

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