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 :)

Piotr

On Mon, Dec 20, 2010 at 5:04 PM, Ron Wheeler <[email protected]
> 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<[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
>>>>
>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to