Looks like we might also get some help from [email protected] in cleaning up the build system!
I hope my previous message clarifies why things are the way they are. I don’t know if there are simpler ways to achieve the same effects or if it would be best to abandon some of them. e.g., instead of having the “accurate” auto-generated MANIFEST.MF/Class-Path in the Edgent jars, we could either have a general, include everything, Class-Path or omit Class-Path and require applications to set CLASSPATH themselves. In either case we could provide a manually created & maintained file identifying all of these dependencies. I believe John would like to get to a state where 3rd party dependencies are not included in the convenience binary tgz. And/or eliminate the binary tgz? Ultimately there’s a need to be to generate some bundle that includes the Edgent jars and their external dependencies for download / install onto an edge device. And the app won’t be built on the device. It should be ~easy for an Edgent user to identify and exclude optional Edgent components (the component’s Edgent jar and its deps) from that bundle. — Dale
