> For this project:
>
http://brutus.apache.org/gump/public/jakarta-turbine-fulcrum/fulcrum-xmlrpc/
> gump_work/build_jakarta-turbine-fulcrum_fulcrum-xmlrpc.html
>
> Maven is failing looking for xmlrpc as a dependency. Unfortunantly, in
> Gump, xmlrpc is called "ws-xmlrpc". I already have the dependency:
It doesn't matter (so much) that Gump and Maven call the project something
different, although (over time) it might be nice to standardize. [It matters
only for the Maven Gump goal automatically generating the Gump descriptor.]
For now --- all that matters is that the Gump <jar id matches the Maven
artifactId.
> <depend project="ws-xmlrpc"/>
>
> >From the docs, doing this isn't what I want: <depend project="ws-xmlrpc"
> ids="xmlrpc"/>, what about doing this: <depend project="ws-xmlrpc"
> id="xmlrpc"/>?
Stefano and I were just discussing this. The <depend element is confusing,
and incompletely documented.
Looking at this, we have the simple case:
http://gump.apache.org/metadata/project.html#depend
There is a more complex case (barely mentioned in this part):
http://gump.apache.org/metadata/project.html#project
I believe the logic here (when a depend is inside <ant or <maven or
whatever) is that one sets attributes that are (1) a property name and (2)
an id (singular), and one effectively gets both a depend and a property.
Hmm, hold on .... I found this documentation:
http://gump.apache.org/metadata/builder.html#depend
regards
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
