[
https://issues.apache.org/jira/browse/MARTIFACT-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MARTIFACT-8.
---------------------------------
Resolution: Fixed
done in
https://github.com/apache/maven-artifact-plugin/commit/7ea7f796a2310fbd4153e7ccdb65e4d9388f1b4a
and aggregate artifact id added to buildinfo, to discover from root copy in
which module the original buildinfo was copied from, in
https://github.com/apache/maven-artifact-plugin/commit/9e7bb8716c8d6c819ae9e6e221993d3cadcfab37
> multi-module: copy aggregate buildinfo to root target
> -----------------------------------------------------
>
> Key: MARTIFACT-8
> URL: https://issues.apache.org/jira/browse/MARTIFACT-8
> Project: Maven Artifact Plugin
> Issue Type: New Feature
> Components: artifact:buildinfo
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Priority: Major
> Fix For: 0.1
>
>
> as seen in MARTIFACT-6, in multi-module builds, aggregate buildinfo can be
> generated and attached for deploy only in the last module, even if from a
> user point of view, root would be much easier to understand
> attaching buildinfo to root module for deployment is tricky, because root
> module deployment already happened
> but it's easy to copy buildinfo to root target dir, with root artifactId: at
> least locally on disk, the buildinfo will be easier to find
--
This message was sent by Atlassian Jira
(v8.3.4#803005)