maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Commented] (MSHARED-362) Support removing default manifest entries with maven-archiver plugin
Date Sat, 02 Jan 2016 20:36:39 GMT


Robert Scholte commented on MSHARED-362:

IIRC some elements are still added, even when you don't specify them in a custom manifest
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:
>             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
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

View raw message