-
15. Re: New Build - Standalone module - multiple builds
"ryan.campbell@jboss.com" wrote:
1. Iterate over all the jars in a release, collecting the component id & version from each jar manifest.
This assumes we add the compoent id to the manifest. -
16. Re: New Build - Standalone module - multiple builds
* This does not address non-archive artifacts, such as text files. We would need to add "manifests" to these text files if we wanted to be able to resolve their source components. Is this necessary for this use case (or in general)?
No. In general configuration files will have no mapping to the dist as they will have been customized. I'm really only interested in being able to reproduce the same binaries from source for support.