the most important part of the gump descriptors are, without doubts, the dependencies. So, today, I picked one of the failing projects (jakarta-slide) and recognized that it was a missing dependency (commons-logging).

So, simply enough, I opened up the jakarta-slide.xml module and then looked at the gump information at

http://brutus.apache.org/gump/public/jakarta-slide/jakarta-slide/index.html

to understand what to do.

There are two places where you can put <depend>

 1) inside <project>
 2) inside <ant>

jakarta-slide.xml uses both.

First of all, what is the rationale behind this? if a project depends on another project, why do we need to specify things further for ant?

Also, I don't understand the difference between:

 <depend property="" project="" id=""/>

and

 <property name="" project="" id=""/>

why are they different? and, if so, why are their methods so similar?

Also, look at the gump "annotations":

it says "unnamed property for [jakarta-slide] in depend on:  jakarta-lucene.

and this is because <ant contains <depend project="jakarta-lucene"/> without further attributes. But then I look at the jakarta-lucene.xml attributes and find out that there are no properties exposed! so, what does that mean? should I move that <depend under <project instead?

gosh, this is all very confusing, people.

the vanilla descriptors (jakarta-lucene.xml) for example, are nice, simple and immediate for people to understand, but things like jakarta-slide.xml are not and I suspect it might also the reason why they break down more.

--
Stefano.


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to