RE: keyword SNAPSHOT in depedency version is ignored
When I have this in the parent POM: dependencyManagement dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version[3.8.1,)/version scopetest/scope /dependency [snip] This is the result when run in a module: [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] artifact junit:junit: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a 2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80 709' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a 2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80 709' - IGNORING [INFO] [compiler:compile] Is this expected, something wrong on my part, or perhaps a bug? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, November 03, 2005 5:58 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored What was the dependency? Do you have a test case? - Brett On 11/4/05, Brian E. Fox [EMAIL PROTECTED] wrote: I'm not able to make this work. I tried: [1.1,) [1.1,] (1.1,) Etc. Each time it is trying to resolve that version exactly as typed. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 3:27 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored This functionality already exists in Maven 2.0. [1.0,) indicates = 1.0 - Brett On 11/1/05, Lukas Theussl [EMAIL PROTECTED] wrote: Right, but this would be something completely different from the current snapshot functionality. As I said in one of my earlier mails, if you want that functionality you can open a JIRA request for it (preferably with a patch attached ;) ). And of course, I retain all my reservations about automatic dependency upgrade as expressed before. But then, if you want it, it's your decision. :) -Lukas Brian E. Fox wrote: I think maybe what is being asked for is the ability to get the lastest non snapshot build? For example if wagon-ftp changes from 1.0 to 1.1, I want to automatically grab it. Maybe not the best decision, but still a possible option to allow people to choose. I think that in terms of versioning modules you have control over, this might be preferrable. This way a development team could depend on the latest sanctioned version without depending on unstable snapshot builds and without having to manually update all the poms everytime a new module is published. -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 1:01 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Hi, What if a released component on remote repository has any bugs? This just underscores my point, no? Generally, I think upgrading (or downgrading) a dependency is always something that should be done very carefully and very consciously, I wouldn't want to have that done automatically. Indicating a SNAPSHOT dependency is only useful if you know that a project is currently under heavy development and you want to stay up to date with changes on a, say, day-to-day basis (assuming the project publishes SNAPSHOTs that often). This implies that your project itself is currently changing frequently, and if something breaks from one day to the other, you know it might not be due to your own code, but to a changed dependency. As soon as a stable release gets out, you have to indicate explicitly (after testing) that you no longer want to use SNAPSHOTs, but stick to a particular stable version. If features of a component do not have to be changed to fix bugs, I think it's useful to replace this bad component on local repository with bug fixed component on remote repository automatically (after agreement). But how would you indicate which component is the good one? A SNAPSHOT always gets you the _latest_ development version, which is actually very rarely the most bug-free one! ;) -Lukas -- -- - 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
Re: keyword SNAPSHOT in depedency version is ignored
Could you run with -X so it tells you exactly which file has the checksum error (it could be the metadata, the pom, or the JAR). We are in the process of minotiring the repository for such errors. - Brett On 11/7/05, Jeff Jensen [EMAIL PROTECTED] wrote: When I have this in the parent POM: dependencyManagement dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version[3.8.1,)/version scopetest/scope /dependency [snip] This is the result when run in a module: [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] artifact junit:junit: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a 2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80 709' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a 2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80 709' - IGNORING [INFO] [compiler:compile] Is this expected, something wrong on my part, or perhaps a bug? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, November 03, 2005 5:58 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored What was the dependency? Do you have a test case? - Brett On 11/4/05, Brian E. Fox [EMAIL PROTECTED] wrote: I'm not able to make this work. I tried: [1.1,) [1.1,] (1.1,) Etc. Each time it is trying to resolve that version exactly as typed. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 3:27 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored This functionality already exists in Maven 2.0. [1.0,) indicates = 1.0 - Brett On 11/1/05, Lukas Theussl [EMAIL PROTECTED] wrote: Right, but this would be something completely different from the current snapshot functionality. As I said in one of my earlier mails, if you want that functionality you can open a JIRA request for it (preferably with a patch attached ;) ). And of course, I retain all my reservations about automatic dependency upgrade as expressed before. But then, if you want it, it's your decision. :) -Lukas Brian E. Fox wrote: I think maybe what is being asked for is the ability to get the lastest non snapshot build? For example if wagon-ftp changes from 1.0 to 1.1, I want to automatically grab it. Maybe not the best decision, but still a possible option to allow people to choose. I think that in terms of versioning modules you have control over, this might be preferrable. This way a development team could depend on the latest sanctioned version without depending on unstable snapshot builds and without having to manually update all the poms everytime a new module is published. -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 1:01 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Hi, What if a released component on remote repository has any bugs? This just underscores my point, no? Generally, I think upgrading (or downgrading) a dependency is always something that should be done very carefully and very consciously, I wouldn't want to have that done automatically. Indicating a SNAPSHOT dependency is only useful if you know that a project is currently under heavy development and you want to stay up to date with changes on a, say, day-to-day basis (assuming the project publishes SNAPSHOTs that often). This implies that your project itself is currently changing frequently, and if something breaks from one day to the other, you know it might not be due to your own code, but to a changed dependency. As soon as a stable release gets out, you have to indicate explicitly (after testing) that you no longer want to use SNAPSHOTs, but stick to a particular stable version. If features of a component do not have to be changed to fix bugs, I think it's useful to replace this bad component on local repository with bug fixed component on remote repository automatically (after agreement). But how would you indicate which component is the good one? A SNAPSHOT always gets you the _latest_ development version, which is actually very rarely the most bug-free one! ;) -Lukas -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
RE: keyword SNAPSHOT in depedency version is ignored
Looks like the jar itself: [INFO] artifact junit:junit: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - IGNORING [DEBUG] junit:junit:jar:3.8.1 (setting version to: 3.8.1 from range: [3.8.1,)) [DEBUG] junit:junit:jar:3.8.1 (selected for test) -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Sunday, November 06, 2005 6:39 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Could you run with -X so it tells you exactly which file has the checksum error (it could be the metadata, the pom, or the JAR). We are in the process of minotiring the repository for such errors. - Brett On 11/7/05, Jeff Jensen [EMAIL PROTECTED] wrote: When I have this in the parent POM: dependencyManagement dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version[3.8.1,)/version scopetest/scope /dependency [snip] This is the result when run in a module: [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] artifact junit:junit: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a 2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80 709' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a 2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80 709' - IGNORING [INFO] [compiler:compile] Is this expected, something wrong on my part, or perhaps a bug? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, November 03, 2005 5:58 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored What was the dependency? Do you have a test case? - Brett On 11/4/05, Brian E. Fox [EMAIL PROTECTED] wrote: I'm not able to make this work. I tried: [1.1,) [1.1,] (1.1,) Etc. Each time it is trying to resolve that version exactly as typed. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 3:27 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored This functionality already exists in Maven 2.0. [1.0,) indicates = 1.0 - Brett On 11/1/05, Lukas Theussl [EMAIL PROTECTED] wrote: Right, but this would be something completely different from the current snapshot functionality. As I said in one of my earlier mails, if you want that functionality you can open a JIRA request for it (preferably with a patch attached ;) ). And of course, I retain all my reservations about automatic dependency upgrade as expressed before. But then, if you want it, it's your decision. :) -Lukas Brian E. Fox wrote: I think maybe what is being asked for is the ability to get the lastest non snapshot build? For example if wagon-ftp changes from 1.0 to 1.1, I want to automatically grab it. Maybe not the best decision, but still a possible option to allow people to choose. I think that in terms of versioning modules you have control over, this might be preferrable. This way a development team could depend on the latest sanctioned version without depending on unstable snapshot builds and without having to manually update all the poms everytime a new module is published. -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 1:01 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Hi, What if a released component on remote repository has any bugs? This just underscores my point, no? Generally, I think upgrading (or downgrading) a dependency is always something that should be done very carefully and very consciously, I wouldn't want to have that done automatically. Indicating a SNAPSHOT dependency is only useful if you know that a project is currently under heavy development and you want to stay up to date with changes on a, say, day-to-day basis (assuming the project publishes SNAPSHOTs that often). This implies that your project itself is currently changing frequently, and if something breaks from one day to the other, you know it might not be due to your own code, but to a changed dependency. As soon as a stable release gets out, you have to indicate explicitly (after testing
RE: keyword SNAPSHOT in depedency version is ignored
Actually, I should say I can't tell! Is there more info to get somehow? Was there something specific you were expecting that isn't there?? -Original Message- From: Jeff Jensen [mailto:[EMAIL PROTECTED] Sent: Sunday, November 06, 2005 7:28 PM To: 'Maven Users List' Subject: RE: keyword SNAPSHOT in depedency version is ignored Looks like the jar itself: [INFO] artifact junit:junit: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - IGNORING [DEBUG] junit:junit:jar:3.8.1 (setting version to: 3.8.1 from range: [3.8.1,)) [DEBUG] junit:junit:jar:3.8.1 (selected for test) -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Sunday, November 06, 2005 6:39 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Could you run with -X so it tells you exactly which file has the checksum error (it could be the metadata, the pom, or the JAR). We are in the process of minotiring the repository for such errors. - Brett On 11/7/05, Jeff Jensen [EMAIL PROTECTED] wrote: When I have this in the parent POM: dependencyManagement dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version[3.8.1,)/version scopetest/scope /dependency [snip] This is the result when run in a module: [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] artifact junit:junit: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a 2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80 709' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a 2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80 709' - IGNORING [INFO] [compiler:compile] Is this expected, something wrong on my part, or perhaps a bug? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, November 03, 2005 5:58 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored What was the dependency? Do you have a test case? - Brett On 11/4/05, Brian E. Fox [EMAIL PROTECTED] wrote: I'm not able to make this work. I tried: [1.1,) [1.1,] (1.1,) Etc. Each time it is trying to resolve that version exactly as typed. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 3:27 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored This functionality already exists in Maven 2.0. [1.0,) indicates = 1.0 - Brett On 11/1/05, Lukas Theussl [EMAIL PROTECTED] wrote: Right, but this would be something completely different from the current snapshot functionality. As I said in one of my earlier mails, if you want that functionality you can open a JIRA request for it (preferably with a patch attached ;) ). And of course, I retain all my reservations about automatic dependency upgrade as expressed before. But then, if you want it, it's your decision. :) -Lukas Brian E. Fox wrote: I think maybe what is being asked for is the ability to get the lastest non snapshot build? For example if wagon-ftp changes from 1.0 to 1.1, I want to automatically grab it. Maybe not the best decision, but still a possible option to allow people to choose. I think that in terms of versioning modules you have control over, this might be preferrable. This way a development team could depend on the latest sanctioned version without depending on unstable snapshot builds and without having to manually update all the poms everytime a new module is published. -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 1:01 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Hi, What if a released component on remote repository has any bugs? This just underscores my point, no? Generally, I think upgrading (or downgrading) a dependency is always something that should be done very carefully and very consciously, I wouldn't want to have that done automatically. Indicating a SNAPSHOT dependency is only useful if you know that a project is currently under heavy development and you want to stay up to date with changes on a, say, day-to-day basis (assuming the project publishes
Re: keyword SNAPSHOT in depedency version is ignored
Yes, I was expecting something more. I thought there'd be a stack trace associated with the warning. I'll take a look. - Brett On 11/7/05, Jeff Jensen [EMAIL PROTECTED] wrote: Actually, I should say I can't tell! Is there more info to get somehow? Was there something specific you were expecting that isn't there?? -Original Message- From: Jeff Jensen [mailto:[EMAIL PROTECTED] Sent: Sunday, November 06, 2005 7:28 PM To: 'Maven Users List' Subject: RE: keyword SNAPSHOT in depedency version is ignored Looks like the jar itself: [INFO] artifact junit:junit: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - IGNORING [DEBUG] junit:junit:jar:3.8.1 (setting version to: 3.8.1 from range: [3.8.1,)) [DEBUG] junit:junit:jar:3.8.1 (selected for test) -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Sunday, November 06, 2005 6:39 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Could you run with -X so it tells you exactly which file has the checksum error (it could be the metadata, the pom, or the JAR). We are in the process of minotiring the repository for such errors. - Brett On 11/7/05, Jeff Jensen [EMAIL PROTECTED] wrote: When I have this in the parent POM: dependencyManagement dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version[3.8.1,)/version scopetest/scope /dependency [snip] This is the result when run in a module: [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] artifact junit:junit: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a 2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80 709' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '732552cf5a 2673094c0d6ceb38249ebc9dfbe9e3'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80 709' - IGNORING [INFO] [compiler:compile] Is this expected, something wrong on my part, or perhaps a bug? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, November 03, 2005 5:58 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored What was the dependency? Do you have a test case? - Brett On 11/4/05, Brian E. Fox [EMAIL PROTECTED] wrote: I'm not able to make this work. I tried: [1.1,) [1.1,] (1.1,) Etc. Each time it is trying to resolve that version exactly as typed. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 3:27 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored This functionality already exists in Maven 2.0. [1.0,) indicates = 1.0 - Brett On 11/1/05, Lukas Theussl [EMAIL PROTECTED] wrote: Right, but this would be something completely different from the current snapshot functionality. As I said in one of my earlier mails, if you want that functionality you can open a JIRA request for it (preferably with a patch attached ;) ). And of course, I retain all my reservations about automatic dependency upgrade as expressed before. But then, if you want it, it's your decision. :) -Lukas Brian E. Fox wrote: I think maybe what is being asked for is the ability to get the lastest non snapshot build? For example if wagon-ftp changes from 1.0 to 1.1, I want to automatically grab it. Maybe not the best decision, but still a possible option to allow people to choose. I think that in terms of versioning modules you have control over, this might be preferrable. This way a development team could depend on the latest sanctioned version without depending on unstable snapshot builds and without having to manually update all the poms everytime a new module is published. -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 1:01 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Hi, What if a released component on remote repository has any bugs? This just underscores my point, no? Generally, I think upgrading (or downgrading) a dependency is always something that should be done very carefully and very consciously, I
RE: keyword SNAPSHOT in depedency version is ignored
I'm not able to make this work. I tried: [1.1,) [1.1,] (1.1,) Etc. Each time it is trying to resolve that version exactly as typed. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 3:27 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored This functionality already exists in Maven 2.0. [1.0,) indicates = 1.0 - Brett On 11/1/05, Lukas Theussl [EMAIL PROTECTED] wrote: Right, but this would be something completely different from the current snapshot functionality. As I said in one of my earlier mails, if you want that functionality you can open a JIRA request for it (preferably with a patch attached ;) ). And of course, I retain all my reservations about automatic dependency upgrade as expressed before. But then, if you want it, it's your decision. :) -Lukas Brian E. Fox wrote: I think maybe what is being asked for is the ability to get the lastest non snapshot build? For example if wagon-ftp changes from 1.0 to 1.1, I want to automatically grab it. Maybe not the best decision, but still a possible option to allow people to choose. I think that in terms of versioning modules you have control over, this might be preferrable. This way a development team could depend on the latest sanctioned version without depending on unstable snapshot builds and without having to manually update all the poms everytime a new module is published. -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 1:01 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Hi, What if a released component on remote repository has any bugs? This just underscores my point, no? Generally, I think upgrading (or downgrading) a dependency is always something that should be done very carefully and very consciously, I wouldn't want to have that done automatically. Indicating a SNAPSHOT dependency is only useful if you know that a project is currently under heavy development and you want to stay up to date with changes on a, say, day-to-day basis (assuming the project publishes SNAPSHOTs that often). This implies that your project itself is currently changing frequently, and if something breaks from one day to the other, you know it might not be due to your own code, but to a changed dependency. As soon as a stable release gets out, you have to indicate explicitly (after testing) that you no longer want to use SNAPSHOTs, but stick to a particular stable version. If features of a component do not have to be changed to fix bugs, I think it's useful to replace this bad component on local repository with bug fixed component on remote repository automatically (after agreement). But how would you indicate which component is the good one? A SNAPSHOT always gets you the _latest_ development version, which is actually very rarely the most bug-free one! ;) -Lukas - 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: keyword SNAPSHOT in depedency version is ignored
What was the dependency? Do you have a test case? - Brett On 11/4/05, Brian E. Fox [EMAIL PROTECTED] wrote: I'm not able to make this work. I tried: [1.1,) [1.1,] (1.1,) Etc. Each time it is trying to resolve that version exactly as typed. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 3:27 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored This functionality already exists in Maven 2.0. [1.0,) indicates = 1.0 - Brett On 11/1/05, Lukas Theussl [EMAIL PROTECTED] wrote: Right, but this would be something completely different from the current snapshot functionality. As I said in one of my earlier mails, if you want that functionality you can open a JIRA request for it (preferably with a patch attached ;) ). And of course, I retain all my reservations about automatic dependency upgrade as expressed before. But then, if you want it, it's your decision. :) -Lukas Brian E. Fox wrote: I think maybe what is being asked for is the ability to get the lastest non snapshot build? For example if wagon-ftp changes from 1.0 to 1.1, I want to automatically grab it. Maybe not the best decision, but still a possible option to allow people to choose. I think that in terms of versioning modules you have control over, this might be preferrable. This way a development team could depend on the latest sanctioned version without depending on unstable snapshot builds and without having to manually update all the poms everytime a new module is published. -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 1:01 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Hi, What if a released component on remote repository has any bugs? This just underscores my point, no? Generally, I think upgrading (or downgrading) a dependency is always something that should be done very carefully and very consciously, I wouldn't want to have that done automatically. Indicating a SNAPSHOT dependency is only useful if you know that a project is currently under heavy development and you want to stay up to date with changes on a, say, day-to-day basis (assuming the project publishes SNAPSHOTs that often). This implies that your project itself is currently changing frequently, and if something breaks from one day to the other, you know it might not be due to your own code, but to a changed dependency. As soon as a stable release gets out, you have to indicate explicitly (after testing) that you no longer want to use SNAPSHOTs, but stick to a particular stable version. If features of a component do not have to be changed to fix bugs, I think it's useful to replace this bad component on local repository with bug fixed component on remote repository automatically (after agreement). But how would you indicate which component is the good one? A SNAPSHOT always gets you the _latest_ development version, which is actually very rarely the most bug-free one! ;) -Lukas - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: keyword SNAPSHOT in depedency version is ignored
I was trying to use this in a parent version section. Probably not a supported use case? I have setup my projects so they all eventually derive from a super parent that contains things that apply to all my projects. How and where to deploy is an example of something I set there. I'd like to be able to make a change to the parent and have everything automatically pick up the new change. I have it setup to use snapshots now but I was trying to explore this as a possible alternative. The reason is that we have mirrors for central that point to maven-proxy. MP is configured to look at more than central and can usually find our snapshots however central is set to have snapshots turned off. That means everyone needs to define a second repository in their settings to bootstrap and find the parent. Previously, I was able to define all our repos in the super parent. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, November 03, 2005 6:58 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored What was the dependency? Do you have a test case? - Brett On 11/4/05, Brian E. Fox [EMAIL PROTECTED] wrote: I'm not able to make this work. I tried: [1.1,) [1.1,] (1.1,) Etc. Each time it is trying to resolve that version exactly as typed. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 3:27 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored This functionality already exists in Maven 2.0. [1.0,) indicates = 1.0 - Brett On 11/1/05, Lukas Theussl [EMAIL PROTECTED] wrote: Right, but this would be something completely different from the current snapshot functionality. As I said in one of my earlier mails, if you want that functionality you can open a JIRA request for it (preferably with a patch attached ;) ). And of course, I retain all my reservations about automatic dependency upgrade as expressed before. But then, if you want it, it's your decision. :) -Lukas Brian E. Fox wrote: I think maybe what is being asked for is the ability to get the lastest non snapshot build? For example if wagon-ftp changes from 1.0 to 1.1, I want to automatically grab it. Maybe not the best decision, but still a possible option to allow people to choose. I think that in terms of versioning modules you have control over, this might be preferrable. This way a development team could depend on the latest sanctioned version without depending on unstable snapshot builds and without having to manually update all the poms everytime a new module is published. -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 1:01 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Hi, What if a released component on remote repository has any bugs? This just underscores my point, no? Generally, I think upgrading (or downgrading) a dependency is always something that should be done very carefully and very consciously, I wouldn't want to have that done automatically. Indicating a SNAPSHOT dependency is only useful if you know that a project is currently under heavy development and you want to stay up to date with changes on a, say, day-to-day basis (assuming the project publishes SNAPSHOTs that often). This implies that your project itself is currently changing frequently, and if something breaks from one day to the other, you know it might not be due to your own code, but to a changed dependency. As soon as a stable release gets out, you have to indicate explicitly (after testing) that you no longer want to use SNAPSHOTs, but stick to a particular stable version. If features of a component do not have to be changed to fix bugs, I think it's useful to replace this bad component on local repository with bug fixed component on remote repository automatically (after agreement). But how would you indicate which component is the good one? A SNAPSHOT always gets you the _latest_ development version, which is actually very rarely the most bug-free one! ;) -Lukas -- -- - 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
Re: keyword SNAPSHOT in depedency version is ignored
Hi My point is what Brian explained. I'm sorry for wandering from the subject. Brett Porter wrote: This functionality already exists in Maven 2.0. [1.0,) indicates = 1.0 I tried this functionality and it works well! Thank you all! Katsuya Takahashi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: keyword SNAPSHOT in depedency version is ignored
Hi, What if a released component on remote repository has any bugs? This just underscores my point, no? Generally, I think upgrading (or downgrading) a dependency is always something that should be done very carefully and very consciously, I wouldn't want to have that done automatically. Indicating a SNAPSHOT dependency is only useful if you know that a project is currently under heavy development and you want to stay up to date with changes on a, say, day-to-day basis (assuming the project publishes SNAPSHOTs that often). This implies that your project itself is currently changing frequently, and if something breaks from one day to the other, you know it might not be due to your own code, but to a changed dependency. As soon as a stable release gets out, you have to indicate explicitly (after testing) that you no longer want to use SNAPSHOTs, but stick to a particular stable version. If features of a component do not have to be changed to fix bugs, I think it's useful to replace this bad component on local repository with bug fixed component on remote repository automatically (after agreement). But how would you indicate which component is the good one? A SNAPSHOT always gets you the _latest_ development version, which is actually very rarely the most bug-free one! ;) -Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: keyword SNAPSHOT in depedency version is ignored
I think maybe what is being asked for is the ability to get the lastest non snapshot build? For example if wagon-ftp changes from 1.0 to 1.1, I want to automatically grab it. Maybe not the best decision, but still a possible option to allow people to choose. I think that in terms of versioning modules you have control over, this might be preferrable. This way a development team could depend on the latest sanctioned version without depending on unstable snapshot builds and without having to manually update all the poms everytime a new module is published. -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 1:01 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Hi, What if a released component on remote repository has any bugs? This just underscores my point, no? Generally, I think upgrading (or downgrading) a dependency is always something that should be done very carefully and very consciously, I wouldn't want to have that done automatically. Indicating a SNAPSHOT dependency is only useful if you know that a project is currently under heavy development and you want to stay up to date with changes on a, say, day-to-day basis (assuming the project publishes SNAPSHOTs that often). This implies that your project itself is currently changing frequently, and if something breaks from one day to the other, you know it might not be due to your own code, but to a changed dependency. As soon as a stable release gets out, you have to indicate explicitly (after testing) that you no longer want to use SNAPSHOTs, but stick to a particular stable version. If features of a component do not have to be changed to fix bugs, I think it's useful to replace this bad component on local repository with bug fixed component on remote repository automatically (after agreement). But how would you indicate which component is the good one? A SNAPSHOT always gets you the _latest_ development version, which is actually very rarely the most bug-free one! ;) -Lukas - 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: keyword SNAPSHOT in depedency version is ignored
Right, but this would be something completely different from the current snapshot functionality. As I said in one of my earlier mails, if you want that functionality you can open a JIRA request for it (preferably with a patch attached ;) ). And of course, I retain all my reservations about automatic dependency upgrade as expressed before. But then, if you want it, it's your decision. :) -Lukas Brian E. Fox wrote: I think maybe what is being asked for is the ability to get the lastest non snapshot build? For example if wagon-ftp changes from 1.0 to 1.1, I want to automatically grab it. Maybe not the best decision, but still a possible option to allow people to choose. I think that in terms of versioning modules you have control over, this might be preferrable. This way a development team could depend on the latest sanctioned version without depending on unstable snapshot builds and without having to manually update all the poms everytime a new module is published. -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 1:01 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Hi, What if a released component on remote repository has any bugs? This just underscores my point, no? Generally, I think upgrading (or downgrading) a dependency is always something that should be done very carefully and very consciously, I wouldn't want to have that done automatically. Indicating a SNAPSHOT dependency is only useful if you know that a project is currently under heavy development and you want to stay up to date with changes on a, say, day-to-day basis (assuming the project publishes SNAPSHOTs that often). This implies that your project itself is currently changing frequently, and if something breaks from one day to the other, you know it might not be due to your own code, but to a changed dependency. As soon as a stable release gets out, you have to indicate explicitly (after testing) that you no longer want to use SNAPSHOTs, but stick to a particular stable version. If features of a component do not have to be changed to fix bugs, I think it's useful to replace this bad component on local repository with bug fixed component on remote repository automatically (after agreement). But how would you indicate which component is the good one? A SNAPSHOT always gets you the _latest_ development version, which is actually very rarely the most bug-free one! ;) -Lukas - 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: keyword SNAPSHOT in depedency version is ignored
This functionality already exists in Maven 2.0. [1.0,) indicates = 1.0 - Brett On 11/1/05, Lukas Theussl [EMAIL PROTECTED] wrote: Right, but this would be something completely different from the current snapshot functionality. As I said in one of my earlier mails, if you want that functionality you can open a JIRA request for it (preferably with a patch attached ;) ). And of course, I retain all my reservations about automatic dependency upgrade as expressed before. But then, if you want it, it's your decision. :) -Lukas Brian E. Fox wrote: I think maybe what is being asked for is the ability to get the lastest non snapshot build? For example if wagon-ftp changes from 1.0 to 1.1, I want to automatically grab it. Maybe not the best decision, but still a possible option to allow people to choose. I think that in terms of versioning modules you have control over, this might be preferrable. This way a development team could depend on the latest sanctioned version without depending on unstable snapshot builds and without having to manually update all the poms everytime a new module is published. -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 1:01 PM To: Maven Users List Subject: Re: keyword SNAPSHOT in depedency version is ignored Hi, What if a released component on remote repository has any bugs? This just underscores my point, no? Generally, I think upgrading (or downgrading) a dependency is always something that should be done very carefully and very consciously, I wouldn't want to have that done automatically. Indicating a SNAPSHOT dependency is only useful if you know that a project is currently under heavy development and you want to stay up to date with changes on a, say, day-to-day basis (assuming the project publishes SNAPSHOTs that often). This implies that your project itself is currently changing frequently, and if something breaks from one day to the other, you know it might not be due to your own code, but to a changed dependency. As soon as a stable release gets out, you have to indicate explicitly (after testing) that you no longer want to use SNAPSHOTs, but stick to a particular stable version. If features of a component do not have to be changed to fix bugs, I think it's useful to replace this bad component on local repository with bug fixed component on remote repository automatically (after agreement). But how would you indicate which component is the good one? A SNAPSHOT always gets you the _latest_ development version, which is actually very rarely the most bug-free one! ;) -Lukas - 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: keyword SNAPSHOT in depedency version is ignored
Hi Lukas, I had the same problem as Stefan ( I am a maven beginner also) and get the same explanation as you give. The fact is that I was expecting the same behavior as Stefan and maybe that can be a possible enhancement to put on the strack? Maybe I miss something but I don't see why it will not be possible. Regards. Gianfranco Oldani Original Message Follows From: Lukas Theussl [EMAIL PROTECTED] Reply-To: Maven Users List users@maven.apache.org To: Maven Users List users@maven.apache.org Subject: Re: keyword SNAPSHOT in depedency version is ignored Date: Thu, 27 Oct 2005 21:11:08 + This is a misunderstanding of the SNAPSHOT functionality, maven does _not_ replace SNAPSHOT with the latest available version of a project. Using a SNAPSHOT dependency still assumes that the project that you depend upon has actually published a SNAPSHOT. This is not the case for commons-logging. See http://maven.apache.org/maven-1.x/using/managing-dependencies.html#Using_SNAPSHOT_Dependencies Regards, Lukas Dr. Stefan Reisner wrote: I have created the following dependency in my maven project: dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId versionSNAPSHOT/version /dependency This results in the following behaviour being logged on the console when invoking maven: D:\workspace\de.syngenio.kompass.kikmaven __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 Attempting to download commons-logging-SNAPSHOT.jar. WARNING: Failed to download commons-logging-SNAPSHOT.jar. My expectation was that maven would replace SNAPSHOT (or for that any version value in which SNAPSHOT occurs as a substring) by the most current version available in the repository. What is going wrong here? I should add that I'm new to maven, so it's probably something stupid simple. Best regards, Dr. Stefan Reisner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Éradiquez enfin les fenêtres intempestives et surfez en toute tranquilité!!! http://toolbar.fr.msn.ch?DI=1057XAPID=2083 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: keyword SNAPSHOT in depedency version is ignored
Hey, I realized when writing the reply that the documentation is somehow misleading (at least if you don't read it carefully), we will rewrite the corresponding section to make it clearer. If you think that the functionality that you expected should be implemented, you could file a feature request on JIRA [1]. However, personally, I am not sure if I would want such a functionality. Having the latest releases downloaded automatically is not always what you want and could even be dangerous (what if the dependency project publishes a backwards-incompatible release?). Cheers, Lukas [1] http://jira.codehaus.org/browse/MAVEN (you have to open an account if you want to file issues) Gianfranco Oldani wrote: Hi Lukas, I had the same problem as Stefan ( I am a maven beginner also) and get the same explanation as you give. The fact is that I was expecting the same behavior as Stefan and maybe that can be a possible enhancement to put on the strack? Maybe I miss something but I don't see why it will not be possible. Regards. Gianfranco Oldani Original Message Follows From: Lukas Theussl [EMAIL PROTECTED] Reply-To: Maven Users List users@maven.apache.org To: Maven Users List users@maven.apache.org Subject: Re: keyword SNAPSHOT in depedency version is ignored Date: Thu, 27 Oct 2005 21:11:08 + This is a misunderstanding of the SNAPSHOT functionality, maven does _not_ replace SNAPSHOT with the latest available version of a project. Using a SNAPSHOT dependency still assumes that the project that you depend upon has actually published a SNAPSHOT. This is not the case for commons-logging. See http://maven.apache.org/maven-1.x/using/managing-dependencies.html#Using_SNAPSHOT_Dependencies Regards, Lukas Dr. Stefan Reisner wrote: I have created the following dependency in my maven project: dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId versionSNAPSHOT/version /dependency This results in the following behaviour being logged on the console when invoking maven: D:\workspace\de.syngenio.kompass.kikmaven __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 Attempting to download commons-logging-SNAPSHOT.jar. WARNING: Failed to download commons-logging-SNAPSHOT.jar. My expectation was that maven would replace SNAPSHOT (or for that any version value in which SNAPSHOT occurs as a substring) by the most current version available in the repository. What is going wrong here? I should add that I'm new to maven, so it's probably something stupid simple. Best regards, Dr. Stefan Reisner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Éradiquez enfin les fenêtres intempestives et surfez en toute tranquilité!!! http://toolbar.fr.msn.ch?DI=1057XAPID=2083 - 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: keyword SNAPSHOT in depedency version is ignored
This is a misunderstanding of the SNAPSHOT functionality, maven does _not_ replace SNAPSHOT with the latest available version of a project. Using a SNAPSHOT dependency still assumes that the project that you depend upon has actually published a SNAPSHOT. This is not the case for commons-logging. See http://maven.apache.org/maven-1.x/using/managing-dependencies.html#Using_SNAPSHOT_Dependencies Regards, Lukas Dr. Stefan Reisner wrote: I have created the following dependency in my maven project: dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId versionSNAPSHOT/version /dependency This results in the following behaviour being logged on the console when invoking maven: D:\workspace\de.syngenio.kompass.kikmaven __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 Attempting to download commons-logging-SNAPSHOT.jar. WARNING: Failed to download commons-logging-SNAPSHOT.jar. My expectation was that maven would replace SNAPSHOT (or for that any version value in which SNAPSHOT occurs as a substring) by the most current version available in the repository. What is going wrong here? I should add that I'm new to maven, so it's probably something stupid simple. Best regards, Dr. Stefan Reisner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
