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

[<rya...@jb...>]

Currently, the version metadata is only used when synchronizing, and this only at the toplevel build.  This was purposeful, because I assumed that the toplevel build should have a complete manifest of all versions used in the build, and that there should only be one version of each component used.   

At the component level, you don't need to resolve imported component versions because they have already been specified and downloaded by the toplevel build.  The component uses whatever is in thirdparty/component-id.

If we were using the component definitions to synchronize, we would need to do as you suggest.  What am I missing???

I agree the import mechanism should support a version for the purposes of flagging unmet version requirements.

I'm not working on the import functionality currently.



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

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