From: <sco...@jb...> - 2005-05-04 03:00:36
|
I have been through the current build-reference.html doc and I'm finding an overall description of the build structure of a project in terms of what the directory structure needs to be, what types of build descriptors there are, what are there content models etc. to be missing. So I want a more top down doc that describes this. Some current issues: - Why is all of the tools module being used? This is largely legacy stuff and includes extraneous stuff like cruisecontrol configuration. The jbossbuild tools could just be an element in repository.jboss.comwith a minimal jbossbuild/bootstrap cvs module to kickstart a project? - The use of the ant project document structure for the different types of build descriptors (build.xml, component-info.xml, etc.) gets us into a problem with non-validatable documents. I'm sure this is due to leveraging the ant import mechanism, but ant does have a notion of namespaces, but I'm not sure if this applies to the project element on imported references. Have we looked into that? Ideally each different build descriptor type would have its own xsd. If we can't actually do this, we at least need xsds for the various build descriptors as a reference to what the allowed content models are. I want to help get this stuff documented as a first time user of the build system to ensure we get it adopted as soon as possible. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876374#3876374 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876374 |