[
http://jira.codehaus.org/browse/MNG-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106072
]
Adrian Petru Dimulescu commented on MNG-2046:
---------------------------------------------
I completely agree, I spent hours searching for a way to externalize build
properties only to find that Maven2 knowingly restricts this. You can't use
external properties files nor external XML entities.
I ended up describing my properties in the profiles.xml file which is the
"proper" way to do it.
In my case, I have unit tests that need to have access dynamically to some of
those properties. If they were a properties file, it would have been extremely
simple to read them. Now I have to code parsing profiles.xml ...
I really think that being able to externalize properties is a good idea. Having
a .properties file per developer with his own database etc. settings is really
simple way of describing configuration.
While I understand that Maven people want to avoid having multiple
configuration locations and want to describe everything in the pom, I think
that restricting external properties is really going to far. I will sincerely
think twice about using Maven in the future, mainly because of this problem.
> External property file in command line
> --------------------------------------
>
> Key: MNG-2046
> URL: http://jira.codehaus.org/browse/MNG-2046
> Project: Maven 2
> Issue Type: Improvement
> Components: Command Line
> Affects Versions: 2.0.2
> Reporter: Raphaël Corre
> Priority: Minor
> Fix For: 2.1.x
>
>
> It would be great to allow the option "-propertyfile" in the command line,
> like Ant does to load multi properties. For the moment, it's possible to do
> "'D", but for a single property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
