mbien commented on PR #5893: URL: https://github.com/apache/netbeans/pull/5893#issuecomment-1544027192
> For local testing, we could also consider making hash check just a warning for local file: URL? That can't accidentally work elsewhere. this would be great. A lot of weird things happened when I tried to *not* use binaries-list for local testing. E.g the build failed because complaining that jars had the same name but different content or something similar. So I ended up writing a script which uploads a jar somewhere so that i can use continue using binaries-list. Ideally I want to point it at the jar in the target folder of a maven project and it should be picked up for local testing. I might be doing something wrong but It never worked properly for me. any ideas for making library upgrades less manual work? https://github.com/apache/netbeans/pull/5679/commits/d7118e8ff41bc27db071aa5a48269e51933706ee this is too much IMO. This all has to be updated manually and someone has to review this too. (speaking of which: a new maven release just went out today. Why does it have to be: properties + xml + binaries-list? Can't it be only the xml for the easy cases? (I understand that a zip is a special case which would require an extra step) I also don't understand why we have to check the hashes of the zip, and then again for every jar. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
