Re: Has the behavior of -U option changed?

I looked at the metadata in question, and the lastUpdated value is in the future (due to the fact that the Artifactory repository is in a different timezone). Could this be the problem? -- View this message in context: http://maven.40175.n5.nabble.com/Has-the-behavior-of-U-option-changed-tp3374

Re: Has the behavior of -U option changed?

Thanks for the reply. I know for a fact that a newer snapshot was uploaded to Artifactory. I imagine then that this issue could be specific to Artifactory. We are currently at version 2.2.2 of that product but coincidentally plan to upgrade soon. -- View this message in context: http://maven.4

Re: Has the behavior of -U option changed?

I have re-tested with the pre-release version of 3.0.3 and find the -U behavior to be the same as 3.0.2. Specifically, when I expect it to download the latest jar from Artifactory, all it downloads is metadata: Downloading: .../0.7-SNAPSHOT/maven-metadata.xml Downloaded: .../0.7-SNAPSHOT/maven-me

Re: Has the behavior of -U option changed?

Thanks but in our case there is no need to go to Maven central because the Artifactory server hosts the dependency. In a nutshell, Team 1 builds the components and Team 2 builds the applications, they both publish to the same repository. -- View this message in context: http://maven.40175.n5.na

Re: Has the behavior of -U option changed?

Thanks for the reply. We are not using Nexus, we are using Artifactory. When I have some time I will gather logs and post them here. -- View this message in context: http://maven.40175.n5.nabble.com/Has-the-behavior-of-U-option-changed-tp3374270p3374705.html Sent from the Maven - Users mailing

Has the behavior of -U option changed?

Hi, I've been using alpha and beta versions of mvn3 for almost a year on the same project, and it seems like only after upgrading to 3.0.2 on January 9th that the behavior of the -U option has changed. Since that time I have had to perform the following sequence several times: 1. mvn3 install -

Re: 3.0-alpha7 password decryption

Thanks for the quick response, here is the issue I created: http://jira.codehaus.org/browse/MNG-4611 jvanzyl wrote: > > Raise an issue in JIRA. > -- View this message in context: http://old.nabble.com/3.0-alpha7-password-decryption-tp28042090p28043925.html Sent from the Maven - Users mailin

3.0-alpha7 password decryption

I've got an issue related to password decryption in 3.0-alpha7 that makes the mvn -X option effectively unusable. The password I've got in my settings.xml file looks like this: {DESede}y+qq...== This is an Artifactory setup password and it does work, however mvn -X logs exceptions a

Downloading modules that are part of the current build, why?

I've been a maven advocate for a while but there is a particular behavior that still puzzles me. When building a multi-module project why does the build process download the latest snapshots of modules that are about to be built? For example, I'm waiting now while a war snapshot is being download