Hi again,
Actually when running mvn help:effective-pom I can see all plugins from the
parent as expected, but when running it after release:prepare (which
actually faills) they are not there anymore. It seems that release:prepare
ignores the parent's plugins for the project it runs the release for.
Though, when plugins are defined in the project's scope and not the parent's
the release:prepare works as expected. The plugin in the parent is defines
parent as follows:
<project>
.
.
.
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.0.2</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
<encoding>UTF-8</encoding>
</configuration>
</plugin>
<plugins>
<build>
<project>
Piotr
On Mon, Dec 20, 2010 at 2:57 PM, Anders Hammar <[email protected]> wrote:
> Check the project's effective pom.
> mvn help:effective-pom
>
> Most likely what you think should be inherited isn't. How is m-compiler-p
> declared in the parent?
>
> /Anders
>
> On Mon, Dec 20, 2010 at 14:50, Piotr Skawinski <
> [email protected]> wrote:
>
> > Hi,
> >
> > I'm having problems using release:prepare plugin on a project that
> inherits
> > from a parent project. It seems that it cannot see the plugins from the
> > parent project and fails on compiling java vesion 1.6 classes claiming
> that
> > 1.3 version does not support annotations. It works fine with clean
> install.
> > The maven-compiler-plugin is defined in the parent project. What can be
> the
> > problem?
> >
> > thanks in advance,
> >
> > Piotr
> >
>
