Stefan Bodewig wrote:
On Mon, 05 Jul 2004, Stephen McConnell <[EMAIL PROTECTED]> wrote:
How do we integrate the generated avalon module definition into the gump process?
commit them to the Gump module as you've done for avalon-tools or commit them to the Avalon SVN repo and point the profile to them via http.
The former allows non-Avalon people to tweak them if something goes wrong.
Actually that's not desirable. If something goes wrong it's a issue related to the project definition that magic reads in (for example, a missing dependency). So the principal is .. update the magic definition and from that generate the gump module automatically.
Running the following ant target on build.xml in avalon/truck generates the complete avalon module into a file name gump.xml:
<target name="gump">
<x:home/>
<x:gump description="Magic Test Module"
public="true" filename="gump.xml">
<x:url href="http://avalon.apache.org/"/>
<x:svn repository="avalon-svn" dir="trunk"/>
<x:license file="central/system/license/LICENSE.TXT"/>
</x:gump>
</target>The idea scenario is that gump generates the module using the above after doing the checkout and before computing dependencies.
Stephen.
Stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
