[jira] Commented: (MNG-2565) plugin version aren't taken from pluginManagement in a sub-sub-modules

2007-06-19 Thread Emmanuel Venisse (JIRA)

[ 
http://jira.codehaus.org/browse/MNG-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100058
 ] 

Emmanuel Venisse commented on MNG-2565:
---

I think we can close it, I can't reproduce it with 2.0.6.
I don't have tested the issue described by kenney

> plugin version aren't taken from pluginManagement in a sub-sub-modules
> --
>
> Key: MNG-2565
> URL: http://jira.codehaus.org/browse/MNG-2565
> Project: Maven 2
>  Issue Type: Bug
>  Components: Inheritance and Interpolation
>Affects Versions: 2.0.5
>Reporter: Emmanuel Venisse
>Priority: Critical
> Fix For: Reviewed Pending Version Assignment
>
>
> It works only for the first inheritence level

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MNG-2565) plugin version aren't taken from pluginManagement in a sub-sub-modules

2007-06-16 Thread Jason van Zyl (JIRA)

[ 
http://jira.codehaus.org/browse/MNG-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99708
 ] 

Jason van Zyl commented on MNG-2565:


Is this an issue? Or can this be closed?

> plugin version aren't taken from pluginManagement in a sub-sub-modules
> --
>
> Key: MNG-2565
> URL: http://jira.codehaus.org/browse/MNG-2565
> Project: Maven 2
>  Issue Type: Bug
>  Components: Inheritance and Interpolation
>Affects Versions: 2.0.5
>Reporter: Emmanuel Venisse
>Priority: Critical
> Fix For: Reviewed Pending Version Assignment
>
>
> It works only for the first inheritence level

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MNG-2565) plugin version aren't taken from pluginManagement in a sub-sub-modules

2006-12-20 Thread Kenney Westerhof (JIRA)
[ http://jira.codehaus.org/browse/MNG-2565?page=comments#action_83055 ] 

Kenney Westerhof commented on MNG-2565:
---

I explicitly set the version for modello to 1.0-alpha-13 in the 
continuum-model/pom.xml, and it still
used 1.0-alpha-8.

I think this is a different issue alltogether: there can be no 2 different 
plugin versions used in 1 reactor.
If some other project uses an older version of a plugin, then that one is used 
on the second instance too.
That would explain why running from top level doesn't work - there's probably 
another project under top level
that uses another version of the plugin.

my 3rd point above is another issue though.

> plugin version aren't taken from pluginManagement in a sub-sub-modules
> --
>
> Key: MNG-2565
> URL: http://jira.codehaus.org/browse/MNG-2565
> Project: Maven 2
>  Issue Type: Bug
>  Components: Inheritance and Interpolation
>Affects Versions: 2.0.5
>Reporter: Emmanuel Venisse
>Priority: Critical
>
> It works only for the first inheritence level

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MNG-2565) plugin version aren't taken from pluginManagement in a sub-sub-modules

2006-12-20 Thread Kenney Westerhof (JIRA)
[ http://jira.codehaus.org/browse/MNG-2565?page=comments#action_83054 ] 

Kenney Westerhof commented on MNG-2565:
---

I didn't find that - running mvn eclipse:eclipse in maven-trunks/continuum 
works,
but running mvn eclipse:eclipse in maven-trunks (where I added a grouping pom 
with continuumhttp://repo1.maven.org/maven2/org/codehaus/modello/modello-maven-plugin/1.0-alpha-13/modello-maven-plugin-1.0-alpha-13.pom
2K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/modello/modello/1.0-alpha-13/modello-1.0-alpha-13.pom
9K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/modello/modello-maven-plugin/1.0-alpha-13/modello-maven-plugin-1.0-alpha-13.jar
13K downloaded
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Goal 'jpox-metadata-class' was specified in an execution, but not found 
in plugin org.codehaus.modello:modello-maven-plugin:1.0-alpha-8
{noformat}

Note the alpha-13 is downloaded but alpha-8 is used.

This is because the wrong parent-pom is used from the local repo. When i remove 
continuum-parent from the local repo,
and run from:

* continuum:  works.
* continuum/continuum-security: (leaf) works
* continuum/continuum-notifiers: (packaging pom, has modules) fails during 
scanning for projects; cannot find continuum-parent (for one of 
continuum/continuum-notifiers' children, but the error doesn't say which one)
* . (maven-trunks, packaging pom, modules): reactor construction works, but 
build fails on eclipse:eclipse while creating a forked lifecycle for 
generate-sources (i think, logs don't say).




> plugin version aren't taken from pluginManagement in a sub-sub-modules
> --
>
> Key: MNG-2565
> URL: http://jira.codehaus.org/browse/MNG-2565
> Project: Maven 2
>  Issue Type: Bug
>  Components: Inheritance and Interpolation
>Affects Versions: 2.0.5
>Reporter: Emmanuel Venisse
>Priority: Critical
>
> It works only for the first inheritence level

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira