> That is the issue, that marriage at the metadata level. > > Ok, "None" was the bit that confused me. Yes, as I understand it, the ID > should match Maven's ID. Not knowing gump, I'm not sure why this is a > problem - I thought the gump descriptor spat out by maven gump would set > this correctly.
Yup, the None is a bug due to many jars in Gump not having ids. :( I am working on fixing that be defaulting the 'id' to a value [maybe not correct] if unset. The problem is that some (potentially hand rolled) Gump descriptors are now being fed into Maven via build.properties. If the Gump descriptors don't have artefact ids, or they do, but they differ from what Maven calls them, we'll have disconnects... Hopefully this can be worked out via metadata management, and community agreement. regards, Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
