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

Hi Charles & everyone, > 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. Thank

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

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)

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)

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)

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)

1:46:59 PM Subject: Re: Please officially support RELEASE and LATEST (was: Re: dependency question) 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

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

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)

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 (was: Re: dependency question)

> 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