You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2022/02/09 07:18:00 UTC

[jira] [Updated] (MARTIFACT-28) warn if project.build.outputTimestamp has not been defined in reactor but in independent parent

     [ https://issues.apache.org/jira/browse/MARTIFACT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herve Boutemy updated MARTIFACT-28:
-----------------------------------
    Description: 
with MARTIFACT-27, we check if reproducible timestamp is defined: that's a good first check

it's also useful (even if not absolutely mandatory) to check that the timestamp is defined in the reactor, so its value is updated during the release process: inheriting value from independent parent release will give a timestamp that represents the parent release, which is probably not really what users want = match their current release timestamp

  was:
with MARTIFACT-27, we check if reproducible timestamp is defined: that's a good first check

it's also useful (even if not absolutely mandatory) that the timestamp is defined in the reactor, so its value is updated during the release process


> warn if project.build.outputTimestamp has not been defined in reactor but in independent parent
> -----------------------------------------------------------------------------------------------
>
>                 Key: MARTIFACT-28
>                 URL: https://issues.apache.org/jira/browse/MARTIFACT-28
>             Project: Maven Artifact Plugin
>          Issue Type: Improvement
>    Affects Versions: 3.1.0
>            Reporter: Herve Boutemy
>            Assignee: Herve Boutemy
>            Priority: Major
>             Fix For: 3.2.0
>
>
> with MARTIFACT-27, we check if reproducible timestamp is defined: that's a good first check
> it's also useful (even if not absolutely mandatory) to check that the timestamp is defined in the reactor, so its value is updated during the release process: inheriting value from independent parent release will give a timestamp that represents the parent release, which is probably not really what users want = match their current release timestamp



--
This message was sent by Atlassian Jira
(v8.20.1#820001)