denys-popov

# get commitId
git log -n 1 --pretty=%H

denys-popov

mvn versions:display-dependency-updates

denys-popov

If you always want to use the newest version, Maven has two keywords you can use as an alternative to version ranges. You should use these options with care as you are no longer in control of the plugins/dependencies you are using.

When you depend on a plugin or a dependency, you can use the a version value of LATEST or RELEASE. LATEST refers to the latest released or snapshot version of a particular artifact, the most recently deployed artifact in a particular repository. RELEASE refers to the last non-snapshot release in the repository. In general, it is not a best practice to design software which depends on a non-specific version of an artifact. If you are developing software, you might want to use RELEASE or LATEST as a convenience so that you don't have to update version numbers when a new release of a third-party library is released. When you release software, you should always make sure that your project depends on specific versions to reduce the chances of your build or your project being affected b

denys-popov

#
# Screen resoure file by chexov@rtf-15
#
#

### Caption set
#caption always "%{yK}|%{yK}%c|  %{yK}%-Lw%{yK}%50>%{Ky}%n%f* %t%{-}%+Lw%<%{- Wk}"

#caption always "%d.%m.%y %0c%{=b kW} %l %{=r kd}%-Lw%{= bd}%50>%n%f* %t%{-}%+Lw%<%{- Wk}"

denys-popov

# ./apps/ROOT/WEB-INF/classes/org/apache/maven/archiva/security.properties

security.policy.password.rule.reuse.enabled=true

security.policy.password.previous.count=1
security.policy.password.expiration.enabled=false
security.policy.allowed.login.attempt=15
security.policy.strict.enforcement.enabled=false
security.policy.strict.force.password.change.enabled=false
security.policy.unlockable.accounts=admin