[
https://issues.apache.org/jira/browse/CLK-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812301#comment-13812301
]
Adrian A. commented on CLK-796:
-------------------------------
> adding click-version into click-control.properties solves problem
I'm not sure that I understand your problem.
{{click-version}} property belongs to {{click-control.properties}} since 2008
(~click-1.4RC3) already.
When making your own customized version of {{click-control.properties}} , the
documentation mentions:
{quote}
Note when customizing the message properties you must include all the
properties, not just the ones you want to override.
{quote}
so users should always include *all* properties there.
Of course, it would be smarter from Click's side to use for version a different
file, since it's of no use to override this property.
> missing click-version in click-control.properties example
> ---------------------------------------------------------
>
> Key: CLK-796
> URL: https://issues.apache.org/jira/browse/CLK-796
> Project: Click
> Issue Type: Brainstorming
> Components: core, documentation
> Affects Versions: 2.3.0
> Reporter: Roman Korsun
> Priority: Trivial
>
> When step by step follow documentation
> http://click.apache.org/docs/user-guide/html/ch03s04.html
> 1) copy and paste messages to new /click-control.properties file
> 2) build and deploy... then application failed to start with strange errors
> in console
> reason can be found from local tomcat log
> at org.apache.click.util.ClickUtils.getClickVersion(ClickUtils.java:1285)
> adding click-version into click-control.properties solves problem
--
This message was sent by Atlassian JIRA
(v6.1#6144)
