Re: findbugs-plugin: Premature end of file.
Perhaps I found the problem. It seems the reports gets generated twice. I had following configuration of the site plugin: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.0.1/version inheritedtrue/inherited configuration localesde, en/locales /configuration /plugin When I change to only one locales localesde/locales everthing things works fine. Also Findbugs-Plugin 2.2/2.1/2.0.1 plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.0.1/version inheritedtrue/inherited configuration localesde/locales /configuration /plugin duality72 wrote: I'm having the same problem today. Looks like the findbugs plugin has been updated to version 2.2 and is causing the problem. Reverting to version 2.0.1 has removed the problem. -- View this message in context: http://old.nabble.com/findbugs-plugin%3A-Premature-end-of-file.-tp26421353p26438771.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
findbugs-plugin: Premature end of file.
I'm getting an error in maven-findbugs-plugin on site generation: Environment: win xp, java 1.6.0_16, maven 2.2.1, findbugs-plugin 2.2/2.1/2.0.1 [INFO] Generating FindBugs Report report. [INFO] Plugin Artifacts to be added -[org.apache.maven.reporting:maven-reporting-impl:jar:2.0:runtime, org.codehaus.plexus:plexus-utils:jar:1.5.1:runtime, commons-validator:commons-validator:jar:1.1.4:runtime, oro:oro:jar:2.0.7:runtime, doxia:doxia-core:jar:1.0-alpha-4:runtime, org.apache.maven.shared:maven-doxia-tools:jar:1.0:runtime, commons-io:commons-io:jar:1.4:runtime, org.apache.maven.doxia:doxia-decoration-model:jar:1.0-alpha-11:runtime, org.codehaus.plexus:plexus-i18n:jar:1.0-beta-7:runtime, com.google.code.findbugs:findbugs-ant:jar:1.3.9:runtime, com.google.code.findbugs:findbugs:jar:1.3.9:runtime, com.google.code.findbugs:bcel:jar:1.3.9:runtime, com.google.code.findbugs:jsr305:jar:1.3.9:runtime, com.google.code.findbugs:jFormatString:jar:1.3.9:runtime, com.google.code.findbugs:annotations:jar:1.3.9:runtime, dom4j:dom4j:jar:1.6.1:runtime, xml-apis:xml-apis:jar:1.0.b2:runtime, jaxen:jaxen:jar:1.1.1:runtime, jdom:jdom:jar:1.0:runtime, xerces:xercesImpl:jar:2.6.2:runtime, xom:xom:jar:1.0:runtime, xerces:xmlParserAPIs:jar:2.6.2:runtime, xalan:xalan:jar:2.6.0:runtime, com.ibm.icu:icu4j:jar:2.6.1:runtime, asm:asm:jar:3.1:runtime, asm:asm-analysis:jar:3.1:runtime, asm:asm-tree:jar:3.1:runtime, asm:asm-commons:jar:3.1:runtime, asm:asm-util:jar:3.1:runtime, asm:asm-xml:jar:3.1:runtime, commons-lang:commons-lang:jar:2.4:runtime, jgoodies:plastic:jar:1.2.0:runtime, org.codehaus.groovy.maven:gmaven-mojo:jar:1.0-rc-3:runtime, org.codehaus.groovy.maven.runtime:gmaven-runtime-api:jar:1.0-rc-3:runtime, org.codehaus.groovy.maven.feature:gmaven-feature-api:jar:1.0-rc-3:runtime, org.codehaus.groovy.maven.runtime:gmaven-runtime-default:jar:1.0-rc-3:runtime, org.slf4j:slf4j-api:jar:1.5.0:runtime, org.codehaus.groovy.maven.runtime:gmaven-runtime-1.5:jar:1.0-rc-3:runtime, org.codehaus.groovy.maven.feature:gmaven-feature-support:jar:1.0-rc-3:runtime, org.codehaus.groovy.maven.runtime:gmaven-runtime-support:jar:1.0-rc-3:runtime, org.codehaus.groovy.maven:gmaven-common:jar:1.0-rc-3:runtime, com.thoughtworks.qdox:qdox:jar:1.6.3:runtime, org.codehaus.groovy:groovy-all-minimal:jar:1.5.6:runtime, org.apache.ant:ant:jar:1.7.1:runtime, org.apache.ant:ant-launcher:jar:1.7.1:runtime, jline:jline:jar:0.9.94:runtime, org.codehaus.plexus:plexus-resources:jar:1.0-alpha-4:runtime, org.apache.maven.reporting:maven-reporting-api:jar:2.0.8:runtime] [INFO] AuxClasspath is
Re: M2 site-plugin: Roadmap for 2.2
Oops, sorry meant 2.1. Hope it coming soon ltheussl wrote: You really mean 2.2 or 2.1? The roadmap is here: http://jira.codehaus.org/browse/MSITE?report=com.atlassian.jira.plugin.system.project:roadmap-panel and 2.1 will include doxia 1.1.2. Timeline there is none. You might also have a look at the related Doxia release plan: http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan HTH, -Lukas Bruno Marti wrote: Which is the roadmap/timeline for release 2.2? And will Doxia 1.1.2 be included? http://jira.codehaus.org/browse/MSITE-419 http://jira.codehaus.org/browse/MSITE-419 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/M2-site-plugin%3A-Roadmap-for-2.2-tp25270282p25291423.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
M2 site-plugin: Roadmap for 2.2
Which is the roadmap/timeline for release 2.2? And will Doxia 1.1.2 be included? http://jira.codehaus.org/browse/MSITE-419 http://jira.codehaus.org/browse/MSITE-419 -- View this message in context: http://www.nabble.com/M2-site-plugin%3A-Roadmap-for-2.2-tp25270282p25270282.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[m2] release-plugin skips parent build plugins configuration
I've got a parent pom which defines several project-wide build-plugins in pluginManagement and the build section. The normal build clean install works fine (compilation of code is for version 1.5) but in release-plugin the pluginManagement and build section is completely missing in pom-release.xml or in reactor build (and compilation of code is version 1.3, causes an error on Enumeration objects). It makes no difference if generateReleasePoms of release-plugin is set or not. (windows xp, maven-2.0.9, release-plugin 2.0-beta-8) Sample: Parent.pom ... groupId.../groupId artifactIdbasis_maven_pom/artifactId version1/version packagingpom/packaging build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.0.2/version inheritedtrue/inherited configuration source1.5/source target1.5/target /configuration /plugin /plugins /pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId inheritedtrue/inherited configuration source1.5/source target1.5/target /configuration /plugin ... MyModule.pom ... parent groupId.../groupId artifactIdbasis_maven_pom/artifactId version1/version /parent groupIdch.visana.rin.ieu.web/groupId artifactIdmyModule/artifactId version1.2.2-SNAPSHOT/version packagingjar/packaging build NOTHING DEFINED HERE, ALL COMES FROM BASIS_MAVEN_POM /build ... Is this a bug or what I'm doing wrong - mvn clean install (works) - mvn release:prepare (compiler error) -- View this message in context: http://www.nabble.com/-m2--release-plugin-skips-parent-build-plugins-configuration-tp22180870p22180870.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[M2] maven-plugin-plugin does not compile with goal helpmojo
I've created a ant plugin on base of http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html. I updated the latest plugin version for usage with executions-goal = helpmojo: - maven-script-ant:2.1.0-M1 - maven-plugin-plugin:2.4.3 It compiles, but if I add: executions execution idgenerate-helpmojo/id goals goalhelpmojo/goal /goals /execution /executions I'm getting a compiler error: ..\target\generated-sources\plugin\m2-plugin-ant\build\HelpMojo.java:[1,7] identifier expected There is a wrong package defintion on line 1: package /m2-plugin-ant.build; Is ther a way to define the package-separator char '.' or want I'm doing wrong? see: http://www.nabble.com/file/p21615272/m2-plugin-ant.rar m2-plugin-ant.rar -- View this message in context: http://www.nabble.com/-M2--maven-plugin-plugin-does-not-compile-with-goal-helpmojo-tp21615272p21615272.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: M2 maven-site-plugin site.xml target attribute no more working
New issue posted in JIRA: http://jira.codehaus.org/browse/MSITE-278 http://jira.codehaus.org/browse/MSITE-278 Dennis Lundberg-2 wrote: Bruno Marti wrote: In maven 1.x xdoc site documentation there could be the following for menus (navigation.xml): menu name=myMenu item name=Maven 1.x href=http://maven.apache.org/maven-1.x/; target=_new / ... (creates a link to maven 1.x in a new window or tab) In maven 2.x site.xml this doesn't work anymore. The target attribute will be ignored. Is this a bug? Yes or rather a request for a new feature. Please post it in JIRA: http://jira.codehaus.org/browse/MSITE -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/M2-maven-site-plugin-site.xml-target-attribute-no-more-working-tp14226588s177p14248503.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
M2 maven-site-plugin site.xml target attribute no more working
In maven 1.x xdoc site documentation there could be the following for menus (navigation.xml): menu name=myMenu item name=Maven 1.x href=http://maven.apache.org/maven-1.x/; target=_new / ... (creates a link to maven 1.x in a new window or tab) In maven 2.x site.xml this doesn't work anymore. The target attribute will be ignored. Is this a bug? -- View this message in context: http://www.nabble.com/M2-maven-site-plugin-site.xml-target-attribute-no-more-working-tf4966309s177.html#a14226588 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
