From: "Vincent Massol" <[EMAIL PROTECTED]>
> Hi,
>
> Several of my projects generate (as distributables) bunches of files
> (actually some generate a full directory structure, others some zip
> files, EAR, etc).
>
> The problem is that gump only knows about jars being delivered by a
> project (and javadoc but this is not used for pre-req checks).
>
> Thus, when I have a project that depends on this kind of project, gump
> does not recognize a prereq failure.
>
> I haven't found anything better than tricking gump by using a <jar>
> entry that points to a non jar files (but then it gets added to the
> classpath and although I can choose the file so that it won't do any
> harm, it is not a really good solution).
>
> Proposal : To extend the gump DTD to support the notion of deliverables
> (I seem to remember Nicola had proposed something along the same lines
> not long ago on this list).
Yes, and AFAIK there is already an working <deliver/> tag...
Any way of getting it working?
> Something like :
>
> <deliverables setid="set1">
> <jar name="" id=""/>
> <directory location=""/>
> <file path=""/>
> </deliverables>
>
> <deliver fromdir="" [...] setid="set1"/>
>
> Prereq logic will check that all deliverables have been created. <jar>
> would work in the same way it is currently working. <deliver> would copy
> the said deliverables to some location.
Hmmm... this basically breakes the fact that it's Gump that should decide
what to do with the module stuff.
In my last proposal, I also proposed to eliminate the javadoc tag, in favor
of a system that tells Gump what the build results are, without defining
explicit deliver systems.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
