Re: Deploying artifacts: 0 byte files
Just wanted to update where I stand on this issue. I switched over to using sftp instead of scp and it seems to be working much more reliably. Thanks for everyone's input. -wr [EMAIL PROTECTED] on 09/28/2004 01:45:17 AM Please respond to Maven Users List [EMAIL PROTECTED] To:Maven Users List [EMAIL PROTECTED] cc: (bcc: Winston Rast/Jeppesen/TMC) Subject:Re: Deploying artifacts: 0 byte files (Embedded image moved to file: pic29358.jpg) This sound like my Problem with dependancies where snapshot are download with 0K if they are all ready present on my local repo. Unfurtunatlety no body answer me. I am curious to see if your -X trace is same as mine : Getting URL: http://arsodev1:8080/maven-repo/arsoe-socle/jars/socle-util-1.2-SNAPSHOT.jar sending == If-Modified-Since: mer., 15-sept.-04 16:24:26 GMT (1095265466000) Received status code: 200 warning: last-modified not specified 0K downloaded Local timestamp: 1095265466000 Remote timestamp: 0 Nicolas Carlos Sanchez [EMAIL PROTECTED] 28/09/2004 01:16 Veuillez répondre à Maven Users List Pour : 'Maven Users List' [EMAIL PROTECTED] cc : Objet : RE: Deploying artifacts: 0 byte files -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 28, 2004 12:38 AM To: Maven Users List Subject: RE: Deploying artifacts: 0 byte files I should probably elaborate more... None of the 0-byte files are symlinks. In addition to the original problem, sometimes the build will say that the artifact has been deployed, but when I go to check the repository, it's not there. I can recall at one point it would take us several builds to get the artifact to show up that first time. Now it seems that sometimes the artifact appears, sometimes it doesn't, and sometimes when it does show up, it's 0 bytes. This really causes lots of issues later as other projects try to get the artifact as a dependency only to get a ZipException because of the file size. That sounds really extrange and it's the first time I hear something like that I will try to delete everything as you suggest to see if that fixes anything. Perhaps there's a way to add a postGoal to maven's deployment process to check the file size after it's done to validate that it got there already? Should this be done by maven out of the box? It's being done in next versions. -wr Carlos Sanchez [EMAIL PROTECTED] on 09/27/2004 04:25:34 PM Please respond to Maven Users List [EMAIL PROTECTED] To:'Maven Users List' [EMAIL PROTECTED] cc: (bcc: Winston Rast/Jeppesen/TMC) Subject:RE: Deploying artifacts: 0 byte files (Embedded image moved to file: pic04827.jpg) Hi, Maybe those snapshots are symlinks created with versions previous to 1.0? Try the universal solution: Delete them and deploy again. Regards Carlos Sanchez A Coruña, Spain http://www.jroller.com/page/carlossg/Weblog Oness Project http://oness.sourceforge.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 28, 2004 12:20 AM To: [EMAIL PROTECTED] Subject: Deploying artifacts: 0 byte files We have an issue with maven's handling of artifact deployment to our remote repository. Sometimes (not always), when a new snapshot artifact is generated it doesn't get completely written to the remote repository. The size is 0 bytes. We are using the scp:// protocol. The origin machine is solaris and the destination box is linux. Anyone have thoughts on this or experienced it before? This has been very problematic in our environment because other team members depend on the snapshot artifact almost as soon as it's generated. Thanks. -wr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deploying artifacts: 0 byte files
This sound like my Problem with dependancies where snapshot are download with 0K if they are all ready present on my local repo. Unfurtunatlety no body answer me. I am curious to see if your -X trace is same as mine : Getting URL: http://arsodev1:8080/maven-repo/arsoe-socle/jars/socle-util-1.2-SNAPSHOT.jar sending == If-Modified-Since: mer., 15-sept.-04 16:24:26 GMT (1095265466000) Received status code: 200 warning: last-modified not specified 0K downloaded Local timestamp: 1095265466000 Remote timestamp: 0 Nicolas Carlos Sanchez [EMAIL PROTECTED] 28/09/2004 01:16 Veuillez répondre à Maven Users List Pour : 'Maven Users List' [EMAIL PROTECTED] cc : Objet : RE: Deploying artifacts: 0 byte files -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 28, 2004 12:38 AM To: Maven Users List Subject: RE: Deploying artifacts: 0 byte files I should probably elaborate more... None of the 0-byte files are symlinks. In addition to the original problem, sometimes the build will say that the artifact has been deployed, but when I go to check the repository, it's not there. I can recall at one point it would take us several builds to get the artifact to show up that first time. Now it seems that sometimes the artifact appears, sometimes it doesn't, and sometimes when it does show up, it's 0 bytes. This really causes lots of issues later as other projects try to get the artifact as a dependency only to get a ZipException because of the file size. That sounds really extrange and it's the first time I hear something like that I will try to delete everything as you suggest to see if that fixes anything. Perhaps there's a way to add a postGoal to maven's deployment process to check the file size after it's done to validate that it got there already? Should this be done by maven out of the box? It's being done in next versions. -wr Carlos Sanchez [EMAIL PROTECTED] on 09/27/2004 04:25:34 PM Please respond to Maven Users List [EMAIL PROTECTED] To:'Maven Users List' [EMAIL PROTECTED] cc: (bcc: Winston Rast/Jeppesen/TMC) Subject:RE: Deploying artifacts: 0 byte files (Embedded image moved to file: pic04827.jpg) Hi, Maybe those snapshots are symlinks created with versions previous to 1.0? Try the universal solution: Delete them and deploy again. Regards Carlos Sanchez A Coruña, Spain http://www.jroller.com/page/carlossg/Weblog Oness Project http://oness.sourceforge.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 28, 2004 12:20 AM To: [EMAIL PROTECTED] Subject: Deploying artifacts: 0 byte files We have an issue with maven's handling of artifact deployment to our remote repository. Sometimes (not always), when a new snapshot artifact is generated it doesn't get completely written to the remote repository. The size is 0 bytes. We are using the scp:// protocol. The origin machine is solaris and the destination box is linux. Anyone have thoughts on this or experienced it before? This has been very problematic in our environment because other team members depend on the snapshot artifact almost as soon as it's generated. Thanks. -wr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deploying artifacts: 0 byte files
I am running v1.0. To follow up with Carlos' suggestion of deleting everything in my repository...it seems (so far) I have had a degree of success. I have yet to see a 0 byte file show up. However, I do see some inconsistency in the behavior of the deployment. Namely, I have one project that deploys a set of files like this: name-timestamp.jar name-timestamp.jar.md5 name-SNAPSHOT.jar name-SNAPSHOT.jar.md5 name-snapshot-version And yet another project that does the exact same deployment only has this set of files: name-timestamp.jar name-SNAPSHOT.jar name-SNAPSHOT.jar.md5 Why the difference? It is as if some of the commands being run remotely are unsuccessful. The build results don't reflect any such failure. As I said things seem ok for now after deleting a bunch of the repo's files, but I have a hunch bad things will be happening here in the next day or two. -wr Jefferson K. French [EMAIL PROTECTED] on 09/27/2004 05:16:58 PM Please respond to Maven Users List [EMAIL PROTECTED]; Please respond to [EMAIL PROTECTED] To:Maven Users List [EMAIL PROTECTED] cc: (bcc: Winston Rast/Jeppesen/TMC) Subject:Re: Deploying artifacts: 0 byte files (Embedded image moved to file: pic19912.jpg) What version of Maven are you running? I remember something similar happening to me (although Linux to Linux), a while back, but I have not had a problem since v1.0. On Mon, 27 Sep 2004, at 16:37:57 [GMT -0600] [EMAIL PROTECTED] wrote: I should probably elaborate more... None of the 0-byte files are symlinks. In addition to the original problem, sometimes the build will say that the artifact has been deployed, but when I go to check the repository, it's not there. I can recall at one point it would take us several builds to get the artifact to show up that first time. Now it seems that sometimes the artifact appears, sometimes it doesn't, and sometimes when it does show up, it's 0 bytes. This really causes lots of issues later as other projects try to get the artifact as a dependency only to get a ZipException because of the file size. I will try to delete everything as you suggest to see if that fixes anything. Perhaps there's a way to add a postGoal to maven's deployment process to check the file size after it's done to validate that it got there already? Should this be done by maven out of the box? -- mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deploying artifacts: 0 byte files
Hi, Maybe those snapshots are symlinks created with versions previous to 1.0? Try the universal solution: Delete them and deploy again. Regards Carlos Sanchez A Coruña, Spain http://www.jroller.com/page/carlossg/Weblog Oness Project http://oness.sourceforge.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 28, 2004 12:20 AM To: [EMAIL PROTECTED] Subject: Deploying artifacts: 0 byte files We have an issue with maven's handling of artifact deployment to our remote repository. Sometimes (not always), when a new snapshot artifact is generated it doesn't get completely written to the remote repository. The size is 0 bytes. We are using the scp:// protocol. The origin machine is solaris and the destination box is linux. Anyone have thoughts on this or experienced it before? This has been very problematic in our environment because other team members depend on the snapshot artifact almost as soon as it's generated. Thanks. -wr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deploying artifacts: 0 byte files
I should probably elaborate more... None of the 0-byte files are symlinks. In addition to the original problem, sometimes the build will say that the artifact has been deployed, but when I go to check the repository, it's not there. I can recall at one point it would take us several builds to get the artifact to show up that first time. Now it seems that sometimes the artifact appears, sometimes it doesn't, and sometimes when it does show up, it's 0 bytes. This really causes lots of issues later as other projects try to get the artifact as a dependency only to get a ZipException because of the file size. I will try to delete everything as you suggest to see if that fixes anything. Perhaps there's a way to add a postGoal to maven's deployment process to check the file size after it's done to validate that it got there already? Should this be done by maven out of the box? -wr Carlos Sanchez [EMAIL PROTECTED] on 09/27/2004 04:25:34 PM Please respond to Maven Users List [EMAIL PROTECTED] To:'Maven Users List' [EMAIL PROTECTED] cc: (bcc: Winston Rast/Jeppesen/TMC) Subject:RE: Deploying artifacts: 0 byte files (Embedded image moved to file: pic04827.jpg) Hi, Maybe those snapshots are symlinks created with versions previous to 1.0? Try the universal solution: Delete them and deploy again. Regards Carlos Sanchez A Coruña, Spain http://www.jroller.com/page/carlossg/Weblog Oness Project http://oness.sourceforge.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 28, 2004 12:20 AM To: [EMAIL PROTECTED] Subject: Deploying artifacts: 0 byte files We have an issue with maven's handling of artifact deployment to our remote repository. Sometimes (not always), when a new snapshot artifact is generated it doesn't get completely written to the remote repository. The size is 0 bytes. We are using the scp:// protocol. The origin machine is solaris and the destination box is linux. Anyone have thoughts on this or experienced it before? This has been very problematic in our environment because other team members depend on the snapshot artifact almost as soon as it's generated. Thanks. -wr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deploying artifacts: 0 byte files
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 28, 2004 12:38 AM To: Maven Users List Subject: RE: Deploying artifacts: 0 byte files I should probably elaborate more... None of the 0-byte files are symlinks. In addition to the original problem, sometimes the build will say that the artifact has been deployed, but when I go to check the repository, it's not there. I can recall at one point it would take us several builds to get the artifact to show up that first time. Now it seems that sometimes the artifact appears, sometimes it doesn't, and sometimes when it does show up, it's 0 bytes. This really causes lots of issues later as other projects try to get the artifact as a dependency only to get a ZipException because of the file size. That sounds really extrange and it's the first time I hear something like that I will try to delete everything as you suggest to see if that fixes anything. Perhaps there's a way to add a postGoal to maven's deployment process to check the file size after it's done to validate that it got there already? Should this be done by maven out of the box? It's being done in next versions. -wr Carlos Sanchez [EMAIL PROTECTED] on 09/27/2004 04:25:34 PM Please respond to Maven Users List [EMAIL PROTECTED] To:'Maven Users List' [EMAIL PROTECTED] cc: (bcc: Winston Rast/Jeppesen/TMC) Subject:RE: Deploying artifacts: 0 byte files (Embedded image moved to file: pic04827.jpg) Hi, Maybe those snapshots are symlinks created with versions previous to 1.0? Try the universal solution: Delete them and deploy again. Regards Carlos Sanchez A Coruña, Spain http://www.jroller.com/page/carlossg/Weblog Oness Project http://oness.sourceforge.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 28, 2004 12:20 AM To: [EMAIL PROTECTED] Subject: Deploying artifacts: 0 byte files We have an issue with maven's handling of artifact deployment to our remote repository. Sometimes (not always), when a new snapshot artifact is generated it doesn't get completely written to the remote repository. The size is 0 bytes. We are using the scp:// protocol. The origin machine is solaris and the destination box is linux. Anyone have thoughts on this or experienced it before? This has been very problematic in our environment because other team members depend on the snapshot artifact almost as soon as it's generated. Thanks. -wr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deploying artifacts: 0 byte files
What version of Maven are you running? I remember something similar happening to me (although Linux to Linux), a while back, but I have not had a problem since v1.0. On Mon, 27 Sep 2004, at 16:37:57 [GMT -0600] [EMAIL PROTECTED] wrote: I should probably elaborate more... None of the 0-byte files are symlinks. In addition to the original problem, sometimes the build will say that the artifact has been deployed, but when I go to check the repository, it's not there. I can recall at one point it would take us several builds to get the artifact to show up that first time. Now it seems that sometimes the artifact appears, sometimes it doesn't, and sometimes when it does show up, it's 0 bytes. This really causes lots of issues later as other projects try to get the artifact as a dependency only to get a ZipException because of the file size. I will try to delete everything as you suggest to see if that fixes anything. Perhaps there's a way to add a postGoal to maven's deployment process to check the file size after it's done to validate that it got there already? Should this be done by maven out of the box? -- mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
