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)?

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).

> 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.

> 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.


Once you confirm my questions, I can write some shell scripts to
populate our repository.

Regards,

Felipe



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

Reply via email to