This content has been marked as final. Show 2 replies
So its not an issue to have the imported project using whatever xsd they want, at least for a simple example:
build.xml: <project name="Top" default="echo"> <import file="subproject.xml" /> <target name="echo"> <echo message="top echo" /> <antcall target="subproject-echo" /> </target> </project> subproject.xml <project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="subproject.xsd"> <target name="subproject-echo"> <echo message="echo from subproject" /> </target> </project>
The jbossbuild tools could just be an element in repository.jboss.com with a minimal jbossbuild/bootstrap cvs module to kickstart a project?
Yes, I agree. There are two options here:
1) Make it a cvs module as you suggest. The advantage is that we have this file in one place.
2) Add a bootstrap.xml to each toplevel project's cvs module. The advantage to this is that a project on HEAD can upgrade to a new jbossbuild version at their own pace, instead of being forced to upgrade because another module did so. So the checkout/build cycle would be:
cvs co jbossas cd jbossas ant -f bootstrap.xml ant synchronize ant build