[jira] Commented: (MPLUGIN-114) PluginXdocGenerator NullPointerException
[ http://jira.codehaus.org/browse/MPLUGIN-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135225#action_135225 ] Benjamin Bentmann commented on MPLUGIN-114: --- bq. Looking at the code above there is a bug in it since there is not a null check before working on the iterator. Just because a line triggers a NPE does not mean this same line is faulty. The question I would like to investigate on is whether the plugin descriptor is properly crafted, i.e. whether the null list is a valid return value. bq. It seem this was brought up some time ago in MNG-2087 There seem to more than one occasion where people reported NPEs because collections were null rather than empty. As I don't currently see a rationale to distinguish a null collection from an empty collection, I believe it's time to fix the descriptors themselves rather to add null checks in every piece of code that processes them. > PluginXdocGenerator NullPointerException > > > Key: MPLUGIN-114 > URL: http://jira.codehaus.org/browse/MPLUGIN-114 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: API >Affects Versions: 2.3 >Reporter: Garvin LeClaire > Attachments: pom.xml > > > When creating a site I get the following stack trace: > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.tools.plugin.generator.PluginXdocGenerator.execute(PluginXdocGenerator.java:95) > at > org.apache.maven.plugin.plugin.PluginReport.generatePluginDocumentation(PluginReport.java:224) > at > org.apache.maven.plugin.plugin.PluginReport.executeReport(PluginReport.java:178) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > 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) > [INFO] > > [INFO] Total time: 33 seconds > [INFO] Finished at: Wed May 14 23:36:51 EDT 2008 > [INFO] Final Memory: 41M/63M > I have tried and get the same results with version of the site plg-in back to > 2.0-beta-3 > Any suggestions?? -- 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] Updated: (MPIR-97) Provide a way of hiding developer/contributer email addresses
[ http://jira.codehaus.org/browse/MPIR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPIR-97: Component/s: project-team > Provide a way of hiding developer/contributer email addresses > - > > Key: MPIR-97 > URL: http://jira.codehaus.org/browse/MPIR-97 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: New Feature > Components: project-team >Affects Versions: 2.0.1 >Reporter: Kristian Andersen >Priority: Minor > Attachments: TeamListReport.java.patch > > > Even in these GMail times it would be nice to be able to hide email addresses > using services such as reCAPTCHA Mailhide [http://mailhide.recaptcha.net/] > One way of achieving this is to tell the team-list report generator to treat > the contents of as HTML, making it possible to include links etc. > Example: > > ... > > ... > > The attached patch does this using a configuration parameter. -- 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] Updated: (MPIR-80) Add Java requirements to the Dependency Report
[ http://jira.codehaus.org/browse/MPIR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPIR-80: Component/s: summary dependencies > Add Java requirements to the Dependency Report > -- > > Key: MPIR-80 > URL: http://jira.codehaus.org/browse/MPIR-80 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: New Feature > Components: dependencies, summary >Affects Versions: 2.0.1 >Reporter: Niall Pemberton > Fix For: 2.1 > > Attachments: maven-projectinfo-dependency-java-v2.patch, > maven-projectinfo-dependency-java-v3.patch, > maven-projectinfo-dependency-java.patch, maven-projectinfo-summary-java.patch > > > It would be nice to add a section to the dependency report showing the java > version requirements. > Attaching a patch which discovers the java version and compiler options from > the java-compiler-plugin configuration and outputs a "Java Version" section. > Has an option to configure whether or not this section is shown (default to > false). -- 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] Updated: (MPIR-85) Refactoring of dependency and dependency management report
[ http://jira.codehaus.org/browse/MPIR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPIR-85: Component/s: dependency-management dependencies > Refactoring of dependency and dependency management report > -- > > Key: MPIR-85 > URL: http://jira.codehaus.org/browse/MPIR-85 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies, dependency-management >Affects Versions: 2.1 >Reporter: Nick Stolwijk > Attachments: comparators.patch, refactor.patch, refactor.patch > > > I've tried to refactor the code from MPIR-83 a bit, because it used a lot of > copied code. > Important improvements: > - Created a AbstractProjectInfoRenderer and AbstractDependencyRenderer. > If this patch is accepted, I want to write all the renderers out of the > inforeports in separate classes, with more code sharing. This is a start of > that. > - I changed the unit tests, because the expected and actual were reversed. > This is the case in many of the info report unit tests. > Please tell me what you think of it. I know it is only a start. -- 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] Created: (MAVENUPLOAD-2064) Host key changed for "cedarsoft.com" and "cedarsoft.eu"
Host key changed for "cedarsoft.com" and "cedarsoft.eu" --- Key: MAVENUPLOAD-2064 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2064 Project: maven-upload-requests Issue Type: Bug Reporter: Johannes Schneider I had to change the keys (due to the Debian bug) for my server. Therefore the synchronization failed for group com.cedarsoft and eu.cedarsoft. -- 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] Updated: (MPIR-94) Change optional label in dependencies site
[ http://jira.codehaus.org/browse/MPIR-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPIR-94: Component/s: dependencies > Change optional label in dependencies site > -- > > Key: MPIR-94 > URL: http://jira.codehaus.org/browse/MPIR-94 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies >Affects Versions: 2.0.1 >Reporter: Michael Osipov >Priority: Minor > > If you check the project dependencies page, the table says for an aoptional > dependency "(optional)". This is actually not really intuitive. A "yes" would > be much more help full or even more, let the user configure a term for both > states. -- 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] Updated: (MPIR-95) Better handling of HTML license documents
[ http://jira.codehaus.org/browse/MPIR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPIR-95: Component/s: license > Better handling of HTML license documents > - > > Key: MPIR-95 > URL: http://jira.codehaus.org/browse/MPIR-95 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: license >Affects Versions: 2.1 >Reporter: Martin von Gagern >Priority: Minor > Attachments: pom.xml > > > I've got a document here specifying > http://www.opensource.org/licenses/mit-license.php as its license. This is > handles rather poorly by the generated license document, as the framework > around the license text gets in the way and the heading levels of the license > text don't fit. I can imagine several possible solutions to improve this > situations: > 1. Specify local file in pom. This makes it difficult to automatically handle > licensing automatically, as only well known public URLs can be used to > identify well known licenses, which won't work for local file names or > private web sites. > 2. Provide a way to specify appropriate local files for licenses without > touching the url in the pom. This could take the form of some map parameter > that associates license names with license documents. > 3. Provide a way to simply not include any license text, only the link. This > is the quickest solution. > 4. Embed the license text as an iframe with an external source, so you only > link and copy nothing. > 5. Parse HTML and allow XPath selectors or something similar to extract the > license content. > When you do some better HTML parsing one day (maybe using > org.htmlparser:htmlparser?), you might wish to adjust headline levels as > well. Find the highest level headline that occurs in the extracted fragment, > calculate an offset that places this one level below the license name > headline printed by the plugin, and apply this offset to every headline in > the fragment. > If you decide for one of the solutions 2-4, I guess I could hack a quick > patch to implement this. 5 is more work, of course. -- 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] Updated: (MPIR-88) Wrong homepage link in project-summary.html when processing staging
[ http://jira.codehaus.org/browse/MPIR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPIR-88: Component/s: summary > Wrong homepage link in project-summary.html when processing staging > --- > > Key: MPIR-88 > URL: http://jira.codehaus.org/browse/MPIR-88 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: summary >Affects Versions: 2.1 >Reporter: Vincent Siveton > Attachments: maven-plugin-plugin-2.4.PNG > > > See the screenshot > http://maven.apache.org/plugin-tools/maven-plugin-tools-api/project-summary.html > http://maven.apache.org/plugin-tools/maven-plugin-tools-api-2.4/project-summary.html -- 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] Updated: (MPIR-76) Dependencies report is incorrect
[
http://jira.codehaus.org/browse/MPIR-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MPIR-76:
Component/s: dependencies
> Dependencies report is incorrect
>
>
> Key: MPIR-76
> URL: http://jira.codehaus.org/browse/MPIR-76
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.0.1
> Environment: Maven 2.0.7, SUN JVM 1.5.0_12, Windows XP
>Reporter: Duncan Doyle
>
> When generating a site from the following POM, the Dependencies report is
> incorrect.
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> test
> Test
> jar
> 0.0.1-SNAPSHOT
> Test
> Test Dependency Graphs
>
>
> commons-logging
> commons-logging
> 1.1
> compile
>
>
>
> javax.servlet
> servlet-api
> 2.4
> compile
>
>
>
>
> TestDependencyGraph
> file://${site.distribution.directory}/TestDependencyGraph
>
>
>
> {code}
> The Dependencies report of this project's generated site doesn't show the
> javax.servlet:servlet-api 2.4 as a compile dependency. Instead it shows it as
> a transitivie dependency. My guess is that it finds the servlet-api 2.3
> transitive dependency of commons-logging. However, the strange thing is that
> it does show the 2.4 version number in the report.
> The Dependency Graph has the same error, it shows the servlet-api as a
> transitive dependency of commons-logging instead of a compile dependency of
> my own project.
--
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] Updated: (MPIR-71) Include transitive dependencies in convergence report
[ http://jira.codehaus.org/browse/MPIR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPIR-71: Component/s: dependency-convergence > Include transitive dependencies in convergence report > - > > Key: MPIR-71 > URL: http://jira.codehaus.org/browse/MPIR-71 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependency-convergence >Reporter: Dennis Lundberg > Fix For: 2.x > > -- 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] Updated: (MPIR-86) Customizable Team list report
[ http://jira.codehaus.org/browse/MPIR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPIR-86: Component/s: project-team > Customizable Team list report > - > > Key: MPIR-86 > URL: http://jira.codehaus.org/browse/MPIR-86 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: project-team >Reporter: Roberto Lo Giacco > > It would be nice and useful to allow for Team list report customization at > least in terms of which columns to display and which to hide. > In my experience the URL, Organization,Organization URL, Time Zone, Actual > Time (GMT) and Properties columns are pratically unused and eats space. > In an optimal view it would be practical to include only columns for which > there is at least a value in one of the rows, automatically excluding the > columns never valorized. > If you can redirect me and give some hints I can contribute myself the > correction. -- 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] Updated: (MPIR-78) Unable to exclude scm anonymous access info
[ http://jira.codehaus.org/browse/MPIR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPIR-78: Component/s: scm > Unable to exclude scm anonymous access info > --- > > Key: MPIR-78 > URL: http://jira.codehaus.org/browse/MPIR-78 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: scm >Affects Versions: 2.0.1 > Environment: WinXP SP2 fully patched, jdk 1.6.0_03, Maven 2.0.8, > Continuum 1.1 >Reporter: creyle >Priority: Minor > > Currently there's no way to exclude the information, about anonymous access > to the source repository, from the scm report. > In the doc [1] it says, the anonymousConnection defaults to > project.scm.connection in POM, but explicitly setting a blank > configuration element just has no effect, as discussed > in the maven user list [2], while setting it to a invalid value e.g. > foo still has no effect with > 2.0.1, but will cause "horrible" problems with 2.1-SNAPSHOT. > [1] > http://maven.apache.org/plugins/maven-project-info-reports-plugin/scm-mojo.html#anonymousConnection > [2] http://www.nabble.com/forum/ViewPost.jtp?post=14413537&framed=y&skin=177 -- 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] Created: (MPIR-99) Strange warnings when generating Plugin Management report
Strange warnings when generating Plugin Management report
-
Key: MPIR-99
URL: http://jira.codehaus.org/browse/MPIR-99
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: plugin-management
Affects Versions: 2.1
Reporter: Dennis Lundberg
When running 'mvn site' on MPIR itself I get the following warnings during the
build:
{noformat}
[INFO] Generating "Plugin Management" report.
[WARNING] Attempting to build MavenProject instance for Artifact
(org.apache.maven.plugins:maven-clean-plugin:2.2) of type: maven-plugin;
constructing POM artifact instead.
[WARNING] Attempting to build MavenProject instance for Artifact
(org.apache.maven.plugins:maven-deploy-plugin:2.3) of type: maven-plugin;
constructing POM artifact instead.
[WARNING] Attempting to build MavenProject instance for Artifact
(org.apache.maven.plugins:maven-gpg-plugin:1.0-alpha-4) of type: maven-plugin;
constructing POM artifact instead.
[WARNING] Attempting to build MavenProject instance for Artifact
(org.apache.maven.plugins:maven-install-plugin:2.2) of type: maven-plugin;
constructing POM artifact instead.
[WARNING] Attempting to build MavenProject instance for Artifact
(org.apache.maven.plugins:maven-jar-plugin:2.2) of type: maven-plugin;
constructing POM artifact instead.
[WARNING] Attempting to build MavenProject instance for Artifact
(org.apache.maven.plugins:maven-javadoc-plugin:2.4) of type: maven-plugin;
constructing POM artifact instead.
[WARNING] Attempting to build MavenProject instance for Artifact
(org.apache.maven.plugins:maven-release-plugin:2.0-beta-7) of type:
maven-plugin; constructing POM artifact instead.
[WARNING] Attempting to build MavenProject instance for Artifact
(org.apache.maven.plugins:maven-source-plugin:2.0.4) of type: maven-plugin;
constructing POM artifact instead.
[WARNING] Attempting to build MavenProject instance for Artifact
(org.apache.maven.plugins:maven-surefire-plugin:2.4.2) of type: maven-plugin;
constructing POM artifact instead.
{noformat}
If there is nothing wrong with the POM or its plugins, there should not be any
warnings issued. On the other hand, if there is something wrong, then a hint to
how the problem can be solved should be included in the warning.
--
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] Closed: (MPLUGIN-113) Improve generated help mojo to control output (indent, width)
[ http://jira.codehaus.org/browse/MPLUGIN-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MPLUGIN-113. - Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.4.2 Done in [r657332|http://svn.apache.org/viewvc?view=rev&revision=657332]. > Improve generated help mojo to control output (indent, width) > - > > Key: MPLUGIN-113 > URL: http://jira.codehaus.org/browse/MPLUGIN-113 > Project: Maven 2.x Plugin Tools > Issue Type: Improvement > Components: Java Plugins >Affects Versions: 2.4.1 >Reporter: Vincent Siveton >Assignee: Benjamin Bentmann > Fix For: 2.4.2 > > > Related thread: > http://markmail.org/message/meccvmjlqci4wsim -- 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: (MJAVADOC-183) Aggregate javadoc does not process the src/main/javadoc directories
[
http://jira.codehaus.org/browse/MJAVADOC-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135235#action_135235
]
Heinrich Nirschl commented on MJAVADOC-183:
---
See also MJAVADOC-118. It has worked in 2.3, and is now broken again in 2.4.
> Aggregate javadoc does not process the src/main/javadoc directories
> ---
>
> Key: MJAVADOC-183
> URL: http://jira.codehaus.org/browse/MJAVADOC-183
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: Windows XP, Maven 2.0.9
>Reporter: Peter Hayes
>Priority: Critical
> Attachments: javadoc-aggregate.zip
>
>
> When running the javadoc plugin in aggregate mode, the plugin ignores the
> src/main/javadoc directory of the child module.
> *options file when running in non-aggregate*
> {quote}
> -classpath 'C:/dev/maven/bugs/javadoc-aggregate/child/target/classes'
> -encoding
> 'ISO-8859-1'
> -protected
> -sourcepath
> 'C:/dev/maven/bugs/javadoc-aggregate/child/src/main/java;C:/dev/maven/bugs/javadoc-aggregate/child/src/main/javadoc'
> -author
> -bottom
> 'Copyright © 2008. All Rights Reserved.'
> -charset
> 'ISO-8859-1'
> -d
> 'C:/dev/maven/bugs/javadoc-aggregate/child/target/site/apidocs'
> -doctitle
> 'child 1.0-SNAPSHOT API'
> -use
> -version
> -windowtitle
> 'child 1.0-SNAPSHOT API'
> {quote}
> *options file when running in aggregate*
> {quote}
> -classpath
> 'C:/dev/maven/bugs/javadoc-aggregate/target/classes;C:/dev/maven/bugs/javadoc-aggregate/child/target/classes'
> -encoding
> 'ISO-8859-1'
> -protected
> -sourcepath
> 'C:/dev/maven/bugs/javadoc-aggregate/child/src/main/java'
> -author
> -bottom
> 'Copyright © 2008. All Rights Reserved.'
> -charset
> 'ISO-8859-1'
> -d
> 'C:/dev/maven/bugs/javadoc-aggregate/target/site/apidocs'
> -doctitle
> 'aggregate javadoc parent 1.0-SNAPSHOT API'
> -use
> -version
> -windowtitle
> 'aggregate javadoc parent 1.0-SNAPSHOT API'
> {quote}
--
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] Updated: (MPIR-99) Strange warnings when generating Plugin Management report
[
http://jira.codehaus.org/browse/MPIR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated MPIR-99:
Attachment: MPIR-99.patch
Using createParentArtifact instead of createPluginArtifact
> Strange warnings when generating Plugin Management report
> -
>
> Key: MPIR-99
> URL: http://jira.codehaus.org/browse/MPIR-99
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: plugin-management
>Affects Versions: 2.1
>Reporter: Dennis Lundberg
> Attachments: MPIR-99.patch
>
>
> When running 'mvn site' on MPIR itself I get the following warnings during
> the build:
> {noformat}
> [INFO] Generating "Plugin Management" report.
> [WARNING] Attempting to build MavenProject instance for Artifact
> (org.apache.maven.plugins:maven-clean-plugin:2.2) of type: maven-plugin;
> constructing POM artifact instead.
> [WARNING] Attempting to build MavenProject instance for Artifact
> (org.apache.maven.plugins:maven-deploy-plugin:2.3) of type: maven-plugin;
> constructing POM artifact instead.
> [WARNING] Attempting to build MavenProject instance for Artifact
> (org.apache.maven.plugins:maven-gpg-plugin:1.0-alpha-4) of type:
> maven-plugin; constructing POM artifact instead.
> [WARNING] Attempting to build MavenProject instance for Artifact
> (org.apache.maven.plugins:maven-install-plugin:2.2) of type: maven-plugin;
> constructing POM artifact instead.
> [WARNING] Attempting to build MavenProject instance for Artifact
> (org.apache.maven.plugins:maven-jar-plugin:2.2) of type: maven-plugin;
> constructing POM artifact instead.
> [WARNING] Attempting to build MavenProject instance for Artifact
> (org.apache.maven.plugins:maven-javadoc-plugin:2.4) of type: maven-plugin;
> constructing POM artifact instead.
> [WARNING] Attempting to build MavenProject instance for Artifact
> (org.apache.maven.plugins:maven-release-plugin:2.0-beta-7) of type:
> maven-plugin; constructing POM artifact instead.
> [WARNING] Attempting to build MavenProject instance for Artifact
> (org.apache.maven.plugins:maven-source-plugin:2.0.4) of type: maven-plugin;
> constructing POM artifact instead.
> [WARNING] Attempting to build MavenProject instance for Artifact
> (org.apache.maven.plugins:maven-surefire-plugin:2.4.2) of type: maven-plugin;
> constructing POM artifact instead.
> {noformat}
> If there is nothing wrong with the POM or its plugins, there should not be
> any warnings issued. On the other hand, if there is something wrong, then a
> hint to how the problem can be solved should be included in the warning.
--
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: (MJAVADOC-183) Aggregate javadoc does not process the src/main/javadoc directories
[
http://jira.codehaus.org/browse/MJAVADOC-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135238#action_135238
]
Vincent Siveton commented on MJAVADOC-183:
--
fixed in r657353, snapshot 2.5 deployed
> Aggregate javadoc does not process the src/main/javadoc directories
> ---
>
> Key: MJAVADOC-183
> URL: http://jira.codehaus.org/browse/MJAVADOC-183
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: Windows XP, Maven 2.0.9
>Reporter: Peter Hayes
>Priority: Critical
> Attachments: javadoc-aggregate.zip
>
>
> When running the javadoc plugin in aggregate mode, the plugin ignores the
> src/main/javadoc directory of the child module.
> *options file when running in non-aggregate*
> {quote}
> -classpath 'C:/dev/maven/bugs/javadoc-aggregate/child/target/classes'
> -encoding
> 'ISO-8859-1'
> -protected
> -sourcepath
> 'C:/dev/maven/bugs/javadoc-aggregate/child/src/main/java;C:/dev/maven/bugs/javadoc-aggregate/child/src/main/javadoc'
> -author
> -bottom
> 'Copyright © 2008. All Rights Reserved.'
> -charset
> 'ISO-8859-1'
> -d
> 'C:/dev/maven/bugs/javadoc-aggregate/child/target/site/apidocs'
> -doctitle
> 'child 1.0-SNAPSHOT API'
> -use
> -version
> -windowtitle
> 'child 1.0-SNAPSHOT API'
> {quote}
> *options file when running in aggregate*
> {quote}
> -classpath
> 'C:/dev/maven/bugs/javadoc-aggregate/target/classes;C:/dev/maven/bugs/javadoc-aggregate/child/target/classes'
> -encoding
> 'ISO-8859-1'
> -protected
> -sourcepath
> 'C:/dev/maven/bugs/javadoc-aggregate/child/src/main/java'
> -author
> -bottom
> 'Copyright © 2008. All Rights Reserved.'
> -charset
> 'ISO-8859-1'
> -d
> 'C:/dev/maven/bugs/javadoc-aggregate/target/site/apidocs'
> -doctitle
> 'aggregate javadoc parent 1.0-SNAPSHOT API'
> -use
> -version
> -windowtitle
> 'aggregate javadoc parent 1.0-SNAPSHOT API'
> {quote}
--
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] Updated: (MJAVADOC-188) -top command line argument is passed even when java version is <1.6, generating a warning
[
http://jira.codehaus.org/browse/MJAVADOC-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated MJAVADOC-188:
-
Description:
The -top argument is being passed when we're using a version smaller than 1.6.
Then the following warning is generated:
{noformat}
"[WARNING] -top option is not supported on Java version < 1.6. Ignore this
option."
{noformat}
This warning shouldn't be thrown since we're not setting the -top parameter in
the POM, so there's no way to ignore it.
On AbstractJavadocMojo.java, line 1492, the following method is called:
{noformat}
addArgIfNotEmpty( arguments, "-top", JavadocUtil.quotedArgument( top ), false,
false, SINCE_JAVADOC_1_6 );
{noformat}
however, this method checks the version first, and then checks if the argument
is null, like the following:
{noformat}
if ( isJavaDocVersionAtLeast( requiredJavaVersion ) )
{
addArgIfNotEmpty( arguments, key, value, repeatKey, splitValue );
}
else
{
if ( getLog().isWarnEnabled() )
{
getLog().warn( key + " option is not supported on Java version
< " + requiredJavaVersion
+ ". Ignore this option." );
}
}
}}
{noformat}
Specifically for this command line argument, the method should check the
version before calling addArgIfNotEmpty, thus removing the warning if we're not
explicitly passing the argument in a jdk < 1.6
was:
The -top argument is being passed when we're using a version smaller than 1.6.
Then the following warning is generated:
"[WARNING] -top option is not supported on Java version < 1.6. Ignore this
option."
This warning shouldn't be thrown since we're not setting the -top parameter in
the POM, so there's no way to ignore it.
On AbstractJavadocMojo.java, line 1492, the following method is called:
addArgIfNotEmpty( arguments, "-top", JavadocUtil.quotedArgument( top ), false,
false, SINCE_JAVADOC_1_6 );
however, this method checks the version first, and then checks if the argument
is null, like the following:
if ( isJavaDocVersionAtLeast( requiredJavaVersion ) )
{
addArgIfNotEmpty( arguments, key, value, repeatKey, splitValue );
}
else
{
if ( getLog().isWarnEnabled() )
{
getLog().warn( key + " option is not supported on Java version
< " + requiredJavaVersion
+ ". Ignore this option." );
}
}
}}
Specifically for this command line argument, the method should check the
version before calling addArgIfNotEmpty, thus removing the warning if we're not
explicitly passing the argument in a jdk < 1.6
> -top command line argument is passed even when java version is <1.6,
> generating a warning
> -
>
> Key: MJAVADOC-188
> URL: http://jira.codehaus.org/browse/MJAVADOC-188
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Environment: jdk 1.5
>Reporter: Cleber Zarate
>Priority: Trivial
>
> The -top argument is being passed when we're using a version smaller than 1.6.
> Then the following warning is generated:
> {noformat}
> "[WARNING] -top option is not supported on Java version < 1.6. Ignore this
> option."
> {noformat}
> This warning shouldn't be thrown since we're not setting the -top parameter
> in the POM, so there's no way to ignore it.
> On AbstractJavadocMojo.java, line 1492, the following method is called:
> {noformat}
> addArgIfNotEmpty( arguments, "-top", JavadocUtil.quotedArgument( top ),
> false, false, SINCE_JAVADOC_1_6 );
> {noformat}
> however, this method checks the version first, and then checks if the
> argument is null, like the following:
> {noformat}
> if ( isJavaDocVersionAtLeast( requiredJavaVersion ) )
> {
> addArgIfNotEmpty( arguments, key, value, repeatKey, splitValue );
> }
> else
> {
> if ( getLog().isWarnEnabled() )
> {
> getLog().warn( key + " option is not supported on Java
> version < " + requiredJavaVersion
>+ ". Ignore this option." );
> }
> }
> }}
> {noformat}
> Specifically for this command line argument, the method should check the
> version before calling addArgIfNotEmpty, thus removing the warning if we're
> not explicitly passing the argument in a jdk < 1.6
--
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] Closed: (MJAVADOC-183) Aggregate javadoc does not process the src/main/javadoc directories
[
http://jira.codehaus.org/browse/MJAVADOC-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-183.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.5
Forgot to fix it ;)
> Aggregate javadoc does not process the src/main/javadoc directories
> ---
>
> Key: MJAVADOC-183
> URL: http://jira.codehaus.org/browse/MJAVADOC-183
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: Windows XP, Maven 2.0.9
>Reporter: Peter Hayes
>Assignee: Vincent Siveton
>Priority: Critical
> Fix For: 2.5
>
> Attachments: javadoc-aggregate.zip
>
>
> When running the javadoc plugin in aggregate mode, the plugin ignores the
> src/main/javadoc directory of the child module.
> *options file when running in non-aggregate*
> {quote}
> -classpath 'C:/dev/maven/bugs/javadoc-aggregate/child/target/classes'
> -encoding
> 'ISO-8859-1'
> -protected
> -sourcepath
> 'C:/dev/maven/bugs/javadoc-aggregate/child/src/main/java;C:/dev/maven/bugs/javadoc-aggregate/child/src/main/javadoc'
> -author
> -bottom
> 'Copyright © 2008. All Rights Reserved.'
> -charset
> 'ISO-8859-1'
> -d
> 'C:/dev/maven/bugs/javadoc-aggregate/child/target/site/apidocs'
> -doctitle
> 'child 1.0-SNAPSHOT API'
> -use
> -version
> -windowtitle
> 'child 1.0-SNAPSHOT API'
> {quote}
> *options file when running in aggregate*
> {quote}
> -classpath
> 'C:/dev/maven/bugs/javadoc-aggregate/target/classes;C:/dev/maven/bugs/javadoc-aggregate/child/target/classes'
> -encoding
> 'ISO-8859-1'
> -protected
> -sourcepath
> 'C:/dev/maven/bugs/javadoc-aggregate/child/src/main/java'
> -author
> -bottom
> 'Copyright © 2008. All Rights Reserved.'
> -charset
> 'ISO-8859-1'
> -d
> 'C:/dev/maven/bugs/javadoc-aggregate/target/site/apidocs'
> -doctitle
> 'aggregate javadoc parent 1.0-SNAPSHOT API'
> -use
> -version
> -windowtitle
> 'aggregate javadoc parent 1.0-SNAPSHOT API'
> {quote}
--
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] Updated: (MJAVADOC-188) -top command line argument is passed even when java version is <1.6, generating a warning
[
http://jira.codehaus.org/browse/MJAVADOC-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated MJAVADOC-188:
-
Affects Version/s: 2.4
> -top command line argument is passed even when java version is <1.6,
> generating a warning
> -
>
> Key: MJAVADOC-188
> URL: http://jira.codehaus.org/browse/MJAVADOC-188
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: jdk 1.5
>Reporter: Cleber Zarate
>Priority: Trivial
>
> The -top argument is being passed when we're using a version smaller than 1.6.
> Then the following warning is generated:
> {noformat}
> "[WARNING] -top option is not supported on Java version < 1.6. Ignore this
> option."
> {noformat}
> This warning shouldn't be thrown since we're not setting the -top parameter
> in the POM, so there's no way to ignore it.
> On AbstractJavadocMojo.java, line 1492, the following method is called:
> {noformat}
> addArgIfNotEmpty( arguments, "-top", JavadocUtil.quotedArgument( top ),
> false, false, SINCE_JAVADOC_1_6 );
> {noformat}
> however, this method checks the version first, and then checks if the
> argument is null, like the following:
> {noformat}
> if ( isJavaDocVersionAtLeast( requiredJavaVersion ) )
> {
> addArgIfNotEmpty( arguments, key, value, repeatKey, splitValue );
> }
> else
> {
> if ( getLog().isWarnEnabled() )
> {
> getLog().warn( key + " option is not supported on Java
> version < " + requiredJavaVersion
>+ ". Ignore this option." );
> }
> }
> }}
> {noformat}
> Specifically for this command line argument, the method should check the
> version before calling addArgIfNotEmpty, thus removing the warning if we're
> not explicitly passing the argument in a jdk < 1.6
--
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] Closed: (MJAVADOC-188) -top command line argument is passed even when java version is <1.6, generating a warning
[
http://jira.codehaus.org/browse/MJAVADOC-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-188.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.5
fixed in r657363, snapshot 2.5 deployed
> -top command line argument is passed even when java version is <1.6,
> generating a warning
> -
>
> Key: MJAVADOC-188
> URL: http://jira.codehaus.org/browse/MJAVADOC-188
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: jdk 1.5
>Reporter: Cleber Zarate
>Assignee: Vincent Siveton
>Priority: Trivial
> Fix For: 2.5
>
>
> The -top argument is being passed when we're using a version smaller than 1.6.
> Then the following warning is generated:
> {noformat}
> "[WARNING] -top option is not supported on Java version < 1.6. Ignore this
> option."
> {noformat}
> This warning shouldn't be thrown since we're not setting the -top parameter
> in the POM, so there's no way to ignore it.
> On AbstractJavadocMojo.java, line 1492, the following method is called:
> {noformat}
> addArgIfNotEmpty( arguments, "-top", JavadocUtil.quotedArgument( top ),
> false, false, SINCE_JAVADOC_1_6 );
> {noformat}
> however, this method checks the version first, and then checks if the
> argument is null, like the following:
> {noformat}
> if ( isJavaDocVersionAtLeast( requiredJavaVersion ) )
> {
> addArgIfNotEmpty( arguments, key, value, repeatKey, splitValue );
> }
> else
> {
> if ( getLog().isWarnEnabled() )
> {
> getLog().warn( key + " option is not supported on Java
> version < " + requiredJavaVersion
>+ ". Ignore this option." );
> }
> }
> }}
> {noformat}
> Specifically for this command line argument, the method should check the
> version before calling addArgIfNotEmpty, thus removing the warning if we're
> not explicitly passing the argument in a jdk < 1.6
--
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: (MJAVADOC-184) Unable to differentiate JavaDoc reports when using multiple doclets
[ http://jira.codehaus.org/browse/MJAVADOC-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135246#action_135246 ] Vincent Siveton commented on MJAVADOC-184: -- Could you send us a test case? > Unable to differentiate JavaDoc reports when using multiple doclets > --- > > Key: MJAVADOC-184 > URL: http://jira.codehaus.org/browse/MJAVADOC-184 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Anthony Whitford > > If you configure the javadoc plugin with a reportSet using 2 doclets (like > the YDoc doclet, and the PDF doclet, for example), both reports appear on > projects-reports.html with the same Document and Description. There is > presently no way to differentiate them. > I think a reasonable solution is to have the ability to overwrite the > Document and Description for the generated reports page, so that I can label > the PDF version as such. -- 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] Created: (MNG-3581) stage:copy ClassCastException with maven 2.0.9
stage:copy ClassCastException with maven 2.0.9 -- Key: MNG-3581 URL: http://jira.codehaus.org/browse/MNG-3581 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Environment: tested on cygwin and freebsd Reporter: Olivier Lamy Priority: Blocker Fix For: 2.0.10 Using stage:copy with maven 2.0.9 generates a ClassCastException. (works fine with 2.0.8) The relevant part of the log say : [INFO] [INFO] org.apache.maven.wagon.providers.ssh.jsch.ScpWagon [INFO] [DEBUG] Trace java.lang.ClassCastException: org.apache.maven.wagon.providers.ssh.jsch.ScpWagon at org.apache.maven.plugins.stage.DefaultRepositoryCopier.copy(DefaultRepositoryCopier.java:252) at org.apache.maven.plugins.stage.CopyRepositoryMojo.execute(CopyRepositoryMojo.java:93) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecuto See http://www.nabble.com/stage%3Acopy-ClassCastException-with-maven-2.0.9-to17292204.html I add this issue in MNG as it looks more a core issue than a stage plugin issue. -- 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] Updated: (MNG-3581) stage:copy ClassCastException with maven 2.0.9
[ http://jira.codehaus.org/browse/MNG-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MNG-3581: -- Fix Version/s: 2.0.10 > stage:copy ClassCastException with maven 2.0.9 > -- > > Key: MNG-3581 > URL: http://jira.codehaus.org/browse/MNG-3581 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 > Environment: tested on cygwin and freebsd >Reporter: Olivier Lamy >Priority: Blocker > Fix For: 2.0.10 > > > Using stage:copy with maven 2.0.9 generates a ClassCastException. (works fine > with 2.0.8) > The relevant part of the log say : > [INFO] > > [INFO] org.apache.maven.wagon.providers.ssh.jsch.ScpWagon > [INFO] > > [DEBUG] Trace > java.lang.ClassCastException: > org.apache.maven.wagon.providers.ssh.jsch.ScpWagon > at > org.apache.maven.plugins.stage.DefaultRepositoryCopier.copy(DefaultRepositoryCopier.java:252) > at > org.apache.maven.plugins.stage.CopyRepositoryMojo.execute(CopyRepositoryMojo.java:93) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecuto > > See > http://www.nabble.com/stage%3Acopy-ClassCastException-with-maven-2.0.9-to17292204.html > I add this issue in MNG as it looks more a core issue than a stage plugin > issue. -- 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: (MJAVADOC-180) aggregation doesn't work for test-javadoc goal
[ http://jira.codehaus.org/browse/MJAVADOC-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135252#action_135252 ] Vincent Siveton commented on MJAVADOC-180: -- Could you send us a test case? > aggregation doesn't work for test-javadoc goal > -- > > Key: MJAVADOC-180 > URL: http://jira.codehaus.org/browse/MJAVADOC-180 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.4 > Environment: maven-javadoc-plugin 2.3 final > maven-javadoc-plugin 2.4-SNAPSHOT r632385 > Maven version: 2.0.8 > Java version: 1.5.0_13 > OS name: "mac os x" version: "10.5.2" arch: "i386" Family: "unix" >Reporter: Elliot Metsger > > When executing 'javadoc:test-javadoc' from a parent project in a multi-module > build, it fails complaining of missing dependencies: > mvn clean -X -e javadoc:test-javadoc > > [DEBUG] embargo-api: using locally installed snapshot > [DEBUG] dspace-api: resolved to version 1.4.2e-20080118.034638-23 from > repository msel.maven.snapshots > [DEBUG] Compiled artifacts for > edu.jhu.library.embargo:embargo-dspace:1.0.0-SNAPSHOT > /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar > /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar > /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar > /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar > /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar > /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar > /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar > /Users/esm/.m2/repository/edu/jhu/library/embargo/embargo-api/1.0.0-SNAPSHOT/embargo-api-1.0.0-SNAPSHOT.jar > /Users/esm/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar > /Users/esm/.m2/repository/org/dspace/dspace-api/1.4.2e-SNAPSHOT/dspace-api-1.4.2e-SNAPSHOT.jar > /Users/esm/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar > > [DEBUG] "cd /Users/esm/idea/workspace/embargo/target/site/testapidocs && > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc" > @options @packages > [search path for source files: > [/Users/esm/idea/workspace/embargo/embargo-api/src/test/java, > /Users/esm/idea/workspace/embargo/embargo-dspace/src/test/java]] > [search path for class files: > [/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/classes.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/ui.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/laf.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jsse.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jce.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/charsets.jar, > /System/Library/Java/Extensions/CoreAudio.jar, > /System/Library/Java/Extensions/dns_sd.jar, > /System/Library/Java/Extensions/j3daudio.jar, > /System/Library/Java/Extensions/j3dcore.jar, > /System/Library/Java/Extensions/j3dutils.jar, > /System/Library/Java/Extensions/jai_codec.jar, > /System/Library/Java/Extensions/jai_core.jar, > /System/Library/Java/Extensions/mlibwrapper_jai.jar, > /System/Library/Java/Extensions/MRJToolkit.jar, > /System/Library/Java/Extensions/QTJava.zip, > /System/Library/Java/Extensions/vecmath.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/dnsns.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/localedata.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunjce_provider.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunpkcs11.jar, > /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar, > /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar, > /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar, > /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar, > /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar, > /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar, > /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar, > /Users/esm/.m2/repository/edu/jhu/library/embargo/embargo-api/1.0.0-SNAPSHOT/embargo-api-1.0.0-SNAPSHOT.jar, > > /Users/esm/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar, > > /Users/esm/.m2/repository/org/dspace/dspace-api/1.4.2e-SNAPSHOT/dspace-api-1.4.2e-SNAPSHOT.jar, > > /Users/esm/.m2/reposit
[jira] Closed: (MJAVADOC-171) Modules in multi-module projects are "built" too often
[ http://jira.codehaus.org/browse/MJAVADOC-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-171. Resolution: Fixed Fix Version/s: 2.4 javadoc 2.4 should resolved it > Modules in multi-module projects are "built" too often > -- > > Key: MJAVADOC-171 > URL: http://jira.codehaus.org/browse/MJAVADOC-171 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: Maven 2.0.8, Linux >Reporter: Stefan Seidel >Priority: Critical > Fix For: 2.4 > > Attachments: 2.2.log, 2.3.log, mjavadoc171.patch, mvnexec.zip > > > In a multi-module project, all modules are "built" twice for each module. > This leads to huge performance problems when many modules are in a project. > In the attached sample project, the xmlbeans plugin is executed 27 times for > a project with one parent module and two submodules. 18 of these executions > can be attributed to the javadoc plugin. With version 2.2, only 3 invocations > (once for each project) are caused by the javadoc plugin. -- 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] Updated: (MJAVADOC-180) aggregation doesn't work for test-javadoc goal
[ http://jira.codehaus.org/browse/MJAVADOC-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliot Metsger updated MJAVADOC-180: Attachment: mjavadoc-180.tar Hi Vincent, thanks for taking a look. I'm attaching mjavadoc-180.tar which will explode the test case to its own subdirectory. Running 'mvn javadoc:test-javadoc' will produce the failure. I've noted in the parent pom where you can work around this issue by changing to 'false'. Hopefully I'm not trying to do anything silly. Thanks! > aggregation doesn't work for test-javadoc goal > -- > > Key: MJAVADOC-180 > URL: http://jira.codehaus.org/browse/MJAVADOC-180 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.4 > Environment: maven-javadoc-plugin 2.3 final > maven-javadoc-plugin 2.4-SNAPSHOT r632385 > Maven version: 2.0.8 > Java version: 1.5.0_13 > OS name: "mac os x" version: "10.5.2" arch: "i386" Family: "unix" >Reporter: Elliot Metsger > Attachments: mjavadoc-180.tar > > > When executing 'javadoc:test-javadoc' from a parent project in a multi-module > build, it fails complaining of missing dependencies: > mvn clean -X -e javadoc:test-javadoc > > [DEBUG] embargo-api: using locally installed snapshot > [DEBUG] dspace-api: resolved to version 1.4.2e-20080118.034638-23 from > repository msel.maven.snapshots > [DEBUG] Compiled artifacts for > edu.jhu.library.embargo:embargo-dspace:1.0.0-SNAPSHOT > /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar > /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar > /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar > /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar > /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar > /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar > /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar > /Users/esm/.m2/repository/edu/jhu/library/embargo/embargo-api/1.0.0-SNAPSHOT/embargo-api-1.0.0-SNAPSHOT.jar > /Users/esm/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar > /Users/esm/.m2/repository/org/dspace/dspace-api/1.4.2e-SNAPSHOT/dspace-api-1.4.2e-SNAPSHOT.jar > /Users/esm/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar > > [DEBUG] "cd /Users/esm/idea/workspace/embargo/target/site/testapidocs && > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc" > @options @packages > [search path for source files: > [/Users/esm/idea/workspace/embargo/embargo-api/src/test/java, > /Users/esm/idea/workspace/embargo/embargo-dspace/src/test/java]] > [search path for class files: > [/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/classes.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/ui.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/laf.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jsse.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jce.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/charsets.jar, > /System/Library/Java/Extensions/CoreAudio.jar, > /System/Library/Java/Extensions/dns_sd.jar, > /System/Library/Java/Extensions/j3daudio.jar, > /System/Library/Java/Extensions/j3dcore.jar, > /System/Library/Java/Extensions/j3dutils.jar, > /System/Library/Java/Extensions/jai_codec.jar, > /System/Library/Java/Extensions/jai_core.jar, > /System/Library/Java/Extensions/mlibwrapper_jai.jar, > /System/Library/Java/Extensions/MRJToolkit.jar, > /System/Library/Java/Extensions/QTJava.zip, > /System/Library/Java/Extensions/vecmath.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/dnsns.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/localedata.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunjce_provider.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunpkcs11.jar, > /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar, > /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar, > /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar, > /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar, > /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar, > /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar, > /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar, >
[jira] Commented: (MJAVADOC-180) aggregation doesn't work for test-javadoc goal
[ http://jira.codehaus.org/browse/MJAVADOC-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135257#action_135257 ] Elliot Metsger commented on MJAVADOC-180: - The exception from the test case is slightly different than what is reported in the in the description: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error has occurred in Test JavaDocs report generation:Exit code: 1 - /private/tmp/MJAVADOC-180/module1/src/test/java/edu/jhu/library/Mjavadoc180Test.java:3: package org.junit does not exist import static org.junit.Assert.assertTrue; ^ /private/tmp/MJAVADOC-180/module1/src/test/java/edu/jhu/library/Mjavadoc180Test.java:3: static import only from classes and interfaces import static org.junit.Assert.assertTrue; ^ /private/tmp/MJAVADOC-180/module1/src/test/java/edu/jhu/library/Mjavadoc180Test.java:4: package org.junit does not exist import org.junit.Test; ^ /private/tmp/MJAVADOC-180/module1/src/test/java/edu/jhu/library/Mjavadoc180Test.java:5: package org.dbunit.database does not exist import org.dbunit.database.IDatabaseConnection; ^ /private/tmp/MJAVADOC-180/module1/src/test/java/edu/jhu/library/Mjavadoc180Test.java:19: cannot find symbol symbol : class Test location: class edu.jhu.library.Mjavadoc180Test @Test ^ I think this is because JUnit is not defined in the parent (unlike in my real-world project where it is). I think this still is evidence of this issue. > aggregation doesn't work for test-javadoc goal > -- > > Key: MJAVADOC-180 > URL: http://jira.codehaus.org/browse/MJAVADOC-180 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.4 > Environment: maven-javadoc-plugin 2.3 final > maven-javadoc-plugin 2.4-SNAPSHOT r632385 > Maven version: 2.0.8 > Java version: 1.5.0_13 > OS name: "mac os x" version: "10.5.2" arch: "i386" Family: "unix" >Reporter: Elliot Metsger > Attachments: mjavadoc-180.tar > > > When executing 'javadoc:test-javadoc' from a parent project in a multi-module > build, it fails complaining of missing dependencies: > mvn clean -X -e javadoc:test-javadoc > > [DEBUG] embargo-api: using locally installed snapshot > [DEBUG] dspace-api: resolved to version 1.4.2e-20080118.034638-23 from > repository msel.maven.snapshots > [DEBUG] Compiled artifacts for > edu.jhu.library.embargo:embargo-dspace:1.0.0-SNAPSHOT > /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar > /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar > /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar > /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar > /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar > /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar > /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar > /Users/esm/.m2/repository/edu/jhu/library/embargo/embargo-api/1.0.0-SNAPSHOT/embargo-api-1.0.0-SNAPSHOT.jar > /Users/esm/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar > /Users/esm/.m2/repository/org/dspace/dspace-api/1.4.2e-SNAPSHOT/dspace-api-1.4.2e-SNAPSHOT.jar > /Users/esm/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar > > [DEBUG] "cd /Users/esm/idea/workspace/embargo/target/site/testapidocs && > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc" > @options @packages > [search path for source files: > [/Users/esm/idea/workspace/embargo/embargo-api/src/test/java, > /Users/esm/idea/workspace/embargo/embargo-dspace/src/test/java]] > [search path for class files: > [/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/classes.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/ui.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/laf.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jsse.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jce.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/charsets.jar, > /System/Library/Java/Extensions/CoreAudio.jar, > /System/Library/Java/Extensions/dns_sd.jar, > /System/Library/Java/Extensions/j3daudio.jar, > /System/Library/Java/Extensions/j3dcore.jar, > /System/Library/Java/Extensions/j3dutils.jar, > /System/Library/Java/Extensions/jai_codec.jar, > /System/Library/Java/Extensions/jai_core.jar, > /System/Library/Java/Extensions/mlibwrapper_jai.jar, > /System/Library/Java/Extensions/MRJToolkit
[jira] Commented: (MJAVADOC-183) Aggregate javadoc does not process the src/main/javadoc directories
[
http://jira.codehaus.org/browse/MJAVADOC-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135259#action_135259
]
Heinrich Nirschl commented on MJAVADOC-183:
---
Thanks, the version 2.5-20080517.141532-2 is working again.
> Aggregate javadoc does not process the src/main/javadoc directories
> ---
>
> Key: MJAVADOC-183
> URL: http://jira.codehaus.org/browse/MJAVADOC-183
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: Windows XP, Maven 2.0.9
>Reporter: Peter Hayes
>Assignee: Vincent Siveton
>Priority: Critical
> Fix For: 2.5
>
> Attachments: javadoc-aggregate.zip
>
>
> When running the javadoc plugin in aggregate mode, the plugin ignores the
> src/main/javadoc directory of the child module.
> *options file when running in non-aggregate*
> {quote}
> -classpath 'C:/dev/maven/bugs/javadoc-aggregate/child/target/classes'
> -encoding
> 'ISO-8859-1'
> -protected
> -sourcepath
> 'C:/dev/maven/bugs/javadoc-aggregate/child/src/main/java;C:/dev/maven/bugs/javadoc-aggregate/child/src/main/javadoc'
> -author
> -bottom
> 'Copyright © 2008. All Rights Reserved.'
> -charset
> 'ISO-8859-1'
> -d
> 'C:/dev/maven/bugs/javadoc-aggregate/child/target/site/apidocs'
> -doctitle
> 'child 1.0-SNAPSHOT API'
> -use
> -version
> -windowtitle
> 'child 1.0-SNAPSHOT API'
> {quote}
> *options file when running in aggregate*
> {quote}
> -classpath
> 'C:/dev/maven/bugs/javadoc-aggregate/target/classes;C:/dev/maven/bugs/javadoc-aggregate/child/target/classes'
> -encoding
> 'ISO-8859-1'
> -protected
> -sourcepath
> 'C:/dev/maven/bugs/javadoc-aggregate/child/src/main/java'
> -author
> -bottom
> 'Copyright © 2008. All Rights Reserved.'
> -charset
> 'ISO-8859-1'
> -d
> 'C:/dev/maven/bugs/javadoc-aggregate/target/site/apidocs'
> -doctitle
> 'aggregate javadoc parent 1.0-SNAPSHOT API'
> -use
> -version
> -windowtitle
> 'aggregate javadoc parent 1.0-SNAPSHOT API'
> {quote}
--
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] Created: (MAVENUPLOAD-2065) Flying Saucer xhtmlrenderer R8pre2
Flying Saucer xhtmlrenderer R8pre2 -- Key: MAVENUPLOAD-2065 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2065 Project: maven-upload-requests Issue Type: Task Reporter: fabrizio giustina -- 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: (MASSEMBLY-73) Sharing a default assembly descriptor across sub modules
[ http://jira.codehaus.org/browse/MASSEMBLY-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135279#action_135279 ] Kaizer Sogiawala commented on MASSEMBLY-73: --- What are the plans of releasing maven-assembly-artifact-types:2.2-beta-2 ? I see maven-assembly-plugin:2.2-beta-2 is already available > Sharing a default assembly descriptor across sub modules > > > Key: MASSEMBLY-73 > URL: http://jira.codehaus.org/browse/MASSEMBLY-73 > Project: Maven 2.x Assembly Plugin > Issue Type: New Feature >Affects Versions: 2.0.1 >Reporter: vinoth rajasekaran >Assignee: John Casey > Fix For: 2.2-beta-2 > > > I have a multi-project folders setup like one shown below, > > root > |_ sub-folder1 > |_ sub-folder2 > |_ sub-folder3 > |_ etc > > Have a root pom.xml at the root folder level and in that I have defined > > maven-assembly-plugin > > > src/main/assembly/descriptor.xml > > > > > > Above descriptor works fine only if I have defined a descriptor file on the > src/main/assembly folder for each sub-folder1, sub-folder2, etc. > It would be great if maven supports me in defining a common assembly > descriptor and can be shared by all the sub modules from a common location. -- 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
