[jira] Commented: (MPLUGINTESTING-7) parameters annotated with default-value are not injected
[ http://jira.codehaus.org/browse/MPLUGINTESTING-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246578#action_246578 ] Francis De Brabandere commented on MPLUGINTESTING-7: I have been looking around at some source code and a lot of people seem to have encountered this annoying issue. > parameters annotated with default-value are not injected > > > Key: MPLUGINTESTING-7 > URL: http://jira.codehaus.org/browse/MPLUGINTESTING-7 > Project: Maven 2.x Plugin Testing > Issue Type: Bug > Components: plugin-testing-harness >Affects Versions: 1.1 >Reporter: Alex Eagle > > I have a Mojo with several parameters annotated with a default-value: > /** >* Colon-delimited packages to whitelist >* >* @parameter default-value="" >*/ > private String whiteList; > But when I lookupMojo() my mojo in an AbstractMojoTestCase, I get a mojo with > a null value in whiteList. > shouldn't I get an empty string instead? > Thanks! -- 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-212) src/main/java does not exist for non-jar project
src/main/java does not exist for non-jar project
Key: MPIR-212
URL: http://jira.codehaus.org/browse/MPIR-212
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Affects Versions: 2.3
Environment: ubuntu linux maven 2.2.1
Reporter: Francis De Brabandere
Priority: Critical
We have our own custom packaging that does not compile java code.
Since the 2.3 plugin we get this issue while running "mvn clean install site":
...
[INFO] [site:site {execution: default-site}]
[INFO] Not executing cobertura:report as the cobertura data file
(xxx/cobertura/cobertura.ser) could not be found
[INFO] Parent project loaded from repository: xxx-parent:pom:8-SNAPSHOT
[INFO] Skipped "Surefire Report" report, file "surefire-report.html" already
exists for the English version.
[INFO] Generating "Continuous Integration" report.
[INFO] Generating "Project Summary" report.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven report: error while invoking generate
basedir xxx/src/main/java does not exist
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error during page
generation
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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:597)
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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page
generation
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:123)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
rendering Maven report: error while invoking generate
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:171)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:154)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:118)
... 19 more
Caused by: org.apache.maven.reporting.MavenReportException: error while
invoking generate
at
org.apache.maven.plugins.site.ReportDocumentRenderer.generateMultiPage(ReportDocumentRenderer.java:248)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:157)
... 23 more
Caused by: java.lang.reflect.InvocationTargetException
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:597)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.generateMultiPage(ReportDocumentRenderer.
[jira] Commented: (MPIR-212) src/main/java does not exist for non-jar project
[
http://jira.codehaus.org/browse/MPIR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247817#action_247817
]
Francis De Brabandere commented on MPIR-212:
could you point me to the snapshot repo?
> src/main/java does not exist for non-jar project
>
>
> Key: MPIR-212
> URL: http://jira.codehaus.org/browse/MPIR-212
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 2.3
> Environment: ubuntu linux maven 2.2.1
>Reporter: Francis De Brabandere
>Assignee: Lukas Theussl
>Priority: Critical
> Fix For: 2.4
>
>
> We have our own custom packaging that does not compile java code.
> Since the 2.3 plugin we get this issue while running "mvn clean install site":
> ...
> [INFO] [site:site {execution: default-site}]
> [INFO] Not executing cobertura:report as the cobertura data file
> (xxx/cobertura/cobertura.ser) could not be found
> [INFO] Parent project loaded from repository: xxx-parent:pom:8-SNAPSHOT
> [INFO] Skipped "Surefire Report" report, file "surefire-report.html" already
> exists for the English version.
> [INFO] Generating "Continuous Integration" report.
> [INFO] Generating "Project Summary" report.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: error while invoking generate
> basedir xxx/src/main/java does not exist
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page
> generation
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> 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:597)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:123)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> ... 17 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
> rendering Maven report: error while invoking generate
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:171)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:154)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:118)
> ... 19 more
> Caused by: org.apache.maven.reporting.MavenReportException: error while
> invoking generate
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.generateMultiPage(ReportDocumentRenderer.java:248)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:157)
> ... 23 more
> Caused by:
[jira] Commented: (MPIR-212) src/main/java does not exist for non-jar project
[
http://jira.codehaus.org/browse/MPIR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247825#action_247825
]
Francis De Brabandere commented on MPIR-212:
found it: https://repository.apache.org/content/repositories/snapshots
I just tested the snapshot and the problem is fixed.
> src/main/java does not exist for non-jar project
>
>
> Key: MPIR-212
> URL: http://jira.codehaus.org/browse/MPIR-212
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 2.3
> Environment: ubuntu linux maven 2.2.1
>Reporter: Francis De Brabandere
>Assignee: Lukas Theussl
>Priority: Critical
> Fix For: 2.4
>
>
> We have our own custom packaging that does not compile java code.
> Since the 2.3 plugin we get this issue while running "mvn clean install site":
> ...
> [INFO] [site:site {execution: default-site}]
> [INFO] Not executing cobertura:report as the cobertura data file
> (xxx/cobertura/cobertura.ser) could not be found
> [INFO] Parent project loaded from repository: xxx-parent:pom:8-SNAPSHOT
> [INFO] Skipped "Surefire Report" report, file "surefire-report.html" already
> exists for the English version.
> [INFO] Generating "Continuous Integration" report.
> [INFO] Generating "Project Summary" report.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: error while invoking generate
> basedir xxx/src/main/java does not exist
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page
> generation
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> 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:597)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:123)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> ... 17 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
> rendering Maven report: error while invoking generate
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:171)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:154)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:118)
> ... 19 more
> Caused by: org.apache.maven.reporting.MavenReportException: error while
> invoking generate
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.generateMultiPage(ReportDocumentRenderer.java:248)
> at
> org.apache.maven.plugins.site.ReportDocumentRender
[jira] (MINSTALL-87) Install:install-file on missing file should fail, not indicate success with bogus jar file message
[ https://jira.codehaus.org/browse/MINSTALL-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304070#comment-304070 ] Francis De Brabandere commented on MINSTALL-87: --- This very annoying! Also it's clearly a BUG and not an Improvement. Should be easy to fix. Used to fail correctly with maven 2.x (see output below) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error installing artifact 'com.bugsense:bugsense-trace:jar': Error installing artifact: File myproject/libs/bugsense-trace-1-9.jar does not exist > Install:install-file on missing file should fail, not indicate success with > bogus jar file message > -- > > Key: MINSTALL-87 > URL: https://jira.codehaus.org/browse/MINSTALL-87 > Project: Maven 2.x Install Plugin > Issue Type: Improvement > Components: install:install-file >Affects Versions: 2.3.1 > Environment: RHEL 6.1 >Reporter: Chris Lott >Priority: Minor > > I had to install a third-party jar into my local repository and used maven to > do so. But I botched the file name, and confusingly the plugin did not > complain; in fact it reported total success. It creates a pom file but no > jar file. I think the build should fail if the file to be installed is not > found. > Reproduce with the following invocation: > mvn install:install-file -DgroupId=foo -DartifactId=foo -Dversion=1 > -Dfile=/tmp/doesnotexit-comma-trust-me -Dpackaging=jar -DgeneratePom=true > Below is the log from running this operation. Despite the message, it did > NOT create a jar file. > [INFO] Scanning for projects... > [INFO] > [INFO] > > [INFO] Building Maven Stub Project (No POM) 1 > [INFO] > > [INFO] > [INFO] --- maven-install-plugin:2.3.1:install-file (default-cli) @ > standalone-pom --- > [INFO] Installing /tmp/doesnotexit-comma-trust-me to > /home/user/.m2/repository/foo/foo/1/foo-1.jar > [INFO] Installing /tmp/mvninstall4193497156837259347.pom to > /home/user/.m2/repository/foo/foo/1/foo-1.pom > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 0.422s > [INFO] Finished at: Mon May 21 11:04:30 EDT 2012 > [INFO] Final Memory: 4M/359M > [INFO] > > Finally, here is full version info. > $ mvn -version > Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500) > Maven home: /home/user/Programs/apache-maven-3.0.4 > Java version: 1.6.0_30, vendor: Sun Microsystems Inc. > Java home: /usr/java/jdk1.6.0_30/jre > Default locale: en_US, platform encoding: UTF-8 > Thanks for listening. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-87) Install:install-file on missing file should fail, not indicate success with bogus jar file message
[ https://jira.codehaus.org/browse/MINSTALL-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304263#comment-304263 ] Francis De Brabandere commented on MINSTALL-87: --- We need to find a team membet that can do this... > Install:install-file on missing file should fail, not indicate success with > bogus jar file message > -- > > Key: MINSTALL-87 > URL: https://jira.codehaus.org/browse/MINSTALL-87 > Project: Maven 2.x Install Plugin > Issue Type: Improvement > Components: install:install-file >Affects Versions: 2.3.1 > Environment: RHEL 6.1 >Reporter: Chris Lott >Priority: Minor > > I had to install a third-party jar into my local repository and used maven to > do so. But I botched the file name, and confusingly the plugin did not > complain; in fact it reported total success. It creates a pom file but no > jar file. I think the build should fail if the file to be installed is not > found. > Reproduce with the following invocation: > mvn install:install-file -DgroupId=foo -DartifactId=foo -Dversion=1 > -Dfile=/tmp/doesnotexit-comma-trust-me -Dpackaging=jar -DgeneratePom=true > Below is the log from running this operation. Despite the message, it did > NOT create a jar file. > [INFO] Scanning for projects... > [INFO] > [INFO] > > [INFO] Building Maven Stub Project (No POM) 1 > [INFO] > > [INFO] > [INFO] --- maven-install-plugin:2.3.1:install-file (default-cli) @ > standalone-pom --- > [INFO] Installing /tmp/doesnotexit-comma-trust-me to > /home/user/.m2/repository/foo/foo/1/foo-1.jar > [INFO] Installing /tmp/mvninstall4193497156837259347.pom to > /home/user/.m2/repository/foo/foo/1/foo-1.pom > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 0.422s > [INFO] Finished at: Mon May 21 11:04:30 EDT 2012 > [INFO] Final Memory: 4M/359M > [INFO] > > Finally, here is full version info. > $ mvn -version > Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500) > Maven home: /home/user/Programs/apache-maven-3.0.4 > Java version: 1.6.0_30, vendor: Sun Microsystems Inc. > Java home: /usr/java/jdk1.6.0_30/jre > Default locale: en_US, platform encoding: UTF-8 > Thanks for listening. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-87) Install:install-file on missing file should fail, not indicate success with bogus jar file message
[ https://jira.codehaus.org/browse/MINSTALL-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304264#comment-304264 ] Francis De Brabandere commented on MINSTALL-87: --- Can you as creator not edit the issue? > Install:install-file on missing file should fail, not indicate success with > bogus jar file message > -- > > Key: MINSTALL-87 > URL: https://jira.codehaus.org/browse/MINSTALL-87 > Project: Maven 2.x Install Plugin > Issue Type: Improvement > Components: install:install-file >Affects Versions: 2.3.1 > Environment: RHEL 6.1 >Reporter: Chris Lott >Priority: Minor > > I had to install a third-party jar into my local repository and used maven to > do so. But I botched the file name, and confusingly the plugin did not > complain; in fact it reported total success. It creates a pom file but no > jar file. I think the build should fail if the file to be installed is not > found. > Reproduce with the following invocation: > mvn install:install-file -DgroupId=foo -DartifactId=foo -Dversion=1 > -Dfile=/tmp/doesnotexit-comma-trust-me -Dpackaging=jar -DgeneratePom=true > Below is the log from running this operation. Despite the message, it did > NOT create a jar file. > [INFO] Scanning for projects... > [INFO] > [INFO] > > [INFO] Building Maven Stub Project (No POM) 1 > [INFO] > > [INFO] > [INFO] --- maven-install-plugin:2.3.1:install-file (default-cli) @ > standalone-pom --- > [INFO] Installing /tmp/doesnotexit-comma-trust-me to > /home/user/.m2/repository/foo/foo/1/foo-1.jar > [INFO] Installing /tmp/mvninstall4193497156837259347.pom to > /home/user/.m2/repository/foo/foo/1/foo-1.pom > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 0.422s > [INFO] Finished at: Mon May 21 11:04:30 EDT 2012 > [INFO] Final Memory: 4M/359M > [INFO] > > Finally, here is full version info. > $ mvn -version > Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500) > Maven home: /home/user/Programs/apache-maven-3.0.4 > Java version: 1.6.0_30, vendor: Sun Microsystems Inc. > Java home: /usr/java/jdk1.6.0_30/jre > Default locale: en_US, platform encoding: UTF-8 > Thanks for listening. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2066) Specify multiple proxies
[ http://jira.codehaus.org/browse/MNG-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218486#action_218486 ] Francis De Brabandere commented on MNG-2066: Do I understand correctly that there is no way to use http together with https repositories when you are behind a single http/https capable proxy? Because of this we can not use the new jboss https (nexus) repository from within our network (without using extra tools). > Specify multiple proxies > > > Key: MNG-2066 > URL: http://jira.codehaus.org/browse/MNG-2066 > Project: Maven 2 & 3 > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Thomas Recloux > Attachments: MNG-2066-maven-site.patch, MNG-2066-maven.patch, > multiple-proxies-paches.zip > > > After this discussion : > http://www.mail-archive.com/d...@maven.apache.org/msg53099.html > In the attached zip file, you'll find four patch files : > - on the maven-artifact-manager projet : changes in the DefaultWagonManager > class, using the http proxy when no https proxy is specified. > - on the maven-core project : changes in the DefaultMaven, adding all teh > active proxies from the settings to the wagon manager > - on the maven-settings project : changes in the settings.mdo file > Theses patches are built on the maven-2.0.x branch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2066) Specify multiple proxies
[ http://jira.codehaus.org/browse/MNG-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218558#action_218558 ] Francis De Brabandere commented on MNG-2066: We actually use nexus but for some reason we can not add jboss to it. It's not because tools like nexus exist that this should not be fixed. > Specify multiple proxies > > > Key: MNG-2066 > URL: http://jira.codehaus.org/browse/MNG-2066 > Project: Maven 2 & 3 > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Thomas Recloux > Attachments: MNG-2066-maven-site.patch, MNG-2066-maven.patch, > multiple-proxies-paches.zip > > > After this discussion : > http://www.mail-archive.com/d...@maven.apache.org/msg53099.html > In the attached zip file, you'll find four patch files : > - on the maven-artifact-manager projet : changes in the DefaultWagonManager > class, using the http proxy when no https proxy is specified. > - on the maven-core project : changes in the DefaultMaven, adding all teh > active proxies from the settings to the wagon manager > - on the maven-settings project : changes in the settings.mdo file > Theses patches are built on the maven-2.0.x branch. -- 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-4643) Transitive dependency not available for dependency in test scope
Transitive dependency not available for dependency in test scope Key: MNG-4643 URL: http://jira.codehaus.org/browse/MNG-4643 Project: Maven 2 & 3 Issue Type: Bug Components: Dependencies Affects Versions: 3.0-beta-1 Environment: linux Reporter: Francis De Brabandere Attachments: testbrokendep.tar.gz I depend on apache ftpserver for my tests. But somehow since 3.0-beta-1 the transitive apache mina dependency is not available in the test classpath any more See the provided project. This code works on maven 2.x and also worked with 3.x versions until 3.0-alpha-7. But with beta 1 this build fails with class not found. Apache Maven 3.0-beta-1 (r935667; 2010-04-19 19:00:39+0200) Java version: 1.6.0_16 Java home: /usr/lib/jvm/java-6-sun-1.6.0.16/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux" version: "2.6.31-20-generic" arch: "i386" Family: "unix" -- 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-4643) Transitive dependency not available for dependency in test scope
[ http://jira.codehaus.org/browse/MNG-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis De Brabandere updated MNG-4643: --- Attachment: testbrokendep.zip that tar.gz is broken > Transitive dependency not available for dependency in test scope > > > Key: MNG-4643 > URL: http://jira.codehaus.org/browse/MNG-4643 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0-beta-1 > Environment: linux >Reporter: Francis De Brabandere > Attachments: testbrokendep.tar.gz, testbrokendep.zip > > > I depend on apache ftpserver for my tests. But somehow since 3.0-beta-1 the > transitive apache mina dependency is not available in the test classpath any > more > See the provided project. This code works on maven 2.x and also worked with > 3.x versions until 3.0-alpha-7. But with beta 1 this build fails with class > not found. > Apache Maven 3.0-beta-1 (r935667; 2010-04-19 19:00:39+0200) > Java version: 1.6.0_16 > Java home: /usr/lib/jvm/java-6-sun-1.6.0.16/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.31-20-generic" arch: "i386" Family: "unix" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4643) [regression] Transitive dependency not available due to dependency POM erroneously rejected as invalid
[ http://jira.codehaus.org/browse/MNG-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218988#action_218988 ] Francis De Brabandere commented on MNG-4643: I suppose you would want to fail the whole build if this happens instead of ignoring the dependency... If this is fixed by doing unstrict parsing I would at least log a warning. I'll contact the ftpserver guys on this issue with their pom. > [regression] Transitive dependency not available due to dependency POM > erroneously rejected as invalid > -- > > Key: MNG-4643 > URL: http://jira.codehaus.org/browse/MNG-4643 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0-alpha-7, 3.0-beta-1 > Environment: linux >Reporter: Francis De Brabandere > Fix For: 3.0-beta-2 > > Attachments: testbrokendep.tar.gz, testbrokendep.zip > > > I depend on apache ftpserver for my tests. But somehow since 3.0-beta-1 the > transitive apache mina dependency is not available in the test classpath any > more > See the provided project. This code works on maven 2.x and also worked with > 3.x versions until 3.0-alpha-7. But with beta 1 this build fails with class > not found. > Apache Maven 3.0-beta-1 (r935667; 2010-04-19 19:00:39+0200) > Java version: 1.6.0_16 > Java home: /usr/lib/jvm/java-6-sun-1.6.0.16/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.31-20-generic" arch: "i386" Family: "unix" -- 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-276) Initial builds of a multi-module project fail
[
http://jira.codehaus.org/browse/MJAVADOC-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220690#action_220690
]
Francis De Brabandere commented on MJAVADOC-276:
This is not the same problem as MJAVADOC-275 (I don't have that logging
described there) and is not fixed with 2.7
Initial site builds using the javadoc plugin have been broken since 2.5. This
is a major issue that everybody using maven will encounter when setting up CI
builds!
see the provided javadoctest.zip
{noformat}
mvn clean install site
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] javadoctest
[INFO] javadoctestapi
[INFO] javadoctestimpl
[INFO]
[INFO] Building javadoctest
[INFO]task-segment: [clean, install, site]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory /home/axeja/workspace/javadoctest/target
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/axeja/workspace/javadoctest/pom.xml to
/home/axeja/.m2/repository/javadoc/test/javadoctest/0.0.1-SNAPSHOT/javadoctest-0.0.1-SNAPSHOT.pom
[INFO] Preparing javadoc:test-javadoc
[INFO] No goals needed for project - skipping
[INFO] Preparing javadoc:test-aggregate
[INFO]
[INFO] Building javadoctest
[INFO]
[INFO] No goals needed for project - skipping
[INFO]
[INFO] Building javadoctestapi
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/axeja/workspace/javadoctest/javadoctestapi/src/main/resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] Building javadoctestimpl
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/axeja/workspace/javadoctest/javadoctestimpl/src/main/resources
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) javadoc.test:javadoctestapi:jar:0.0.1-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=javadoc.test
-DartifactId=javadoctestapi -Dversion=0.0.1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=javadoc.test -DartifactId=javadoctestapi
-Dversion=0.0.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
Path to dependency:
1) javadoc.test:javadoctestimpl:jar:0.0.1-SNAPSHOT
2) javadoc.test:javadoctestapi:jar:0.0.1-SNAPSHOT
--
1 required artifact is missing.
for artifact:
javadoc.test:javadoctestimpl:jar:0.0.1-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 8 seconds
[INFO] Finished at: Mon May 10 17:31:24 CEST 2010
[INFO] Final Memory: 42M/319M
[INFO]
{noformat}
> Initial builds of a multi-module project fail
> -
>
> Key: MJAVADOC-276
> URL: http://jira.codehaus.org/browse/MJAVADOC-276
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.6.1
> Environment: Java jdk1.6.0_16, Maven 2.2.1, Windows Vista 64-bit
> Java jdk1.6.0_05, Maven 2.0.9, Windows XP 32-bit
>Reporter: Anthony Whitford
>Assignee: John Casey
>Priority: Blocker
> Fix For: 2.7
>
> Attachments: bug.zip
>
>
> I ran into a problem using Maven Javadoc Plugin 2.6.1 right after I
> released... I went from version 1.15 to 1.16-SNAPSHOT, and my 1.16-SNAPSHOT
>
[jira] Updated: (MJAVADOC-276) Initial builds of a multi-module project fail
[
http://jira.codehaus.org/browse/MJAVADOC-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francis De Brabandere updated MJAVADOC-276:
---
Attachment: javadoctest.zip
To reproduce:
rm ~/.m2/repository/javadoc -rf
mvn clean install site
> Initial builds of a multi-module project fail
> -
>
> Key: MJAVADOC-276
> URL: http://jira.codehaus.org/browse/MJAVADOC-276
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.6.1
> Environment: Java jdk1.6.0_16, Maven 2.2.1, Windows Vista 64-bit
> Java jdk1.6.0_05, Maven 2.0.9, Windows XP 32-bit
>Reporter: Anthony Whitford
>Assignee: John Casey
>Priority: Blocker
> Fix For: 2.7
>
> Attachments: bug.zip, javadoctest.zip
>
>
> I ran into a problem using Maven Javadoc Plugin 2.6.1 right after I
> released... I went from version 1.15 to 1.16-SNAPSHOT, and my 1.16-SNAPSHOT
> build failed ({{mvn clean install site}}) because Javadoc fails when run from
> the top-level parent. When it is building _module A_, the javadoc complains
> that _module B_ and _module C_ are missing -- of course they are, they
> haven't been built yet. Note that running {{mvn clean install}} from _module
> A_ works fine -- the behavior is limited to running from the top-level parent
> -- AND, if you run a {{mvn install}} for _module B_ and _module C_, then you
> have given it what it needs and so you won't see the error.
> The attached example exhibits the problem. It was created from the
> _j2ee-simple_ archetype -- I only added the explicit javadoc plugin
> declaration to the top level pom to control the version being used. To
> recreate the problem, unzip and simply: {{mvn clean install site}}. You
> will get an error message like:
> {noformat}
> [INFO] Unable to find resource 'root.project.projects:logging:jar:1.0' in
> repository central (http://repo1.maven.org/maven2)
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
> Missing:
> --
> 1) root.project.projects:logging:jar:1.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=root.project.projects
> -DartifactId=logging -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=root.project.projects
> -DartifactId=logging -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=
> [id]
> Path to dependency:
> 1) root.project:primary-source:jar:1.0
> 2) root.project.projects:logging:jar:1.0
> --
> 1 required artifact is missing.
> for artifact:
> root.project:primary-source:jar:1.0
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> {noformat}
> As you can see, it seems to think that a submodule (in this case
> {{root.project.projects:logging:jar:1.0}}) is necessary to build the javadoc
> for the project... Since this is the first time that this is being built,
> the submodule does not exist (yet).
> I have replicated this problem on two different computing environments, so
> I'm convinced that the Maven version is not relevant.
> (It is unclear to me if this problem also existed with Javadoc 2.6, but I
> don't think so.)
--
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: (MSTAGE-14) DefaultRepositoryCopier rename script does not check move command exit codes
DefaultRepositoryCopier rename script does not check move command exit codes Key: MSTAGE-14 URL: http://jira.codehaus.org/browse/MSTAGE-14 Project: Maven 2.x Stage Plugin Issue Type: Improvement Affects Versions: 1.0-alpha-2 Reporter: Francis De Brabandere Only if the last move command fails will the plugin fail. This because the exit code for unix scipts is the one from the last command. Better would be to use something like this: #!/bin/sh touch test.txt \ && rm test.txt \ && rm test2.txt \ <- fails here and won't continue && touch test2.txt \ rm test2.txt this script will fail even if the last 2 commands would succeed (those will not even run) I know this failing is something that is not common but still possible. We actually had this issue and it took quite some time to find out why certain builds failed and others not (depended on what the last mv command was). -- 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: (MRELEASE-536) CommonBasedir Calculation fails on windows
[ http://jira.codehaus.org/browse/MRELEASE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229988#action_229988 ] Francis De Brabandere commented on MRELEASE-536: Might be a good idea to catch this -1 string index and throwing a proper exception indicating what goes wrong by showing both paths we have this problem with subversion-based projects being released in apache hudson [INFO] Working directory: c:\hudson\workspace\...\trunk > CommonBasedir Calculation fails on windows > -- > > Key: MRELEASE-536 > URL: http://jira.codehaus.org/browse/MRELEASE-536 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0 >Reporter: Matthias Vach > Attachments: patchfile.patch > > > The method getCommonBasedir in class > org.apache.maven.shared.release.util.ReleaseUtil runs into the Exception:\\ > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > ... while comparing pathes with small and capital lettes for Windows drives. > e.g.: C:\WoRkInG\root\project1 has no common base dir with > c:\working\root\project2\\ but it should have c:\working\root as common base > directory. > A patch and a test for that bug is attached. > I do have the problem with version 2.0 but I fixed it in trunk for now > Regards Matthias -- 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] Issue Comment Edited: (MRELEASE-536) CommonBasedir Calculation fails on windows
[ http://jira.codehaus.org/browse/MRELEASE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229988#action_229988 ] Francis De Brabandere edited comment on MRELEASE-536 at 7/27/10 11:32 AM: -- Might be a good idea to catch this -1 string index and throwing a proper exception indicating what goes wrong by showing both paths we have this problem with subversion-based projects being released in hudson [INFO] Working directory: c:\hudson\workspace\...\trunk was (Author: francisdb): Might be a good idea to catch this -1 string index and throwing a proper exception indicating what goes wrong by showing both paths we have this problem with subversion-based projects being released in apache hudson [INFO] Working directory: c:\hudson\workspace\...\trunk > CommonBasedir Calculation fails on windows > -- > > Key: MRELEASE-536 > URL: http://jira.codehaus.org/browse/MRELEASE-536 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0 >Reporter: Matthias Vach > Attachments: patchfile.patch > > > The method getCommonBasedir in class > org.apache.maven.shared.release.util.ReleaseUtil runs into the Exception:\\ > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > ... while comparing pathes with small and capital lettes for Windows drives. > e.g.: C:\WoRkInG\root\project1 has no common base dir with > c:\working\root\project2\\ but it should have c:\working\root as common base > directory. > A patch and a test for that bug is attached. > I do have the problem with version 2.0 but I fixed it in trunk for now > Regards Matthias -- 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: (MRELEASE-536) CommonBasedir Calculation fails on windows
[ http://jira.codehaus.org/browse/MRELEASE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229990#action_229990 ] Francis De Brabandere commented on MRELEASE-536: A workaround is to revert to the 2.0-beta-9 maven-release-plugin. > CommonBasedir Calculation fails on windows > -- > > Key: MRELEASE-536 > URL: http://jira.codehaus.org/browse/MRELEASE-536 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0 >Reporter: Matthias Vach > Attachments: patchfile.patch > > > The method getCommonBasedir in class > org.apache.maven.shared.release.util.ReleaseUtil runs into the Exception:\\ > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > ... while comparing pathes with small and capital lettes for Windows drives. > e.g.: C:\WoRkInG\root\project1 has no common base dir with > c:\working\root\project2\\ but it should have c:\working\root as common base > directory. > A patch and a test for that bug is attached. > I do have the problem with version 2.0 but I fixed it in trunk for now > Regards Matthias -- 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: (MRELEASE-536) CommonBasedir Calculation fails on windows
[ http://jira.codehaus.org/browse/MRELEASE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230329#action_230329 ] Francis De Brabandere commented on MRELEASE-536: here is a stacktrace: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1937) at org.apache.maven.shared.release.util.ReleaseUtil.getCommonBasedir(ReleaseUtil.java:206) at org.apache.maven.shared.release.util.ReleaseUtil.getCommonBasedir(ReleaseUtil.java:177) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformDocument(AbstractRewritePomsPhase.java:303) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:208) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:114) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.execute(AbstractRewritePomsPhase.java:97) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:203) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103) at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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) > CommonBasedir Calculation fails on windows > -- > > Key: MRELEASE-536 > URL: http://jira.codehaus.org/browse/MRELEASE-536 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0 >Reporter: Matthias Vach > Attachments: patchfile.patch > > > The method getCommonBasedir in class > org.apache.maven.shared.release.util.ReleaseUtil runs into the Exception:\\ > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > ... while comparing pathes with small and capital lettes for Windows drives. > e.g.: C:\WoRkInG\root\project1 has no common base dir with > c:\working\root\project2\\ but it should have c:\working\root as common base > directory. > A patch and a test for that bug is attached. > I do have the problem with version 2.0 but I fixed it in trunk for now > Regards Matthias -- 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-214) test javadoc goal uses incorrect dependency classpath
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190216#action_190216 ] Francis De Brabandere commented on MJAVADOC-214: I have seen this issue when you do a "mvn clean install" on a multimodule build where javadoc report aggregation is enabled. And this only after changing to a new version. (it's indicated in the logs that he does not seem to find snapshots) The fix was to do a "mvn clean install" first to get the snapshots in the local repo or to disable report generation. > test javadoc goal uses incorrect dependency classpath > - > > Key: MJAVADOC-214 > URL: http://jira.codehaus.org/browse/MJAVADOC-214 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Brett Porter > > according to this report: > http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19158787.html > The test javadoc goal is not using the test classpath dependencies. -- 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] Issue Comment Edited: (MJAVADOC-214) test javadoc goal uses incorrect dependency classpath
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190216#action_190216 ] Francis De Brabandere edited comment on MJAVADOC-214 at 9/8/09 7:17 AM: I have seen this issue when you do a "mvn clean install site" on a multimodule build where javadoc report aggregation is enabled. And this only after changing to a new version. (it's indicated in the logs that he does not seem to find snapshots) The fix was to do a "mvn clean install" first to get the snapshots in the local repo or to disable report generation. was (Author: francisdb): I have seen this issue when you do a "mvn clean install" on a multimodule build where javadoc report aggregation is enabled. And this only after changing to a new version. (it's indicated in the logs that he does not seem to find snapshots) The fix was to do a "mvn clean install" first to get the snapshots in the local repo or to disable report generation. > test javadoc goal uses incorrect dependency classpath > - > > Key: MJAVADOC-214 > URL: http://jira.codehaus.org/browse/MJAVADOC-214 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Brett Porter > > according to this report: > http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19158787.html > The test javadoc goal is not using the test classpath dependencies. -- 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-268) performance problem in AbstractJavadocMojo.getModulesLinks()
[ http://jira.codehaus.org/browse/MJAVADOC-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20#action_20 ] Francis De Brabandere commented on MJAVADOC-268: I seem to still have this problem with 2.6.1 > performance problem in AbstractJavadocMojo.getModulesLinks() > > > Key: MJAVADOC-268 > URL: http://jira.codehaus.org/browse/MJAVADOC-268 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.6 > Environment: Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200) > Java version: 1.6.0_13 > Java home: /home/mkleint/javatools/jdk1.6.0_13/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.29.6-desktop-2mnb" arch: "i386" Family: "unix" >Reporter: Milos Kleint >Assignee: Vincent Siveton >Priority: Critical > Fix For: 2.6.1 > > Attachments: javadoc.patch > > > The getModulesLinks() method is unacceptably slow under certain conditions: > 1. project's url is defined > 2. one or more projects in reactor do not have any java sources and are not > of "pom" packaging. > For such projects the apidocs/ output folder is never created resulting in > repeated invokation of a forked javadoc goal. It's more severe with high > number of modules in reactor and high number of modules without any java > sources. > as an example checkout "hg clone https://hg.kenai.com/hg/forceten~src"; > The immediate problem is in the apidocsFile.exists() condition that > re-triggers the forked invokation. The attached patch fixes that. However it > looks suspicitions that the method is being called repeatedly for each module > at all. Maybe the aborting condition at the start of the method body is wrong > (I was not able to decypher that) > workaround is to use 2.5 or not to specify the url in pom.xml or set the > detectOfflineLinks parameter 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
