Felipe, I'mon vacation this week so you may not get many responses from me. I'll try to be breif.
Quoting Felipe Leme <[EMAIL PROTECTED]>: > Hi Mark, > > I'd like to upload all taglibs to the repository, but I have some > questions: > > > On Sat, 2004-02-28 at 12:12, Mark R. Diggory wrote: > > > 1.) create a project directory for taglibs that looks like > > > > > /www/www.apache.org/dist/java-repository/jakarta-taglibs/jars/standard- <version>.jar > > > /www/www.apache.org/dist/java-repository/jakarta-taglibs/jars/jndi- <version>.jar > > > /www/www.apache.org/dist/java-repository/jakarta-taglibs/jars/<tag-lib>- <version>.jar > > > 1.Is /www/www.apache.org/dist/java-repository/ still the right directory > that is synced to ibiblio? If so, where the taglibs from ibiblio came > from (as that directory does not have any of our artifacts)? > Yes, but, you should do all your work to setup the directory structure in a staging area like your home directory before placing anything into these directories. Have someone else whose done the process review everything prior to moving it into the repository. > 2.Ibiblio already have groups for jstl and taglibs, but they have just a > few jars. So, we have 2 options: > > a.maintain that structure > b.put everything on jakarta-taglibs, removing these old files from > ibiblio > > I opt for option b - the only problem is that if remove jstl and taglibs > from ibiblio, it might break other projects that depends on them (I > would still prefer that option, as those groups are crippled). > I don't believe that removing something from java-repository actually removes it from ibiblio because of the rsync process. Yes, you should leave whatever is on ibiblio there at this time. > > 2.) for the last couple releases we should probibly just extract the > > jars from the tar ball distributions and generate md5's for them. > > Ideally, we should 'mavenize' the whole project. But for now, we can > just generate/upload the MD5 files manually. thats fine. > > > 3.) finally, a SNAPSHOT symlink and reference file should be generate > > which points to the latest release for each taglib: > > I read in some ASF list that we should not be providing SNAPSHOTs, only > official releases. > SNAPSHOT is different than unofficial release, SNAPSHOT referes to a link to the most recent release. an unofficial release is one that has the date as a version number, thus there can be SNAPSHOTS that point to official releases in the repository. > > Once you confirm my questions, I can write some shell scripts to > populate our repository. > > Regards, > > Felipe > > Cheers, I'll be around next week if you need help, but I don't suspect I'll have time to respond the rest of this week. -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
