Paul et all

http://cvs.apache.org/repository has snapshot and timestamp versions of
jelly, but has only a snapshot version of jelly-xml. 
Paul, could you please upload the timestamp version of the build? (Or make a
new one :()

Regards, Diogo

-----------------------------------
Diogo Bacelar Quintela
EF - Tecnologias de Informação, Lda.
Av. António Serpa, 26 - 4º Dto.
1050-027 Lisboa, Portugal
Tel: (+351) 217 827 800
Fax: (+351) 217 827 830
Email: [EMAIL PROTECTED]
PGP: 0xF51A5AB9 

> -----Original Message-----
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: quinta-feira, 4 de Agosto de 2005 12:35
> To: Jakarta Commons Developers List
> Subject: Re: [jelly] Jelly Builds
> 
> Paul Libbrecht wrote:
> 
> > I'll put jelly and jelly-tags-xml current snapshots and
> > http://cvs.apache.org/repository if I manage but I have a consistency
> > problem:
> > there are snapshots at
> >  http://www.ibiblio.org/maven/commons-jelly/jars/
> > (and presumably other commons projects).
> >
> > So either we delete the snapshots from there (bad!), or we mirror
> > with  up-to-date snapshots!
> > commons-jelly-SNAPSHOT.jar is even older as commons-jelly-1.0.jar...
> > I  doubt this is good, or?
> >
> >
> > That's probably historical and there's probably an FAQ, still, I find
> > it really delicate.
> > How would a newbie developer, freshly embracing maven and jelly and
> > believing maven and jelly fit together, know that he needs a special
> > repository property in order to get the current jelly-snapshot ?
> 
> Yes, I agree we should remove the SNAPSHOT files, but -must- retained
> the timestamped snapshots of Jelly for historical purposes.
> 
> If you agree, I can do this.
> 
> - Brett
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


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

Reply via email to