Luca, I just downloaded and unpacked build #376 with no problems. I wouldn't run NetBeans if the "archive is corrupt". Try downloading again.
The module errors you are seeing on startup might be an unrelated issue. I used to get a "..*could not start some modules...*" message when starting NetBeans from a fresh download, but now avoid it by deleting the user directory and cache directory before starting NetBeans for the first time from a fresh download. This ensures you get a completely clean start with a new build. Just do *Help -> About *in NetBeans to get the names of those two directories before downloading a new build. For me, on Windows those two directories are named as follows, though obviously yours won't be identical: - *User directory:* C:\Users\johndoe\AppData\Roaming\NetBeans\dev - *Cache directory:* C:\Users\johndoe\AppData\Local\NetBeans\Cache\dev Rick On Sat, Mar 24, 2018 at 6:19 AM, Luca Mambretti <[email protected]> wrote: > While downloading and unpacking the latest dev version I got warnings that > some files were corrupted: > > NetBeans-dev-incubator-netbeans-linux-376-on-20180323-basic.zip: Checksum > error in netbeans\ide\modules\org-netbeans-modules-code-analysis.jar. The > file is corrupt > NetBeans-dev-incubator-netbeans-linux-376-on-20180323-basic.zip: Checksum > error in netbeans\java\modules\ext\jaxws22\gmbal-api-only.jar. The file > is corrupt > NetBeans-dev-incubator-netbeans-linux-376-on-20180323-basic.zip: Checksum > error in netbeans\javafx\modules\org-netbeans-modules-javafx2-samples.jar. > The file is corrupt > NetBeans-dev-incubator-netbeans-linux-376-on-20180323-basic.zip: The > archive is corrupt > > The IDE starts anyway but with module errors most probably caused by the > missing/corrupt files. > > Is anyone else seeing something similar?? > > Regards > Luca. >
