![]() Please wait while updating issue type...
Could not save your changes
This issue has been changed since you started editing it
Data that has been changed is highlighted in red below. Undo your changes to see the updated information
You have changed this issue, but haven't saved your changes yet. To save it, press the Save changes button to the right
lolo4j (lolocohen) has been working on this issue since May 11, 2015 (08:11)
This issue is blocking the next release
There are no comments
There is nothing attached to this issue
This issue has no duplicates
There are no code checkins for this issue |
|||||||||||||||||||||||||||||
Really delete this comment?
From my many attempts at finding a solution, I also absoerved that what you propose has its own problems. In particular, the fact that the documentation may signinficantly change between major versions will cause broken links, That's what the current way we're publishing the documntation is attempting to avoid.
To give some backround, the online documentation is a MediaWiki instance customized to fly under the JPPF colors. What I'm thinking of is to automatically add some text to all pages, which would not be rendered and that wxould contain the version number, like:
With this, a Google search including the version may yield more accurate results (currently it doesn't, event though the version is part of the url).
Or, we could use a copy (or redirection) of the /doc/v5 content but with the path /doc/current instead, something like that, and still apply the enhancement above.
Really delete this comment?