Possibly generateReleasePoms=true could be the problem. It is now deprecated, so I wouldn't be surprised if not too many people use it and/or it's not tested fully.
I suggest that you stop using it. There's a separate goal for that if you really need it. Btw, I assume you have tried upgrading to the latest version of the plugin? /Anders On Wed, Dec 22, 2010 at 09:53, Piotr Skawinski < piotr.skawinski.ma...@gmail.com> wrote: > The error occurs while using generateReleasePoms=true as configuration > within maven-release-plugin. The maven-release-plugin will generate a > release-pom.xml for the release and it is being used by maven for the > build. > Looking into release-pom.xml I dont see any reference to java 1.6 version > which is defined within the plugins part in the parent project, so it is > not > strange why it fails on building java code with annotations, since maven > uses java 1.3 version as default. My question is why release-pom.xml is not > getting plugins from the parent project? Could it be that this is a bug > inside maven-release-plugin? The release works fine with > generateReleasePoms=false. > > Piotr > > On Tue, Dec 21, 2010 at 5:31 PM, Ron Wheeler < > rwhee...@artifact-software.com > > wrote: > > > On 21/12/2010 6:40 AM, Piotr Skawinski wrote: > > > >> Hi Ron, > >> > >> There's actually no reference to 1.3, that is what what makes it strange > >> :) > >> The m-compiler-p is defined in the parent pom to use version 1.6, but > >> somehow seems to be ignored by release:prepare. Maven is using version > 1.3 > >> to compile with per default, unless you define the java version through > >> m-compiler-p, which I actually do. Though, it seems to be ignored by > >> release:prepare. When running clean install it works fine. I don't quite > >> understand what you mean by using effective-pom. I thought it was > intented > >> to be used especially in this cas to see the real pom seen by maven :) > >> > > Never seen any reference to 1.3 in anything that we have done with Maven > > over the last 3 years. > > We use Eclipse/STS as our IDE so we have GUI controls to set to control > > Maven and it is pretty easy to see what compiler is being requested, what > > JRE is being used for Maven tasks, etc. > > > > What IDE are you using and how do you build with Maven? > > > > I really like the Eclipse/STS from Springsource and everyone in the forum > > is probably tired of hearing me mention it but it makes Eclipse a > pleasure > > to install (biggest reason we moved from standard eclipse) and it makes > > Maven very easy to use. > > > > I am also a big fan of Sonotype's Nexus and really recommend getting a > repo > > as quickly as possible if you are going to use Maven. > > Other repos also exist but I only know Nexus. > > > > Ron > > > > > > > > Piotr > >> > >> On Mon, Dec 20, 2010 at 5:04 PM, Ron Wheeler< > >> rwhee...@artifact-software.com > >> > >>> wrote: > >>> Where is the reference to 1.3 coming from? > >>> I think that was what the effective-pom was for, not to see if the > >>> plug-ins > >>> were there but to find out who is asking for 1.3. > >>> > >>> Ron > >>> > >>> > >>> > >>> On 20/12/2010 10:05 AM, Piotr Skawinski wrote: > >>> > >>> 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<and...@hammar.net> > >>>> 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< > >>>>> piotr.skawinski.ma...@gmail.com> 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 > >>>>>> > >>>>>> > >>>>>> > --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >>> For additional commands, e-mail: users-h...@maven.apache.org > >>> > >>> > >>> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
