You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/05/23 17:30:00 UTC
[jira] [Commented] (KARAF-7157) Editing a factory config lacking a
FILEINSTALL_FILE_NAME prop. produces a file with incorrect filename
[ https://issues.apache.org/jira/browse/KARAF-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350110#comment-17350110 ]
ASF GitHub Bot commented on KARAF-7157:
---------------------------------------
jassuncao opened a new pull request #1380:
URL: https://github.com/apache/karaf/pull/1380
When generating a filename for a configuration lacking a
FILEINSTALL_FILE_NAME property, the type of configuration is taken in
consideration and a filename following the convention
<factoryPID>-<identifier>.cfg will be used for factory configs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> Editing a factory config lacking a FILEINSTALL_FILE_NAME prop. produces a file with incorrect filename
> ------------------------------------------------------------------------------------------------------
>
> Key: KARAF-7157
> URL: https://issues.apache.org/jira/browse/KARAF-7157
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 4.3.2
> Reporter: Joao Assuncao
> Priority: Minor
>
> Using config:edit to edit a factory configuration that lacks a FILEINSTALL_FILE_NAME property will result in the creation of a file with a filename that does't follow the convention:<factory_pid>-<identifier>.cfg.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)