Re: Download artifacts from remote repo too many times
This is correct behaviour, in case there is a newer one on a repository later in the list. I believe per-dependency repositories is on consideration for later versions of Maven. If it isn't in JIRA, feel free to add it. Cheers, Brett On Wed, 16 Feb 2005 14:25:47 -0800, baleineca <[EMAIL PROTECTED]> wrote: > Yes, I use snapshot dependencies, so I expect the download. What I > would like ideally is that once it downloaded it from one repo (or > verified the last modified time and decided it doesn't have to), then it > should stop there. Instead right now, it tried to download from the > other repo even after it got it from one. > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Download artifacts from remote repo too many times
Rick Mangi wrote: Yes, well, that's the nature of the snapshot. I think (although someone would have to validate this) that you can restrict a dependency to a particular repo. So if your snapshot dependencies are coming from a known repo you can just check that one. This would be a good solution. Can anyone point me to the right direction? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Download artifacts from remote repo too many times
Yes, well, that's the nature of the snapshot. I think (although someone would have to validate this) that you can restrict a dependency to a particular repo. So if your snapshot dependencies are coming from a known repo you can just check that one. Otherwise I think you're stuck, the assumption with a snapshot is that you're looking for the latest and greatest, so there's no way to know which is the newest unless maven checks all repos. On Feb 16, 2005, at 5:25 PM, baleineca wrote: Yes, I use snapshot dependencies, so I expect the download. What I would like ideally is that once it downloaded it from one repo (or verified the last modified time and decided it doesn't have to), then it should stop there. Instead right now, it tried to download from the other repo even after it got it from one. Rick Mangi wrote: Are you using snapshot dependencies? On Feb 16, 2005, at 1:58 PM, baleineca wrote: I have 2 remote repositories listed in the project.properties as value for maven.repo.remote. Upon sucessfully downloading an artifact from the first repo, maven still goes to the second repo, and of course, because the artifact only resides in the first repo it gets a 404. This doesn't fail the build, but makes build time longer. I think it's unnecessary to try the other repos on the list if we've successfullly downloaded the artifact. Is there a setting or something I am missing to prevent this behaviour or is this just how maven behaves for now? - 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: Download artifacts from remote repo too many times
Yes, I use snapshot dependencies, so I expect the download. What I would like ideally is that once it downloaded it from one repo (or verified the last modified time and decided it doesn't have to), then it should stop there. Instead right now, it tried to download from the other repo even after it got it from one. Rick Mangi wrote: Are you using snapshot dependencies? On Feb 16, 2005, at 1:58 PM, baleineca wrote: I have 2 remote repositories listed in the project.properties as value for maven.repo.remote. Upon sucessfully downloading an artifact from the first repo, maven still goes to the second repo, and of course, because the artifact only resides in the first repo it gets a 404. This doesn't fail the build, but makes build time longer. I think it's unnecessary to try the other repos on the list if we've successfullly downloaded the artifact. Is there a setting or something I am missing to prevent this behaviour or is this just how maven behaves for now? - 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: Download artifacts from remote repo too many times
Are you using snapshot dependencies? On Feb 16, 2005, at 1:58 PM, baleineca wrote: I have 2 remote repositories listed in the project.properties as value for maven.repo.remote. Upon sucessfully downloading an artifact from the first repo, maven still goes to the second repo, and of course, because the artifact only resides in the first repo it gets a 404. This doesn't fail the build, but makes build time longer. I think it's unnecessary to try the other repos on the list if we've successfullly downloaded the artifact. Is there a setting or something I am missing to prevent this behaviour or is this just how maven behaves for now? - 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]
Download artifacts from remote repo too many times
I have 2 remote repositories listed in the project.properties as value for maven.repo.remote. Upon sucessfully downloading an artifact from the first repo, maven still goes to the second repo, and of course, because the artifact only resides in the first repo it gets a 404. This doesn't fail the build, but makes build time longer. I think it's unnecessary to try the other repos on the list if we've successfullly downloaded the artifact. Is there a setting or something I am missing to prevent this behaviour or is this just how maven behaves for now? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
