[ 
http://jira.codehaus.org/browse/MBUILDHELPER-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved MOJO-652 to MBUILDHELPER-3:
-------------------------------------------------

    Component/s:     (was: build-helper)
            Key: MBUILDHELPER-3  (was: MOJO-652)
        Project: Maven 2.x Build Helper Plugin  (was: Mojo)

> build-helper (attach-artifact): allow user to attach artifacts listed in a 
> file external to pom.xml
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MBUILDHELPER-3
>                 URL: http://jira.codehaus.org/browse/MBUILDHELPER-3
>             Project: Maven 2.x Build Helper Plugin
>          Issue Type: Bug
>            Reporter: Alan D. Salewski
>         Attachments: MOJO-652-build-helper-1.patch
>
>
> I've come across a scenario in which I need to specify attachment artifacts 
> in a file external to {{pom.xml}}. The specific motivation is for a file 
> whose name is derived, in part, from modified values of maven project 
> properties. I have an assembly that creates an RPM file, but the RPM system 
> does not allow dashes in the version number (the dash _after_ the version 
> number is the separator between the artifact version number and the RPM 
> packaging number). Obviously, this does not work when dealing with a SNAPSHOT 
> version of my project becuase the format of the value in 
> '{{$project.version}}}' is '{{fN.N.N\-SNAPSHOT}}' .
> As a workaround, I have code that ensures that the dash between the artifact 
> version and "SNAPSHOT" gets changed to an underscore char for the generated 
> RPM file. However, I do not have a good way of telling the 
> {{build\-helper\-maven\-plugin}} the name of the file (which has to be 
> constructed dynamically). If maven-2.x provided an easy way to modify 
> properties within '{{pom.xml}}' using a {{sed}}-like replacement facility, 
> then I would change it there. As it is, though, the easiest way I've found to 
> do such things is in external files using the {{maven-antrun-plugin}} and the 
> {{ant}} '{{copy}}' task (with a configured '{{filterchain}}').
> I have a patch against version 1.0 of the {{build\-helper\-maven\-plugin}} 
> that allows the user to specify artifacts to attach in an external file, in 
> '{{pom.xml}}' (the current way), or both. I'll upload that patch once I get 
> an issue number from jira.

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

        

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to