Sorry, i have next to zero knowledge regarding Maven I hope it’s fixed at some point. If everything else fails, you can just copy HistoryExtension,java and historyextension.js
from GitHub to your own project, and everything should work. Remember to put the .js file into the resources package.
That being said,
I updated the add-on to support Vaadin Navigator, which should be pretty helpful to those who want a more ready integration.
The blogpost is still work in progress I need to take another approach on it. Maybe I’ll tackle it tonight…
I just had a quick look and it seems like the 1.1.0 Version works again with Maven while the 1.0.0 version is still not reachable. (If you want it to be up again you might have to republish/reupload it. Disclaimer: I have only 0.000001 knowledge of uploading maven projects, i have more when it comes to downloading them )
When publishing packages that are already in the Maven form (with POM in the META-INF/…, optionally separate -sources and -javadoc JARs etc) Directory uses them as is. If the add-on is not in a Maven compatible form, Directory generates a minimal POM.
There were some problems with this recently affecting a few add-ons, Teemu worked on those and fixed some such cases.
Hi, it would be greate if the NavigationStateManager could degrade internally for Browsers that do not support pushState. http://caniuse.com/#search=pushState
There’s a green button in the download page, you can find a downloadable zip file from there.
You’re right, it would be a nice feature. Unfortunately I don’t have the time/energy to maintain my add-ons anymore, so further development on those is quite unlikely. In case the project gets pull requests, it’d be easier for me to incorporate those changes into a new version, but that’s also, unfortunately, a funnily big effort from my part