Hi Gregg,
Gregg Wonderly wrote:
Mark Brouwer wrote:
Hi Jim,
There is a link to Roadmap, see
http://issues.apache.org/jira/browse/RIVER?report=com.atlassian.jira.plugin.system.project:roadmap-panel
for all the closed and open issues
I went and looked at this link, and there is good information visible
here. I looked through the issues, and was wondering about River-203
and why / can't always be recognized on windows. I regularly do not use
${/} because of the complete clutter in readability it causes. At this
point, it is a non-changable historical artifact that / is equal to \ on
windows. There are so many places where that can't be "fixed" as in
".properties" files and manifest files etc.
This would really make peoples life easier I think...
I take that as you disagree with my reasoning not to fix it ;-) ? I
mentioned while working through all issues related to the tools that it
didn't require fixing. See my response below:
"With regard to RIVER-230 I'm wondering whether the request for
improvement is "a good thing", given the fact that ClassDep specifies
Platform specific classpaths and file paths. I don't think we should
take 'advantage' of the fact Java also accepts the wrong file separator
for the Windows platform. I believe that Ant can provide the proper
abstraction layer so you won't run into any problems as the build files
of the River project show, or that other Ant tasks on top of ClassDep
provide. Personally I would like to close RIVER-203 as "Won't fix", but
maybe I'm missing something, so please shoot if my reasoning is wrong."
Nobody responded so I closed it ultimately as I believe there are better
ways to arrange for portability, nevertheless if somebody can and wants
to fix this AFAIC he/she is free to fix it.
--
Mark
