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
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
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
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
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
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
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
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
Analyzing the debug and error output should also give a clue. Maybe focus on
that and ignore the effective pom for now.
/Anders (mobile)
Den 20 dec 2010 17.05 skrev Ron Wheeler rwhee...@artifact-software.com:
Where is the reference to 1.3 coming from?
I think that was what the effective-pom was
