[ 
https://issues.apache.org/jira/browse/TOMAHAWK-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leonardo Uribe updated TOMAHAWK-1483:
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.10-SNAPSHOT
         Assignee: Leonardo Uribe
           Status: Resolved  (was: Patch Available)

Thanks to Michael Kurz for provide this patch

> Build Failure on Maven 2.2.1
> ----------------------------
>
>                 Key: TOMAHAWK-1483
>                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1483
>             Project: MyFaces Tomahawk
>          Issue Type: Bug
>          Components: Build Process (Assembly)
>    Affects Versions: 1.1.10-SNAPSHOT
>         Environment: Windows 7, Maven 2.2.1
>            Reporter: Michael Kurz
>            Assignee: Leonardo Uribe
>             Fix For: 1.1.10-SNAPSHOT
>
>         Attachments: TOMAHAWK-1483.patch
>
>
> We had some strange troubles over here building the Tomahawk trunk. The build 
> succeeded on one machine and failed on another. After some investigations we 
> found out that it is working with Maven 2.0.10 and not working with Maven 
> 2.2.1 (generated source folders are not used in core12 and core20).
> The problem seems to be, that the build-helper-maven-plugin is defined twice 
> in core12 and core20. The first time it adds the following directories in 
> phase generate-sources:
> ${project.build.directory}/shared_sources
> ${project.build.directory}/tomahawk12_sources
> The second time it adds the following directories in phase process-sources:
> ${project.build.directory}/shared_sources
> The funny thing is, with Maven 2.2.1 the first plugin execution in phase 
> generate-sources never seems to be called. When I remove the second one it 
> works as expected.
> Anyway, do we need the second execution of the plugin in phase 
> process-sources? I don't see a reason.
> Thanks to Ingo Hofmann for pointing me to this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to