You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2019/09/08 15:12:00 UTC
[jira] [Commented] (MSHARED-835) add an API to not define
Build-Jdk-Spec default manifest entry
[ https://issues.apache.org/jira/browse/MSHARED-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16925188#comment-16925188 ]
Hudson commented on MSHARED-835:
--------------------------------
Build succeeded in Jenkins: Maven TLP » maven-archiver » master #16
See https://builds.apache.org/job/maven-box/job/maven-archiver/job/master/16/
> add an API to not define Build-Jdk-Spec default manifest entry
> --------------------------------------------------------------
>
> Key: MSHARED-835
> URL: https://issues.apache.org/jira/browse/MSHARED-835
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-archiver
> Affects Versions: maven-archiver-3.4.0
> Reporter: Hervé Boutemy
> Assignee: Hervé Boutemy
> Priority: Major
> Fix For: maven-archiver-3.4.1
>
>
> in general, packaging plugins package content resulting from JDK compiler, then having {{Build-Jdk-Spec}} as default manifest entry by default is a good idea.
> But a few plugins do not package any compiled content: maven-source-plugin for example.
> For these, disabling this default entry is useful to get reproducible content whatever the JDK version is.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)