You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Benjamin Bentmann (JIRA)" <de...@velocity.apache.org> on 2008/10/28 00:21:44 UTC
[jira] Created: (VELOCITY-638) Lock down version of reporting
plugins in POM
Lock down version of reporting plugins in POM
---------------------------------------------
Key: VELOCITY-638
URL: https://issues.apache.org/jira/browse/VELOCITY-638
Project: Velocity
Issue Type: Improvement
Components: Build, Engine
Affects Versions: 1.6-beta1
Reporter: Benjamin Bentmann
Priority: Minor
Attachments: VELOCITY-638.patch
Leaving plugin versions unspecified (i.e. blindly relying on LATEST) is a bad practice as it sacrifies build reproducibility. Even if the POM itself is not used for the actual build, it would promote best practices to consumers when fixed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Updated: (VELOCITY-638) Lock down version of reporting
plugins in POM
Posted by "Benjamin Bentmann (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated VELOCITY-638:
---------------------------------------
Attachment: VELOCITY-638.patch
> Lock down version of reporting plugins in POM
> ---------------------------------------------
>
> Key: VELOCITY-638
> URL: https://issues.apache.org/jira/browse/VELOCITY-638
> Project: Velocity
> Issue Type: Improvement
> Components: Build, Engine
> Affects Versions: 1.6-beta1
> Reporter: Benjamin Bentmann
> Priority: Minor
> Attachments: VELOCITY-638.patch
>
>
> Leaving plugin versions unspecified (i.e. blindly relying on LATEST) is a bad practice as it sacrifies build reproducibility. Even if the POM itself is not used for the actual build, it would promote best practices to consumers when fixed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Resolved: (VELOCITY-638) Lock down version of reporting
plugins in POM
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna resolved VELOCITY-638.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.6
> Lock down version of reporting plugins in POM
> ---------------------------------------------
>
> Key: VELOCITY-638
> URL: https://issues.apache.org/jira/browse/VELOCITY-638
> Project: Velocity
> Issue Type: Improvement
> Components: Build, Engine
> Affects Versions: 1.6-beta1
> Reporter: Benjamin Bentmann
> Priority: Minor
> Fix For: 1.6
>
> Attachments: VELOCITY-638.patch
>
>
> Leaving plugin versions unspecified (i.e. blindly relying on LATEST) is a bad practice as it sacrifies build reproducibility. Even if the POM itself is not used for the actual build, it would promote best practices to consumers when fixed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org