On 09/16/2014 01:25 PM, David Roden wrote: > On 16.09.2014, at 05:42, Steve Dougherty <st...@asksteved.com> > wrote: > >> Java artifacts can have minimum Java version requirements. From >> what I've been able to find Java .class files do not have >> standardized "target version" information, so this would need to be >> in the jar MANIFEST. > > Class files do contain major and minor version (see > http://docs.oracle.com/javase/specs/jvms/se7/html/jvms-4.html) of the > target they are compiled for but we probably don’t want to check > every class file for that information.
Ah, okay. It doesn't seem likely to be straightforward to do either. >> Thoughts? > > All in all: that sounds awesome. I’m not sure though whether I fully > understand what is required for the update channel > creator/maintainer; can you give some details on an example > workflow? I'm not sure if this is what you mean, but: 1) build artifacts 2) insert artifacts with signatures 3) ask other signers to verify artifacts and insert signatures 4) insert manifest / definition > Also, is this usable for plugins, too? It seems desirable to have it generic enough to do so, but I'm not sure it's in the initial scope.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
