[
https://issues.apache.org/jira/browse/MARTIFACT-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264662#comment-17264662 ]
Herve Boutemy commented on MARTIFACT-6:
---------------------------------------
now that I opened this issue and took time to clearly describe it, generating a buildinfo file in the root directory is not hard: what is harder is to install/deploy it, because root artifact and attached sub-artifacts have already been deployed
then it would be easy to generate a buildinfo file *on local disk* that could not be deployed during the buildinfo goal: this could perhaps be a good initial compromise to discover next steps
> create buildinfo file in root artifact instead of last module
> -------------------------------------------------------------
>
> Key: MARTIFACT-6
> URL:
https://issues.apache.org/jira/browse/MARTIFACT-6> Project: Maven Artifact Plugin
> Issue Type: New Feature
> Components: artifact:buildinfo
> Affects Versions: 0.1
> Reporter: Herve Boutemy
> Priority: Major
>
> when used with multi-modules build, current implementation creates the buildinfo file in the last module (that will be deployed to repository, more precisely)
> This is because buildinfo records fingerprints/hashes of the result of the build, then artifacts to be fingerprinted are available only at the end of the build
> It works, but it adds a level of complexity to find the buildinfo file
> It would be a lot easier to use if buildinfo could be generated (and eventually deployed) in root directory
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Locked
