Ideally, the gump nightly build would also be of the dependency in the Apache case. If this was impossible, you could place the jar somewhere local for the gump build and point the project.properties to it using the jar override mechanism in Maven.

http://maven.apache.org/reference/user-guide.html#Overriding_Stated_Dependencies

-Mark

Mario Ivankovits wrote:
Noel J. Bergman wrote:

Why use snapshots? If you want to track *current* status, you really want
to turn that over to GUMP


GUMP could solve it too - and i like the idea to know ASAP about api-changes of dependencies, but if i commit my changes to the apache-cvs without pointing to the needet dependency-snapshot, their nightly builds will fail.
This seems bad to me.


It looks like (for now) we have to go both ways.

-- Mario


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]


-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to