[
https://issues.apache.org/jira/browse/MSHARED-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076656#comment-15076656
]
Robert Scholte commented on MSHARED-362:
----------------------------------------
IIRC some elements are still added, even when you don't specify them in a
custom manifest file.
So it is personal that you don't like it. It is the fact that the local machine
username is used, or that the jar can be traced back to you?
In both private (work) and open development I see enough benefits of it. In
case I'm hitting issues with a specific jar and can't regenerate that artifact
it might help to know who made it and how he did it.
Why don't you see it as some kind of reward that you released this jar?
The original request was about an option to remove the Build-By, not to drop it
by default.
> Support removing default manifest entries with maven-archiver plugin
> --------------------------------------------------------------------
>
> Key: MSHARED-362
> URL: https://issues.apache.org/jira/browse/MSHARED-362
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-archiver
> Affects Versions: maven-archiver-2.4.2, maven-archiver-2.5
> Reporter: Richard Neish
> Priority: Minor
>
> As described in the StackOverflow question at
> http://stackoverflow.com/q/25098307/274350 maven-archiver should allow the
> user to remove the default manifest entries, such as "Built-By:"
> Currently it is possible to set an empty value for these default entries, but
> not to remove them from the manifest.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
