Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

2017-04-24 Thread Charles Honton
To prevent SNAPSHOT churn you can use a plugin like exists-maven-plugin (https://chonton.github.io/exists-maven-plugin/0.0.2/plugin-info.html ) to prevent re-releasing unchanged artifacts. chas > On Apr 24, 2017, at 1:52 PM,

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

2017-04-24 Thread mike digioia
SUBMIT ME On Mon, Apr 24, 2017 at 1:52 PM, Curtis Rueden wrote: > Hi Karl, > > Thanks very much for your reply! > > > Not only for displaying...you can also use it to update them... > > Understood. But I actually don't want to always auto-update everything to > latest releases. The point of the

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

2017-04-24 Thread Curtis Rueden
Hi Karl, Thanks very much for your reply! > Not only for displaying...you can also use it to update them... Understood. But I actually don't want to always auto-update everything to latest releases. The point of the BOM is that the versions it references have been tested to work together. Especi

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

2017-04-24 Thread Karl Heinz Marbaise
Hi, On 24/04/17 19:46, Curtis Rueden wrote: Hi Jesse, Prefer to harden the version # in a corporate pom. Then use versions-m-p to detect and update bulk dependencies across all our projects. We manage about 350 dependencies in the corporate pom Definitely agreed. I am managing a similar numb

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

2017-04-24 Thread Richard Sand
Are you using the versions plugin? I can't live without it, I've got it in my corporate master base POM http://www.mojohaus.org/versions-maven-plugin/ -Richard -- Original Message -- From: "Curtis Rueden" To: "Maven Users List" Sent: 4/24/2017 1:46:59 PM Subject: Re: Please official

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

2017-04-24 Thread Curtis Rueden
Hi Jesse, > Prefer to harden the version # in a corporate pom. Then use > versions-m-p to detect and update bulk dependencies across all our > projects. We manage about 350 dependencies in the corporate pom Definitely agreed. I am managing a similar number, and indeed versions-m-p is super nice f

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

2017-04-24 Thread jieryn
Prefer to harden the version # in a corporate pom. Then use versions-m-p to detect and update bulk dependencies across all our projects. We manage about 350 dependencies in the corporate pom, and that doesn't even include the huge number that are scope=import for Arquillian and Selenium, etc. On M

Re: Please officially support RELEASE and LATEST

2017-04-24 Thread Rick Huff
Curtis, For what it's worth, I completely agree. This is a broken part of Maven that we've learned to work around because of a theoretical benefit. I can agree with needing to specify a version or version range for other dependencies, but for my code in non-Prod environments -- I want LATES

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

2017-04-24 Thread Curtis Rueden
> I would like to argue for the inclusion / restoration / continued > support of the RELEASE and LATEST tags. Really? No one else cares enough to respond? I am very often running into use cases where the easiest solution seems to be LATEST and/or RELEASE. I have to manage a large Bill of Material