You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2006/06/22 16:56:40 UTC

[jira] Commented: (MNG-2301) Maven Archiver deleteing already existing pom.properties file.

    [ http://jira.codehaus.org/browse/MNG-2301?page=comments#action_67949 ] 

John Casey commented on MNG-2301:
---------------------------------

IMO, this could be a vector for introducing false data which may eventually be depended upon (even unintentionally)...I'd tend to say that this file should *always* be generated.

What reason do you have for doing this?



> Maven Archiver deleteing already existing pom.properties file.
> --------------------------------------------------------------
>
>          Key: MNG-2301
>          URL: http://jira.codehaus.org/browse/MNG-2301
>      Project: Maven 2
>         Type: Bug

>   Components: maven-archiver
>     Versions: 2.0.4
>     Reporter: Sharmarke Aden
>  Attachments: maven-archiver_pomDelete.patch
>
>
> My project has it's own pom.properties file and it seems that maven archiver is deleting it right after packaging the application. Any particular reason why it's doing this? It seems to me the archiver shouldn't be deleting the file if it already exists. It should delete the file if it doesn't exists otherwise it should add the necessary information (version, groupId, etc) to the file and leave it be. I have attached a patch that fixes the issue. 
> Also note that this patch adds the "builtOn" property to the pom.properties which is satisfy the following enhancement request: http://jira.codehaus.org/browse/MNG-1830 

-- 
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