[
https://issues.apache.org/jira/browse/MNG-6154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811060#comment-15811060
]
Michael Osipov commented on MNG-6154:
-------------------------------------
Never likely to happen. It has been a deliberate choice not to have external
files to depend upon. The POM has to be complete. The diametral result is the
mess caused by Ant, includes all over the place.
> load properties from file not using plugin
> ------------------------------------------
>
> Key: MNG-6154
> URL: https://issues.apache.org/jira/browse/MNG-6154
> Project: Maven
> Issue Type: New Feature
> Reporter: Miroslav Zaťko
>
> In many usecases there is need of load properties from file at build start.
> It could be probably done similar way as it is for {{<settingsSecurity>}} in
> {{settings-security.xml}} where we can use {{<relocation>}} referring file
> where is master password stored instead of listing it directly. However
> something like
> {quote}
> <properties>
> <include>path1/to1/file1</include>
> <include>path2/to2/file2</include>
> ..........
> </properties>
> {quote}
> would be better probably and we can offer this property-name.
> Other possibility, maybe easier is to make values from {{<filters>}} more
> like properties and make it's values available directly in pom.
> This feature is definitely missing in maven since beginning. Using plugins
> like properties-maven-plugin is not usable when running particular goal (e.g.
> {{mvn liquibase:update}}), not lifecycle build.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
