On 8/8/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> And how are we going to handle the vote? I think we should tag and
> build it as 1.1.4, run the TCK, then vote. Other opinions? (The
> guidelines on the wiki may need to be revised.)
So the plan is:
1.) Deploy to the snapshot repo
2.) Vote
3.) Manually copy to the ibiblio sync dirs?
1) could be either m2-snapshot-repository, or the myfaces repo on the zone.
1.5) Run the TCK one last time on the exact artifacts we intend to release.
3) Yes, with the caveat that there is no easy way to 'promote' an
artifact from the snapshot to the ibiblio-rsync repo. You can't just
copy files over, since Maven depends on the repository metadata xml
files for information.
For jars, you can 'mvn deploy deploy:file' them.
For the artifacts of packaging=pom (myfaces-core-project) Carlos
suggested changing the repo in the pom, doing 'mvn deploy' to
m2-ibiblio-rsync-repository, then copying the 'original' pom,
checksums and signatures over the deployed ones.
And we do this for both shared and core right? And does shared go to
ibiblio or do we keep that on our internal repo only?
I don't have a strong opinion on this. It needs to be available so
people can easily build from source (and provide patches.) The way
the repositories are configured, releases will be picked up from
central (ibiblio) and the myfaces repo on the zone, so Shared 2.0.3
needs to be in one of those places.
--
Wendy
