That is certainly possible, but it probably has the drawback that it makes the jar file very much bigger.
A rise in size from say 60KB to well over 2MB is no exception.
Besides: when I did that the first time I had the problem that this HTML file, stored as a resource, could easily be launched when the application was run in NetBeans, but not when the app was run as a jar file.
I solved it, more or less, by having the jar file and the html file in the same map, but as two different files. That had some advantages:
1) the help file could be launched separately, just by double clicking
2) the user can store the jar and the help file at any location fit
3) in my jar file, the main file did two things: determine the map it is stored in, and second, it started the real application, giving the path as a parameter. The application could then launch the html file as usual, to whatever browser the user had figured as standard.
4) I explained this situation in a very small ReadMe file.
I know, it was in my
java beginning period, so I did not know any better, but I always found this way of doing satisfying. Agreed, the user base was me and at best some direct family...
