You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2022/10/14 06:48:00 UTC
[jira] [Commented] (MENFORCER-427) Rule for no version ranges, version placeholders or SNAPSHOT versions
[ https://issues.apache.org/jira/browse/MENFORCER-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617514#comment-17617514 ]
Hudson commented on MENFORCER-427:
----------------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-enforcer » master #75
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/master/75/
> Rule for no version ranges, version placeholders or SNAPSHOT versions
> ---------------------------------------------------------------------
>
> Key: MENFORCER-427
> URL: https://issues.apache.org/jira/browse/MENFORCER-427
> Project: Maven Enforcer Plugin
> Issue Type: New Feature
> Reporter: Simon
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: next-release
>
>
> In order to create a reproducible build, it could make sense to fix all versions of direct and transitive dependencies.
> This can be done adding this in {{<dependencyManagement>}}.
> It would be great to add a rule to ensure that all dependency versions are fixed (i.e. need not to be resolved during build).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)