[TEXEN-17] Default properties of Generator are processed differently than the propertie file(s) given in the Ant-task

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.1
• Fix Version/s: 1.1
• Labels: properties texen
• Assignee: Unassigned
• Reporter: Fedor Jutte
• Created: 29/Mar/10 16:14
• Updated: 30/Mar/10 16:34

Description

The TexenTask uses TexenUtils.populateContext() to populate the context.
Instead of reusing TexenUtils.populateContext(), Generator.fillContextProperties() uses it's own, slightly different, algorithm to fill the context with it's default properties.

Difference:
TexenUtils.populateContext() provides additional support for entries like "license.file.contents = license.txt", but Generator.fillContextProperties() doesn't.
Generator.fillContextProperties() provides additional supports for entries like "context.objects.strings=org.apache.velocity.util.StringUtils", but TexenUtils.populateContext() doesn't.

SOLUTION:
Instead of giving Generator.fillContextProperties() it's own algorithm, it should use TexenUtils.populateContext(). And the additional support for objects in Generator.fillContextProperties() should be added to TexenUtils.populateContext().