You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/09/02 16:46:08 UTC
[jira] Commented: (MAVEN-1433) maven should indicate which Jelly file is failing
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Thu, 2 Sep 2004 10:44 AM
Body:
You can obtain it with maven -X or maven -e
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1433?page=comments#action_23727
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1433
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1433
Summary: maven should indicate which Jelly file is failing
Type: Improvement
Status: Open
Priority: Minor
Original Estimate: 30 minutes
Time Spent: Unknown
Remaining: 30 minutes
Project: maven
Components:
plugin manager
Fix Fors:
1.0.1
Versions:
1.0
Assignee: Felipe Leme
Reporter: Felipe Leme
Created: Thu, 2 Sep 2004 10:36 AM
Updated: Thu, 2 Sep 2004 10:44 AM
Description:
It's commong (at least to me :-) to screw-up a plugin.jelly somewhere and not being able to discover where:
$ rm -rf ~/.maven/cache
$ maven plugin:install
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0
Plugin cache will be regenerated
Fatal Error [line 43, row 3]: The element type "goal" must be terminated by the
matching end-tag "</goal>".
org.apache.maven.MavenException: Error parsing plugin script
at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j
ava:165)
at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j
ava:177)
at org.apache.maven.plugin.PluginManager.readMavenXml(PluginManager.java
:479)
at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:
551)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266)
at org.apache.maven.cli.App.doMain(App.java:486)
at org.apache.maven.cli.App.main(App.java:1215)
at java.lang.reflect.Method.invoke(Native Method)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
--- Nested Exception ---
So, it would help a lot if the message included which file generated that exception, instead of only the line and column (Fatal Error [line 43, row 3]).
I will try to fix it and submit a patch (as this is an issue on Maven Core).
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org