Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
0.2
-
None
Description
As highlighted by Ferdy [0], and subsequently discussed when rolling the 0.2 RC, this issue should be addressed in trunk (0.3-SNAPSHOT) when 0.2 has been released.