You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eduardo Martins (JIRA)" <ji...@codehaus.org> on 2008/03/28 16:47:58 UTC
[jira] Created: (MNG-3487) The POM model should support not only
but also
The POM model should support not only <properties/> but also <property-files/>
------------------------------------------------------------------------------
Key: MNG-3487
URL: http://jira.codehaus.org/browse/MNG-3487
Project: Maven 2
Issue Type: New Feature
Components: POM
Reporter: Eduardo Martins
Currently there is no support for properties files in the POM, users often need this feature and use plugins to achieve that, but plugins can't touch elements in the POM which use a property to define some value, simply because that is defined before any phase is done.
I recommend adding a new <project/> element, <property-files>, which can have <property-file/> childs. Maven will load all properties in this file (no xml, usual format of property.name=property.value) the same way if they were defined inside <properties/>.
--
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
[jira] Commented: (MNG-3487) The POM model should support not only
but also
Posted by "Eduardo Martins (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129729#action_129729 ]
Eduardo Martins commented on MNG-3487:
--------------------------------------
Please note that this feature implies that the install phase must put a POM with the properties injected in the M2 repo, otherwise the POM is broken.
> The POM model should support not only <properties/> but also <property-files/>
> ------------------------------------------------------------------------------
>
> Key: MNG-3487
> URL: http://jira.codehaus.org/browse/MNG-3487
> Project: Maven 2
> Issue Type: New Feature
> Components: POM
> Reporter: Eduardo Martins
>
> Currently there is no support for properties files in the POM, users often need this feature and use plugins to achieve that, but plugins can't touch elements in the POM which use a property to define some value, simply because that is defined before any phase is done.
> I recommend adding a new <project/> element, <property-files>, which can have <property-file/> childs. Maven will load all properties in this file (no xml, usual format of property.name=property.value) the same way if they were defined inside <properties/>.
--
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
[jira] Updated: (MNG-3487) The POM model should support not only
but also
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3487:
------------------------------
Fix Version/s: 2.x
> The POM model should support not only <properties/> but also <property-files/>
> ------------------------------------------------------------------------------
>
> Key: MNG-3487
> URL: http://jira.codehaus.org/browse/MNG-3487
> Project: Maven 2
> Issue Type: New Feature
> Components: POM
> Reporter: Eduardo Martins
> Fix For: 2.x
>
>
> Currently there is no support for properties files in the POM, users often need this feature and use plugins to achieve that, but plugins can't touch elements in the POM which use a property to define some value, simply because that is defined before any phase is done.
> I recommend adding a new <project/> element, <property-files>, which can have <property-file/> childs. Maven will load all properties in this file (no xml, usual format of property.name=property.value) the same way if they were defined inside <properties/>.
--
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
[jira] Closed: (MNG-3487) The POM model should support not only
but also
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-3487.
------------------------------
Resolution: Won't Fix
We're not going to include references to external resources.
> The POM model should support not only <properties/> but also <property-files/>
> ------------------------------------------------------------------------------
>
> Key: MNG-3487
> URL: http://jira.codehaus.org/browse/MNG-3487
> Project: Maven 2
> Issue Type: New Feature
> Components: POM
> Reporter: Eduardo Martins
> Fix For: 3.x
>
>
> Currently there is no support for properties files in the POM, users often need this feature and use plugins to achieve that, but plugins can't touch elements in the POM which use a property to define some value, simply because that is defined before any phase is done.
> I recommend adding a new <project/> element, <property-files>, which can have <property-file/> childs. Maven will load all properties in this file (no xml, usual format of property.name=property.value) the same way if they were defined inside <properties/>.
--
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