On 7/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:
After resetting my Maven repository, it took several restarts to get it to build. The build would stall on a 503 error, but get past the rror on that field, when restarted.
I had to look up 503... Service Unavailable ? When you say you reset your repository, did you delete the whole thing, or just org/apache/struts? What you're describing sounds like the typical 'first build' that fails several times until all of the transitive dependencies get downloaded to the local repo.
The same thing seems to be happening to me with deploy, but it still fails.
Can you run it with -X and redirect to a file so I can see the entire thing?
Does deploy update the maven-snapshot folder. Evidentally, that part comes at the end.
Yes, 'mvn deploy -Ppre-assembly' should be uploading (via scp) metadata and artifacts to people.apache.org/maven-snapshot-repository as it builds each module. I'm a little concerned because Maven rebuilds the jars during the install phase, so the jars in the assembly are not going to be the same ones that finally get deployed to the m2 repo. (But since there is no date in the manifest, there is a chance they'll match exactly.)
Otherwise, it's tagged, rolled, and uploaded.
Thank you! When you have time I'd like to hear your thoughts on the release process. For such a short checklist, it sure seems like a lot of work. After the last two I wondered if I was making it harder than necessary. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
