[jira] Commented: (MRELEASE-481) prepare goal no longer errors on subversion files
[ http://jira.codehaus.org/browse/MRELEASE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192452#action_192452 ] Robert Scholte commented on MRELEASE-481: - Arnaud, The problem occurs with a new and uncommitted file. It's not about files being modified (at least, that's what your logs are telling me). > prepare goal no longer errors on subversion files > --- > > Key: MRELEASE-481 > URL: http://jira.codehaus.org/browse/MRELEASE-481 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-8 >Reporter: Paul Hammant > Fix For: 2.0-beta-10 > > > Snow Leopard / Maven 2.2.0 / Svn 1.6.3 (via macports) > release:prepare used to error telling you that you had files not checked in. > It no longer does, or no longer does by default :-( > -ph -- 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: (MPH-70) Maven Help Plugin prints an Exception Stack Trace: NoSuchMethodError on execution
[
http://jira.codehaus.org/browse/MPH-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MPH-70.
Assignee: Benjamin Bentmann
Resolution: Cannot Reproduce
I could not reproduce this with any of the released plugin versions. The fact
that DescribeMojo.java:930 and DescribeMojo.java:969 don't match against
released sources makes we think you were running either a custom build of the
plugin or some buggy snapshot (head seems OK).
> Maven Help Plugin prints an Exception Stack Trace: NoSuchMethodError on
> execution
> -
>
> Key: MPH-70
> URL: http://jira.codehaus.org/browse/MPH-70
> Project: Maven 2.x Help Plugin
> Issue Type: Bug
>Reporter: Tim O'Brien
>Assignee: Benjamin Bentmann
>
> I just tried to run the Help plugin
> Here is my Maven version info:
> Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500)
> Java version: 1.6.0_15
> Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x" version: "10.6.1" arch: "x86_64" Family: "mac"
> Here is the error output:
> ~/book$ mvn help:describe -Dplugin=scm -e
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Maven: The Definitive Guide Example Code
> [INFO] Maven: The Definitive Guide (Parent Project)
> [INFO] Maven: The Definitive Guide (XML, HTML, PDF, and Site)
> [INFO] Searching repository for plugin with prefix: 'help'.
> [INFO]
>
> [INFO] Building Maven: The Definitive Guide (Parent Project)
> [INFO]task-segment: [help:describe] (aggregator-style)
> [INFO]
>
> [INFO] [help:describe {execution: default-cli}]
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] NoSuchMethodException:
> org.apache.maven.plugins.help.HelpMojo.toLines(java.lang.String, int, int,
> int)
> [INFO]
>
> [INFO] Trace
> org.apache.maven.BuildFailureException: NoSuchMethodException:
> org.apache.maven.plugins.help.HelpMojo.toLines(java.lang.String, int, int,
> int)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
> 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)
> Caused by: org.apache.maven.plugin.MojoFailureException:
> NoSuchMethodException:
> org.apache.maven.plugins.help.HelpMojo.toLines(java.lang.String, int, int,
> int)
> at
> org.apache.maven.plugins.help.DescribeMojo.toLines(DescribeMojo.java:930)
> at
> org.apache.maven.plugins.help.DescribeMojo.append(DescribeMojo.java:969)
> at
> org.apache.maven.plugins.help.DescribeMojo.describePlugin(DescribeMojo.java:515)
> at
> org.apache.maven.plugins.help.DescribeMojo.execute(DescribeMojo.java:268)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>
[jira] Closed: (MDOAP-22) Documentation regarding site-integration hrefs wrong file
[
http://jira.codehaus.org/browse/MDOAP-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MDOAP-22.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 1.1
Applied in [r819347|http://svn.apache.org/viewvc?view=rev&revision=819347],
thanks!
Your patch refers to some non-existent/renamed file, so as a general advice,
please always patch the trunk.
> Documentation regarding site-integration hrefs wrong file
> -
>
> Key: MDOAP-22
> URL: http://jira.codehaus.org/browse/MDOAP-22
> Project: Maven 2.x DOAP Plugin
> Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Sebastian Hoß
>Assignee: Benjamin Bentmann
>Priority: Trivial
> Fix For: 1.1
>
> Attachments: maven-doap-plugin - site-integration.patch
>
>
> The documentation related to the [site
> integration|http://maven.apache.org/plugins/maven-doap-plugin/examples/with-site-plugin.html]
> hrefs to "${project.url}/doap_*maven-doap-plugin*.rdf" but that should read
> "${project.url}/doap_*${project.artifactId}*.rdf" as that is the default
> value for the
> [doap:generate|http://maven.apache.org/plugins/maven-doap-plugin/generate-mojo.html]
> goal.
> The attached patch corrects this problem.
--
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: (MDOAP-23) Plugin assumes that both and are always specified
[
http://jira.codehaus.org/browse/MDOAP-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MDOAP-23.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 1.1
Applied in [r819360|http://svn.apache.org/viewvc?view=rev&revision=819360],
thanks!
Same comment, please provide patches against the head revision, otherwise your
patch is more likely to be non-applicable due to recent commits on the code
base.
> Plugin assumes that both and are always
> specified
>
>
> Key: MDOAP-23
> URL: http://jira.codehaus.org/browse/MDOAP-23
> Project: Maven 2.x DOAP Plugin
> Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Sebastian Hoß
>Assignee: Benjamin Bentmann
> Fix For: 1.1
>
> Attachments: maven-doap-plugin - scm connection.patch
>
>
> While trying out the DOAP plugin I ran into the following NPE:
> [INFO] [doap:generate {execution: site}]
> [INFO] Generating a pure DOAP file...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.plugin.doap.DoapMojo.writeSourceRepository(DoapMojo.java:1062)
> at
> org.apache.maven.plugin.doap.DoapMojo.writeSourceRepositories(DoapMojo.java:1009)
> at
> org.apache.maven.plugin.doap.DoapMojo.execute(DoapMojo.java:378)
> ...
> The _writeSourceRepositories_ method assumes that both the anonymous
> and the are specified. If they are not the
> follow-up method (_writeSourceRepository_) will throw a NullPointerException
> while trying to do compute *connection.length() < 4*
> The attached patch corrects this inside the _writeSourceRespositories_ method
> by checking if those connections are really specified. Only if they are the
> follow-up method is called.
--
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: (MDOAP-22) Documentation regarding site-integration hrefs wrong file
[
http://jira.codehaus.org/browse/MDOAP-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192514#action_192514
]
Sebastian Hoß commented on MDOAP-22:
Ah sorry, I picked the 1.0 tag out of laziness. Will do better next time!
> Documentation regarding site-integration hrefs wrong file
> -
>
> Key: MDOAP-22
> URL: http://jira.codehaus.org/browse/MDOAP-22
> Project: Maven 2.x DOAP Plugin
> Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Sebastian Hoß
>Assignee: Benjamin Bentmann
>Priority: Trivial
> Fix For: 1.1
>
> Attachments: maven-doap-plugin - site-integration.patch
>
>
> The documentation related to the [site
> integration|http://maven.apache.org/plugins/maven-doap-plugin/examples/with-site-plugin.html]
> hrefs to "${project.url}/doap_*maven-doap-plugin*.rdf" but that should read
> "${project.url}/doap_*${project.artifactId}*.rdf" as that is the default
> value for the
> [doap:generate|http://maven.apache.org/plugins/maven-doap-plugin/generate-mojo.html]
> goal.
> The attached patch corrects this problem.
--
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
