You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Michael Kurz (JIRA)" <de...@myfaces.apache.org> on 2010/02/01 13:47:51 UTC

[jira] Updated: (TOMAHAWK-1483) Build Failure on Maven 2.2.1

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

Michael Kurz updated TOMAHAWK-1483:
-----------------------------------

    Status: Patch Available  (was: Open)

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