Re: [PLEASE TEST] Apache Maven 3.0-RC1

2010-09-17 Thread Martin Vaněk

 Hi guys,
so far so good, but I've found something little odd.
I have reporting plugins preconfigured in pluginManagement section of 
parent pom and I've noticed that this configuration is used only when 
building parent and is not inherited into child projects and has to be 
configured explicitly again. Version of plugin is inherited. Is it 
intentional?


Martin


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: [PLEASE TEST] Apache Maven 3.0-RC1

2010-09-17 Thread Martin Vaněk

 So now I've found most likely bug in site plugins configuration

In parent pom.xml
build.pluginManagement.plugins.plugin[maven-site-plugin].reportPlugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changes-plugin/artifactId
reports
reportchanges-report/report
/reports
configuration
xmlPath${basedir}/src/changes.xml/xmlPath
/configuration
/plugin

plugin
groupIdde.smartics.maven.plugin/groupId
artifactIdmaven-buildmetadata-plugin/artifactId
reports
reportbuildmetadata-report/report
/reports
/plugin

If in child pom.xml
build.pluginManagement.plugins.plugin[maven-site-plugin].reportPlugins
plugin
groupIdde.smartics.maven.plugin/groupId
artifactIdmaven-buildmetadata-plugin/artifactId
!--
reports
reportbuildmetadata-report/report
/reports
--
/plugin

same maven-buildmetadata-plugin is without 
reportbuildmetadata-report/report mvn site will fail


[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site 
(default-site) on project komix-common: failed to
get Reports: Could not find goal changes-report in plugin 
de.smartics.maven.plugin:maven-buildmetadata-plugin:1.1.0 among 
available goals bu

ildmetadata-report, provide-buildmetadata, build-point - [Help 1]

So it tries to generate report from another plugin...

It fails in combinations:
parent in build.pluginManagement  child in build.pluginManagement
parent in build.pluginManagement  child in build.plugins
parent in build.plugins  child in build.plugins

So it only works when:
parent in build.plugins  child in build.pluginManagement because child 
build.pluginManagement is completely ignored (and it is inherited) for 
site plugin



 Hi guys,
so far so good, but I've found something little odd.
I have reporting plugins preconfigured in pluginManagement section of 
parent pom and I've noticed that this configuration is used only when 
building parent and is not inherited into child projects and has to be 
configured explicitly again. Version of plugin is inherited. Is it 
intentional?


Martin


-
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



maven-site-plugin 2.1

2010-03-17 Thread Martin Vaněk

Hi guys,
I've upgraded maven-site-plugin from 2.0.1 to 2.1 and all generated site 
pages suddenly have empty (left) menu. I'm using maven-2.2.1 on JDK 1.6
Menu appears again after I add site.xml, but it is quite uncomfortable 
to copy same site.xml into every module in all projects because it is 
not even inherited from parent project?!?

So this behaviour is normal or I'm missing something or something is broken?

Martin Vanek

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org