Version 1.17 will require java 17

[EricBerendsen]

Early warning; the next release of DVB Inspector (1.17) will require java 17. I know this may inconvenience some users, as some people may not have the admin rights to install a new version of Java, or Java 17 may not yet be available for their OS (Raspberry Pi ?). I am sorry about that.

I have two main goals when working on DVB Inspector; learning about DVB and learning about new features of Java. I think there are enough new features in Java 17 to justify upgrading to this new version.

[jimbo2018]

I cannot get this program to work whatsoever. I have a downloaded file of the SI tables but cannot read them.

I downloaded your program. The jar file will not work despite it being in the correct directory. The bat file does not work either as all that does is flash the command prompt for a quarter ofa second and disappear.

All I want is to be able to read the SI tables. How can I do this on a Windows 10 machine when this will only work on linux? Thank you.

[EricBerendsen]

DVB Inspector can run on Windows 10. Do you have java (11 or higher) installed? One option to start is double click the DVBinspector-1.16.1.jar file. (Not the DVBinspector.jar)

You could also try to execute dvb.bat from inside a command shell. Then any error will not disappear.

[lars18th]

Hi @EricBerendsen ,

In any case, could you provide please a nightly build of the last version? Or provide a "Beta" or "Release Candidate"? I can't compile the current master tree and I want to check if it runs in my Windows 10 machine.

Thank you.

[EricBerendsen]

Hi @lars18th

Please find a snapshot at https://www.digitalekabeltelevisie.nl/dvb_inspector/img/DVBinspector-1.17.0-SNAPSHOT-dist.zip

DVB Inspector should be pretty easy to build, if you have Java 17 and maven installed. See https://www.digitalekabeltelevisie.nl/dvb_inspector/building.shtml

Any specific problems I might help with?

[lars18th]

Nice! This snapshot works without changes in my Win10 x64 with Oracle Java installed on it. So plug&play. 😉

Regarding the compilation, I hate to "install" innecessary software in my computer (and I like Portable software). So I prefer to not install toolchains and IDEs that I don't need to use every day (I prefer to compile in Linux boxes). So my suggestion is to compile your tool with a Docker Container and share the image. Then we can use it to compile the snapshot. Or if you prefer, publish some snapshot time to time (like now). The latter from my point of view is the simplest and preferable.

Regards.

[EricBerendsen]

To run DVB inspector you need to install Java anyway. So the only extra tool you need is maven.

Don't think using Docker is going to make my (or casual users) life any easier, not planning on doing that.

I should try to do a release more often, but in between you can have a look at the Actions tab , for any commit it will trigger a build. At the bottom of the results page like this it will have a Artifacts section;

You can download that snapshot. Disadvantage, GitHub will only keep that snapshot for I think 30 days, after that it is removed. So if there have not been any commits in 30 days there is no snapshot

[lars18th]

Great! From my point of view this is a nice solution. But in any case, if you publish a Release Candidate when in the last month (or two months) you've done some commits, then it will be more than sufficient. You agree?