Stefan Bodewig wrote:
On Tue, 26 Oct 2004, Brett Porter <[EMAIL PROTECTED]> wrote:
As I understand it, the general problem here is that the project.xml changes, and the gump descriptor is not updated. The version is just a reflection of this, and it probably changes the most. Is this correct?
Yes, and I agree with the long term goal to use project.xml directly. This certainly clashes with Stefano's quest to move all metadata into Gump's own repo 8-)
Not necessarely. The idea to move the data "in-house" is to allow us to reach equilibrium faster.
The long term goal is exactly what Eric describes: you should name your dependencies only once and gump should do the work for you.
I'd really like to go down the track of having gump effectively run "maven gump" for a project, then use the generated descriptor instead. What is involved in that from the gump end? I assume since it happened for magic, it must be possible.
It doesn't happen for Magic. The projects using Magic do the equivalent of "maven gump" and add the generated descriptor to Gump's metadata set IIUC.
which, IMO, is a pretty broken design.
Gump should be able to digest any metadata format that is required to build stuff.
But obviously, that implies that people stop being allergic to python.
-- Stefano.
smime.p7s
Description: S/MIME Cryptographic Signature
