AW: Project description
Hi Jeff, this is at the moment not solved yet. The Description tag in pom has to consist of one single line (no linebreaks or paragraphs between it). I did not find a jira issue yet, may be we have to set one up. Because I had the same problem, I just made the project description by myself using Xdoc Format. Because I named it index.xml the project 'About' link was than linked to this page. Hope that helps, Arne -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Ivo Limmen Gesendet: Mittwoch, 26. Juli 2006 10:29 An: Maven Users List Betreff: Re: Project description I recently discovered that the description is also added to the manifest within the jar that is produced. When the description spans more than one line my build fails i.e. the jar is not valid. So to answer your question: I don't think it is possible. On 7/26/06, Jeff Mutonho [EMAIL PROTECTED] wrote: My project description is a bit long and would like to introduce paragraphs and sub-headings in it.Is it possible to do this? -- Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: multi-module project site: link to module sites
Hi Valerio, sorry for the late reply. Just the case you have something like: +Project | +-Module A | +-Module B | +-Module C In your parent pom you have set up the following parameters in order to stage your site completely. 1. the Distribution Management Tag distributionManagement site idmy-site/id nameMy Website/name urlscpexe://www.myPath.toMyProject//url /site /distributionManagement This setting will be used to place the full website into the directory c:\fullsite\www.myPath.toMyProject 2. The Module Tag modules moduleA/module moduleB/module moduleC/module /modules In order to tell maven which submodules are present. The last thing is to use the full pathname and not a relative one for the stagingDirectory Parameter: e.g. mvn site:stage -DstagingDirectory=C:\fullsite Maven itself will find out which subprojects are present and stage the content of the site to the specified directory. If only the site of the parent projects is available, than you did not specify the modules section in the pom. Please refer to the following pages for details: http://maven.apache.org/plugins/maven-site-plugin/howto.html and http://maven.apache.org/guides/mini/guide-site.html Within my project everything works fine. Hope this helps, Arne -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Valerio Schiavoni Gesendet: Samstag, 22. Juli 2006 15:56 An: Maven Users List Betreff: Re: multi-module project site: link to module sites Hello Arne, On 7/21/06, Arne Sutor [EMAIL PROTECTED] wrote: Maven first creates in each module a directory staging and than copies everything in the directory c:\fullsite. i launched mvn clean site:stage -DstagingDirectory=fullsite/ the content of fullsite is only about the parent project website. that is, the copy of module websites has not being performed... did you specify a particular revision for the maven-site-plugin ? thanks, valerio -- http://valerioschiavoni.blogspot.com http://jroller.com/page/vschiavoni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] maven-changelog-plugin - Has someone found a repository for it?
Hi all, I tried to get the change log reporting plug-in up and running. Unfortunately there is during the site goal I get an error saying, that the plugin could not be found or not a valid version is specified. My pom looks in excerps like this: pluginRepositories pluginRepository idibiblio/id nameibiblio/name urlhttp://www.ibiblio.org/maven2/url releasesenabledtrue/enabled/releases snapshotsenabledtrue/enabled/snapshots /pluginRepository /pluginRepositories reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId reportSets reportSet iddual-report/id configuration typerange/type range30/range /configuration reports reportchangelog/report reportdev-activity/report /reports /reportSet /reportSets /plugin /plugins /reporting After I browsed the ibibleo library I found out that the specified directory org/apache/maven/plugins/maven-changelog-plugin does not exists. Did anyone get the changelog report working with the correct repository settings? Thanks for an answer, Arne
[m2]: Discovering problems with the maven-site and the maven-javadoc plugins - No staging of javadocs
Hi all, as newbie I am just playing around with maven2 in a multi-project environment. While setting up the documentation for our project I discovered that maven when executing the site goal generates everything fine including the javadoc. But as soon as I use the stage goal, maven seems not to stage the generated javadocs in the directory target/statging/[..]/apidocs. How can I set up my pom, that the javadoc plugin during staging generates the javadocs in the staging directory? Thankful for everyone who can answer that question, Arne
[m2] Another findbugs plugin problem - site goal resides into a nullpointer execption
Hi all, I set up my project so far and I wanted to include the findbugs in the reporting section. Reading the Mailing list archives I discovered several hints. Executing the goal findbugs:findbugs does not result into any errors. But as soon as I start the mvn site:site goal, I will get the following stack trace. Does anyone have a solution for this? Thanks in advanced, Arne Here is the stack trace: [INFO] Velocimacro : initialization complete. [INFO] Velocity successfully started. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager. java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPl uginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyReportPlugin(DefaultPlugi nManager.java:487) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin(Defau ltLifecycleExecutor.java:1292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecy cleExecutor.java:657) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecy cleExecutor.java:637) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife cycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec ycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail ures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa ultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle Executor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
AW: [m2] Another findbugs plugin problem - site goal resides into a nullpointer execption
Hi Denis, Thanks for your answer. Here is the out commented line of the reporting section: reporting plugins !--plugin groupIdmaven-plugins/groupId artifactIdmaven-findbugs-plugin/artifactId version1.0-SNAPSHOT/version configuration outputDirectorytarget/site/outputDirectory thresholdLow/threshold /configuration /plugin-- /plugins /reporting With regards, Arne -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von dcabasson Gesendet: Freitag, 21. Juli 2006 10:24 An: users@maven.apache.org Betreff: Re: [m2] Another findbugs plugin problem - site goal resides into a nullpointer execption Care to show the reporting section fo your pom? Most of the time, these NPE comes from mispelled plugin names/groups (which can explain that the plugin is working fine when launched from command line). Denis. -- View this message in context: http://www.nabble.com/-m2--Another-findbugs-plugin-problem---site-goal-resid es-into-a-nullpointer-execption-tf1978903.html#a5430086 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Newbie: need to package a jar
Hi Denis, The mailing lists are searchable, see the link below: http://www.nabble.com/Maven---Users-f178.html The search area can be found on the top right. Have fun, Arne -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Denis McCarthy Gesendet: Freitag, 21. Juli 2006 11:33 An: users@maven.apache.org Betreff: Newbie: need to package a jar Hi, I'm sure this question has been asked a thousand times before but I can't see a clear answer on the maven site or through google (Unfortunately the mailing list archives aren't searchable either). I'm converting a project to use maven as the build tool and I've set up most of my dependencies (the ones that have jars on ibiblio). However, my project depends on an oracle jar called sdoapi.jar. How do I get maven to put this jar in the local repository? Thanks Denis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: multi-module project site: link to module sites
Hi Valerio, this is due to the fact that maven generates the pages in the directory parent\foo\target\site parent\bar\target\site parent\target\site You have to view each module separately. In order to test the full website try: mvn site:stage -DstagingDirectory=C:\fullsite Maven first creates in each module a directory staging and than copies everything in the directory c:\fullsite. You will discover that all files are placed correctly. In order to get more detailed information try this: http://maven.apache.org/plugins/maven-site-plugin/howto.html Have fun, Arne -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Valerio Schiavoni Gesendet: Freitag, 21. Juli 2006 15:08 An: Maven Users List Betreff: multi-module project site: link to module sites hello, i have a multi-module site. the parent project site.xml declares something like: project body links item name=Maven 2 href=http://maven.apache.org/maven2// /links menu name=My Project item name=Introduction href=index.html/ item name=Download href=download.html/ /menu menu ref=modules / /body /project i have 2 modules, named Foo and Bar... The generated site correctly shows links to them, but the links are not correct. they look like: li class=none a href=../../maven-site/foo/index.htmlFoo/a /li li class=none a href=../../maven-site/bar/index.htmlBar/a /li but they are not there. why is maven-site used ? if i look into parent/foo/target/site/index.html i can see the index for Foo (same for other submodules). thanks, valerio -- http://valerioschiavoni.blogspot.com http://jroller.com/page/vschiavoni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
m2: Discovering problems with the maven-site and the maven-javadoc plugins - No staging of javadocs
Hi all, as newbie I am just playing around with maven2 in a multi-project environment. While setting up the documentation for our project I discovered that maven when executing the site goal generates everything fine including the javadoc. But as soon as I use the stage goal, maven seems not to stage the generated javadocs in the specified directory. Does anyone discovered that problem as well or is this just a settings thing. Browsing the mailing list archives did not worked out well. Thankful for everyone who can answer that question, Arne
[m2] Another findbugs plugin problem - site goal resides into a nullpointer execption
Hi all, I set up my project do far and I wanted to include the findbugs in the reporting section. Reading the Mailing list archives I discovered several hints. Executing the coals findbugs:findbugs does not result into any errors. But as soon as I start the mvn site goal, I will get the following stack trace. Does anyone have a solution for this? With in advance, Arne Here is the staktrace: [INFO] Velocimacro : initialization complete. [INFO] Velocity successfully started. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager. java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPl uginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyReportPlugin(DefaultPlugi nManager.java:487) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin(Defau ltLifecycleExecutor.java:1292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecy cleExecutor.java:657) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecy cleExecutor.java:637) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife cycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec ycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail ures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa ultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle Executor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
