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/07/19 14:26:39 UTC
[jira] Created: (MAVEN-1380) MavenUtils eat the parsing error exception
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1380
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1380
Summary: MavenUtils eat the parsing error exception
Type: Improvement
Status: Unassigned
Priority: Critical
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Versions:
1.0
Assignee:
Reporter: Julien Kirch
Created: Mon, 19 Jul 2004 8:26 AM
Updated: Mon, 19 Jul 2004 8:26 AM
Environment: Maven 1.0 Window NT4
Description:
I have a (probably) malformed project.xml and maven gave me an :
org.apache.maven.MavenException: Error parsing project.xml 'C:\XXXXXXXXXXXXXXXXXXXXXX\project.xml'
at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123)
at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235)
at org.apache.maven.MavenSession.initialize(MavenSession.java:175)
at org.apache.maven.cli.App.doMain(App.java:473)
at org.apache.maven.cli.App.main(App.java:1215)
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:324)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
which doesn't help me much, because MavenUtils eat the original Exception (MavenUtils l 208) :
try
{
project = (Project) getProjectBeanReader().parse( projectDescriptor );
}
catch (Exception e)
{
throw new MavenException("Error parsing project.xml '" + projectDescriptor.getAbsolutePath() + "'", e);
}
IWBNI the original exception were passed as a parameter in the MavenException so it would be displayed in the stacktrace.
---------------------------------------------------------------------
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
[jira] Commented: (MAVEN-1380) MavenUtils eat the parsing error exception
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Brett Porter
Created: Tue, 21 Sep 2004 10:19 AM
Body:
1.0.1 has not yet been released.
You can build it from CVS if necessary.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1380?page=comments#action_24308
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1380
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1380
Summary: MavenUtils eat the parsing error exception
Type: Improvement
Status: Closed
Priority: Critical
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Fix Fors:
1.0.1
Versions:
1.0
Assignee: Vincent Massol
Reporter: Julien Kirch
Created: Mon, 19 Jul 2004 8:26 AM
Updated: Tue, 21 Sep 2004 10:19 AM
Environment: Maven 1.0 Window NT4
Description:
I have a (probably) malformed project.xml and maven gave me an :
org.apache.maven.MavenException: Error parsing project.xml 'C:\XXXXXXXXXXXXXXXXXXXXXX\project.xml'
at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123)
at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235)
at org.apache.maven.MavenSession.initialize(MavenSession.java:175)
at org.apache.maven.cli.App.doMain(App.java:473)
at org.apache.maven.cli.App.main(App.java:1215)
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:324)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
which doesn't help me much, because MavenUtils eat the original Exception (MavenUtils l 208) :
try
{
project = (Project) getProjectBeanReader().parse( projectDescriptor );
}
catch (Exception e)
{
throw new MavenException("Error parsing project.xml '" + projectDescriptor.getAbsolutePath() + "'", e);
}
IWBNI the original exception were passed as a parameter in the MavenException so it would be displayed in the stacktrace.
---------------------------------------------------------------------
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
[jira] Closed: (MAVEN-1380) MavenUtils eat the parsing error exception
Posted by ji...@codehaus.org.
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Mon, 19 Jul 2004 9:50 AM
Done.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1380
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1380
Summary: MavenUtils eat the parsing error exception
Type: Improvement
Status: Closed
Priority: Critical
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Fix Fors:
1.0.1
Versions:
1.0
Assignee: Vincent Massol
Reporter: Julien Kirch
Created: Mon, 19 Jul 2004 8:26 AM
Updated: Mon, 19 Jul 2004 9:50 AM
Environment: Maven 1.0 Window NT4
Description:
I have a (probably) malformed project.xml and maven gave me an :
org.apache.maven.MavenException: Error parsing project.xml 'C:\XXXXXXXXXXXXXXXXXXXXXX\project.xml'
at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123)
at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235)
at org.apache.maven.MavenSession.initialize(MavenSession.java:175)
at org.apache.maven.cli.App.doMain(App.java:473)
at org.apache.maven.cli.App.main(App.java:1215)
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:324)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
which doesn't help me much, because MavenUtils eat the original Exception (MavenUtils l 208) :
try
{
project = (Project) getProjectBeanReader().parse( projectDescriptor );
}
catch (Exception e)
{
throw new MavenException("Error parsing project.xml '" + projectDescriptor.getAbsolutePath() + "'", e);
}
IWBNI the original exception were passed as a parameter in the MavenException so it would be displayed in the stacktrace.
---------------------------------------------------------------------
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
[jira] Commented: (MAVEN-1380) MavenUtils eat the parsing error exception
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Rupam
Created: Tue, 21 Sep 2004 10:10 AM
Body:
Can anyone give a pointer to the downloads for this fix ?
Thanks in Advance
Rupam
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1380?page=comments#action_24307
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1380
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1380
Summary: MavenUtils eat the parsing error exception
Type: Improvement
Status: Closed
Priority: Critical
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Fix Fors:
1.0.1
Versions:
1.0
Assignee: Vincent Massol
Reporter: Julien Kirch
Created: Mon, 19 Jul 2004 8:26 AM
Updated: Tue, 21 Sep 2004 10:10 AM
Environment: Maven 1.0 Window NT4
Description:
I have a (probably) malformed project.xml and maven gave me an :
org.apache.maven.MavenException: Error parsing project.xml 'C:\XXXXXXXXXXXXXXXXXXXXXX\project.xml'
at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123)
at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235)
at org.apache.maven.MavenSession.initialize(MavenSession.java:175)
at org.apache.maven.cli.App.doMain(App.java:473)
at org.apache.maven.cli.App.main(App.java:1215)
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:324)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
which doesn't help me much, because MavenUtils eat the original Exception (MavenUtils l 208) :
try
{
project = (Project) getProjectBeanReader().parse( projectDescriptor );
}
catch (Exception e)
{
throw new MavenException("Error parsing project.xml '" + projectDescriptor.getAbsolutePath() + "'", e);
}
IWBNI the original exception were passed as a parameter in the MavenException so it would be displayed in the stacktrace.
---------------------------------------------------------------------
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