[
https://issues.apache.org/jira/browse/METRON-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456462#comment-16456462
]
ASF GitHub Bot commented on METRON-1541:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1003
@mmiklavc I don't believe profiler.j2 should. That template looks like it
actually gets used directly. It should probably be made more consistent with
the other properties files, but I'm inclined to leave that as follow-on.
If we're dropping the old enrichment.properties.j2, should that be dropped
from metron-enrichment? I'm not familiar enough with how that all lines up to
know if they can be safely dropped.
> Mvn clean results in git status having deleted files.
> -----------------------------------------------------
>
> Key: METRON-1541
> URL: https://issues.apache.org/jira/browse/METRON-1541
> Project: Metron
> Issue Type: Bug
> Reporter: Justin Leet
> Priority: Minor
>
> When you run mvn clean, you end up with the following git status.
> deleted:
> metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/templates/enrichment-splitjoin.properties.j2
> deleted:
> metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/templates/enrichment-unified.properties.j2
>
> These files should likely be in the .gitignore and deleted from source
> control.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
