Version in javadoc links

The change to adding versions to the javadoc link breaks wiki links and should be returned to generic links.

Currently looks like,

should be,

Otherwise every release requires an entire wiki redo.

Currently thats 32 links and 12 pages.

Edit: If this is not possible I can update the links but would be best not to.

Edit: I have to change them to https as it is but didnt know till now they were even changed.

1 Like

what about having a “latest” version?

To me, I think light background with dark text. Easier to read.

The documentation page theme looks sharp btw.

Ok, this is another topic. I made it dark since the forum and the store have dark theme and i thought the home page was going to have it too. I think you can open a poll or something, honestly it’s the same for me.

This is the css that gets injected into the doc when it is generated.

I see, latest version, I dont really care how its worded as long as its static.

Is “latest” master or is “latest” the last alpha/beta release?

Whatever is marked latest in github releases

Which I think means that even if we had a 3.3 final/stable release and someone cut a new 3.2.90 release that it would replace the 3.3 docs.

That’s probably not desirable.

I guess colors are highly opinionated, but from experience documentation should be light background dark text.

I like the forum colors but if I were the rule maker it would all be that way. Store, forum, docs, etc.

Either way, I do believe strongly that the documentation should be a light theme.

Yes you are right. So, how should we solve this now that the doc is updated automatically?
Maybe write some code to detect the higher version number (instead of using the github /latest api)?
Or have something in the wiki (eg. a property or a global variable (not sure what our wiki uses)) to update the links when there is a new release?

Do we build javadoc as part of the master builds?

Maybe just have the wiki point to that?

I don’t know what the process is so I can’t really comment. But in an ideal world, real releases would be marked as such and the docs would either be the latest release (version-wise) or just master.

Edit: and by “marked as such”, I mean that 3.2.5 would be under /3.2.5 and 3.3.0 would be /3.3.0… or if we don’t want to have a ton then just the latest from each branch.

A variable can be set for all links. I can do that in the header of the docs.

I dont know enough about travis or even if travis can can read from other repos like that though.

The variable is localized to the document. So all docs with links to wiki would still require updates, basically still at square one unless travis can do it on commits.

Edit: I can set one variable to update them all I believe. Will have to experiment some.

I added a global attribute and reset all links for wiki contributors.

This is set in the gradle file but can be overridden in the document headers whenever the need arises.

I guess we will just set this whenever with new engine updates.

Seems some other changes were made that I was unaware of.



had the parenthesis changed to -.


Anymore surprises I should be aware of?

I added a global attribute and reset all links for wiki contributors.

This seems like the best solution

Seems some other changes were made that I was unaware of.

The previous javadoc was very old, it was probably generated with java7 or 6. I wasn’t aware of these changes either.

1 Like