Re: [collections] new snapshot to ibiblio

[Mario Ivankovits]

Stefan Bodewig wrote:

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.
   

Gump won't use any repository at all, it will only use the things it
has built itself.
 

I think i have to try to express my thoughts better.

I currently see two build systems - let 1=apache, 2=gump

My above sentence means:
1) use the apache repository http://cvs.apache.org/repository to make 
the apache build happy
2) let gump do for what it is designed for (NOT using the repository, 
but the self generated jars) - and therefore gumps build is happy 
automatically.

Mark R. Diggory wrote:

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. 


I dont want to freeze on a special unrelease version, but - beside gump 
- i see no other chance to let the apache build finish successfully.

For the apache build (1):
If it is possible to use automatically the latest nightly on 
http://cvs.apache.org/builds/jakarta-commons/nightly/ this might be good 
- by having a link to the latest nightly jar
e.g. 
http://cvs.apache.org/builds/jakarta-commons/nightly/commons-collections/commons-collections-latest.jar 
this could be done.

Then there are two dependency-systems possible: 1) use a release 2) use 
the bleeding edge

Think of the current problem in commons-logging and log4j, if one use 
commons-logging he has to wait until a new release of commons-logging is 
out to fix the current build failure.
But if we could temporarily route the build to the bleeding-edge build 
of the dependency this might be a good thing.

-- Mario