I just found an issue:
The new project/pom.xml configures and runs the maven-eclipse.plugin:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<skip>false</skip>
<pde>true</pde>
<!-- Workaround for http://jira.codehaus.org/browse/MECLIPSE-94 -->
<eclipseProjectDir>..</eclipseProjectDir>
<!-- We don't want any sources or javadocs jars -->
<downloadSources>false</downloadSources>
<downloadJavadocs>false</downloadJavadocs>
</configuration>
</plugin>
This configuration in inherited by the sub-projects. It is required to
overwrite the configuration in each sub-project to fix the generation
of Eclipse project files.
I added the following for shared/pom.xml, the same must be added to
the other sub-projects:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<pde>false</pde>
<eclipseProjectDir>${eclipse.projectDir}</eclipseProjectDir>
<downloadSources>true</downloadSources>
<downloadJavadocs>true</downloadJavadocs>
</configuration>
</plugin>
Is this acceptable, or is there a way to prevent configuration inheritance?
Kind Regards,
Stefan
On Mon, Jan 31, 2011 at 2:42 PM, Stefan Seelmann <[email protected]> wrote:
> Hi devs,
>
> I'd like to release a new TLP pom (version 19).
>
> Changes:
> - Full Maven 3 support, including site generation
> - Dropped Maven 2 support
> - Updated plugin versions
> - Removed outdated mailing list archives
>
> The tagged pom can be found at [1], the staging repository can be found at
> [2].
>
> I'll continue to release the staging repository after the grace period
> of 4 hours.
>
> Kind Regards,
> Stefan
>
>
> [1] https://svn.apache.org/repos/asf/directory/project/tags/19/
> [2] https://repository.apache.org/content/repositories/orgapachedirectory-018/
>
