I'm not 100% sure of this so I'm cross posting to the gump list to see if they agree with me on this subject. They may disagree entirely, in which case I am in error.
Also, I'm not sure why you would want to fix your dependency to a specific snapshot release date when you the latest snapshot may be available to you via Gump/Maven. If you needed to rely on a specific version of a dependency, it would in my opinion, be a major release of that jar and not a dated snapshot.
What I am saying is that you either base your development on the bleeding edge (SNAPSHOT) or a stable release (x.x), not on a possibly outdated and unstable dated or nightly build. This is what we are trying to break away from by getting the nightlies off of ibiblio and into a separate Repository.
-Mark
Mario Ivankovits wrote:
Mark R. Diggory wrote:
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
I thought i have understood GUMP - it seems not.
My impression was, GUMP always use the cvs-head to build the dependencies - and fixing the dependency to a given release is not the intention of GUMP.
The best i can do is to build a snapshot of the required dependency and put it to the apache repository and let GUMP automatically use the nightlies.
Isnt it correct that way?
-- 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]
