"[EMAIL PROTECTED]" wrote : One issue that is not clear in this discussion is do I have sufficient info to go obtain the source for every jar I find in the dist? Ultimately I want this for patches as well. The ideal roundtrip behavior is that I would point a ant task to a release and have it spit out the jboss-build.xml that would obtain the source and thirdparty repository to rebuild the possibly patched dist. |
Right, you might have a distribution which has potentially reflects multiple patches, and now you want the source for this distribution. I think this is possible with the current design. How it would work: 1. Iterate over all the jars in a release, collecting the component id & version from each jar manifest. 2. Verify there are no conflicts between jars. IE, jboss-common.jar and jboss-common-client.jar must agree on their version. Otherwise, the source is not resolvable. 3. Based on the above, you have enough information to create a toplevel build. * 4. Upon calling synchronize for this toplevel build, the component id's and versions will be used to resolve the component-info from the build repository. 5. The component-info will contain the cvsroot, module, and tags for each component. These data will then be used to checkout the source for each component. * 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)? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874116#3874116 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874116 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
