[
https://issues.apache.org/jira/browse/MSHARED-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068961#comment-15068961
]
Michael Osipov commented on MSHARED-288:
----------------------------------------
Neither senstive data belong into the POM nor should one hardcode paths to
senstive information. Use profiles in {{settings.xml}}. This should be
dynamic/configurable inside your library.
> Allow Maven Archiver to not include pom.xml and/or pom.properties files
> -----------------------------------------------------------------------
>
> Key: MSHARED-288
> URL: https://issues.apache.org/jira/browse/MSHARED-288
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
> Affects Versions: maven-archiver-2.4
> Reporter: Justin Wesley
> Priority: Minor
>
> Currently, when configuring the archive for a package, the developer can only
> include both pom.properties and pom.xml files, or neither of them. They can't
> pick to only include one or the other.
> Some projects may want to ability to determine programatically basic
> information of the jar they have by using the properties file, but not
> include the pom.xml file as it may contain information that may expose
> information about the build that could be specific to a build machine or have
> locations to a license file or have the license key in the pom.xml that
> should/can not be public.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
