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

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

So we need to finalize the repository structure and component-info so I can recreate the jboss-4.0.x thirdparty contents from a jbossbuild.xml.

One current issue is the license info. The existing jboss-4.0/thirdparty/licenses/thirdparty-licenses.xml now has an index of the licenses used along with the acceptable source code headers used in the codebase to reference the license. The latter is used by the org.jboss.tools.license.ValidateLicenseHeaders utility to run across every source file in the codebase to validate that a license header exists, and that it maps to an acceptable license.

So the first change that needs to be made to the repository structure is to pull out all license files from the component dirs into a repository/licenses structure so that there is a canonical representation of the licenses in use. When I look at a licenseType="apache-2.0" reference from a component-info.xml, its a reference to either repository/licenes/apache-2.0 contents, or a reference to an element in a single repository/licenes/license-info.xml element not unlike the current thirdparty-licenses.xml licenses section:


  | <licenses>
  |       <license id="apache-1.1" licenseFile="apache-1.1.txt">
  |          <terms-header id="apache#0">
  |           * The Apache Software License, Version 1.1
  | ...
  | 

I would lean towards a single repository/licenes/license-info.xml with the license text in repository/licenes as currently is done in jboss-4.0/thirdparty/licenses.

I have some general questions about the overall build structure relationships and xml descriptors format that I'll create a seperate post on.


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

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