You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/09/06 22:46:17 UTC
[jira] [Closed] (MASSEMBLY-542) Create bill of materials
[ https://issues.apache.org/jira/browse/MASSEMBLY-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MASSEMBLY-542.
------------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.
> Create bill of materials
> ------------------------
>
> Key: MASSEMBLY-542
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-542
> Project: Maven Assembly Plugin
> Issue Type: New Feature
> Reporter: Max Schaefer
>
> I would like the assembly plugin to produce a kind of bill of materials xml.
> That should tell where each file came from.
> E.g. if in a dependency set the files are renamed via the output filename mapping I would like to know what was the original maven coordinate.
> If an archive is unpacked I would like to know which files were extracted.
> That would make it much easier to track down the maven artifact that originally contained certain files of my assembly.
> The bill of materials could even transformed into a maven report.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)