I imagine for the gump people the below is as hard to read as it was for me. Spend some time on ICQ with Steve trying to figure out what he's on about. Basically he's whipped up a rather extensive object model (much more so than gump or maven), a superset of gumps object model.

This model is parsed by ant tasks and used to build stuff, populate maven-like repositories, etc.

I think the only viable option right now is to have this tool ("magic") generate a gump descriptor. And because the way this project works implies doing more advanced classpath management than gump can feasibly do, the only viable option is to generate a descriptor which calls ant which calls ant with fork="true", to get back classloader control.

Something like

  <project name="foo">
    <ant target="gump">
      <property project="bar" name="bar.jar" reference="jar"/>
      <property project="bar" name="bar.meta"
         path="../target/meta/bar.meta"/>
    </ant>
    <depend project="bar"/>
  </project>
  <project name="bar">
    <ant target="gump">
      <depend property="log4j.jar" project="log4j"/>
    </ant>
    <depend project="bar"/>
  </project>

with in the antfile...

<target name="gump">
  <antcall target="main" fork="true"/>
</target>

In other words, the problem comes down to figuring out how to set what properties. A further goal later on will probably be to have the generation of the gump descriptors execute right before every gump run, which will require a crontab change on brutus and or script change.

from the peanut gallery,

- LSD

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to