You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/04/27 19:35:46 UTC

[jira] Reopened: (MNG-357) 'build' section of POM does not appears to be inherited

     [ http://jira.codehaus.org/browse/MNG-357?page=all ]
     
John Casey reopened MNG-357:
----------------------------


There appears to be a bug in the handling of pluginManagement inheritance and also in the merging of pluginManagement-based data with the local-POM's plugin specification. I'm reopening this in order to track the fix...

> 'build' section of POM does not appears to be inherited
> -------------------------------------------------------
>
>          Key: MNG-357
>          URL: http://jira.codehaus.org/browse/MNG-357
>      Project: m2
>         Type: Bug
>   Components: maven-core
>     Versions: 2.0-alpha-1
>     Reporter: Peter van de Hoef

>
>
> It appears that the <build> section is (completely) inherited if it is not present in the derived POM, but if a <build> section is specified in the derived POM, everything from the base POM is thrown away and only the settings of the derived POM are used.
> In my parent POM I have a <build> section which specifies the source directory and some parameters for the java compiler:
>    <build>
>        <sourceDirectory>src</sourceDirectory>
>        <plugins>
>            <plugin>
>                <groupId>org.apache.maven.plugins</groupId>
>                <artifactId>maven-compiler-plugin</artifactId>
>                <version>1.0-alpha-2-SNAPSHOT</version>
>                <configuration>
>                    <source>1.5</source>
>                    <target>1.5</target>
>                </configuration>
>            </plugin>
>        </plugins>
>    </build>
> In a derived POM, the source directory is different, so a new <build> section is specified:
>    <build>
>        <sourceDirectory>module/src</sourceDirectory>
>    </build>
> The overridden source directory is effectuated in this second POM, but it appears that  the java compiler settings have disappeared (it starts e.g. complaining about JDK 1.4 features like assertions). If I do not specify a <build> section in the derived POM, the settings of the base POM are inherited.

-- 
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, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org