[
https://issues.apache.org/jira/browse/JEXL-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732910#action_12732910
]
Henri Biestro commented on JEXL-43:
-----------------------------------
I guess I can't just create a patch on xdocs/index.xml as a starting point
since there is a catch-22 on a "site" issue (aka we have to commit it before
release but can't expose it before it is released), How should I proceed ? Is
there any common procedure to update index.xml? Something like create a new
index-2.0.xml & somehow have a directive that instructs which index-xx.xml to
use to produce index.html on the site (which would be the last action for
release).
Where should the list of features appear (&highlight for new ones)? I guess
the JIRA derivable info is not going to cut it (wouldn't to me if I was
discoverng the project...).. Should that be in a javadoc (package.html) ?
Much guidance needed here.
> Website overview does not mention method calls and new 2.0 features
> -------------------------------------------------------------------
>
> Key: JEXL-43
> URL: https://issues.apache.org/jira/browse/JEXL-43
> Project: Commons JEXL
> Issue Type: Improvement
> Affects Versions: 1.1
> Reporter: Sebb
> Priority: Minor
> Fix For: 2.0
>
>
> The website overview of language syntax does not mention method calls.
> It would be helpful if a simple method call was documented; for more
> information, the reader could be directed to the "Reference" section.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
