[Jboss-dev-forums] [Design of JBoss Build System] - Re: Build Repository Structure

[<sco...@jb...>]

Right, assuming by manifest you mean the repository component-info.xml import statements?

We do need to figure out to handle the multiple version mismatches that will show up. As part of generating the license-info.xml from the thirdparty repository references, detection of version conflicts will be flagged. That should in fact be a custom cruisecontrol action that results in an email to qa and the development list. Maybe its best to require the version on component-info.xml import statements rather than trying to default to the latest to start with in the absence of such info to start with.

As you say I don't see any magic resolution. There needs to be testing and lead on the component using the older version consulted to see if the changes look to be problematic. This gets back to exactly what should be in the thirdparty repository. Release notes, source and patches would seem to be a good minimum in addition to the binaries.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877406#3877406

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877406