I've got some questions regarding the points mentioned at
http://tapestry.apache.org/tapestry5/dev/checklist.html

1) Near the end, the command
rm /www/www.apache.org/dist/tapestry/*-5.0.4*
is mentioned  with the comment that "Only the current release should
be in the dist folder."
What's the reason for this? Should we be doing the same thing for
4.1.X files (I see many versions
of those in the dist folder)?

2) The whole rsync procedure for syncing
~hlship/public_html/tapestry-ibiblio-rsynch-repository/ to
/www/people.apache.org/repo/m2-ibiblio-rsync-repository has some side
effects which are evident in all
the projects that share the same name between T4 and T5. As described in
https://issues.apache.org/jira/browse/TAPESTRY-2718,
several maven-metadata.xml files will miss reference to the 4.1 versions...

I've lately deployed against
/www/people.apache.org/repo/m2-ibiblio-rsync-repository, so
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/tapestry/tapestry-project/maven-metadata.xml
mentions version 4.1.6 but
http://people.apache.org/~hlship/tapestry-ibiblio-rsynch-repository/org/apache/tapestry/tapestry-project/maven-metadata.xml
(which i guess in a few minutes will be copied over) doesn't.

Anyway, the real overlap (after the rename in T5 of the annotation
project to tapestry5-annotation... it's the only
one with such naming) is for tapestry-project and tapestry-test.

Apart from hand editing the files, i guess the alternatives are:
   a) making sure that the latest files from
/www/people.apache.org/repo/m2-ibiblio-rsync-repository are
also in ~hlship/public_html/tapestry-ibiblio-rsynch-repository/ before
deploying there, or
   b) deploying directly to
/www/people.apache.org/repo/m2-ibiblio-rsync-repository

I think i'm with a) esp. since it can only involve the metadata
files... Any more thoughts on this?


-- 
Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting

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

Reply via email to