You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by bo...@werken.com on 2003/03/12 04:28:01 UTC
[maven-bug] Updated: (MAVEN-330) maven running in a directory that has not a project.XML crashes
The following issue has been updated:
Updater: Paulo Silveira (mailto:paulo@paulo.com.br)
Date: Tue, 11 Mar 2003 9:28 PM
Comment:
ok, this is the issue:
project.getContext().getWerkzProject() returns null at PluginManager when there is no project.xml (makes sense). So I verify in the same IF clause which checks the goals.size() == 0, and now if there is no project.xml, it simply "builds successful"
this patch is just to see the problem, a real patch should return a new error code? NO_PROJECT_FILE or sth like that, and should verify this before.
Changes:
[Attachment] [patchWorkaround.txt] was added
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-330&page=history
---------------------------------------------------------------------
View the issue:
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-330
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-330
Summary: maven running in a directory that has not a project.XML crashes
Type: Bug
Status: Assigned
Priority: Major
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Component: core
Versions:
1.0-beta-9
Assignee: Jason van Zyl
Reporter: Paulo Silveira
Created: Tue, 11 Mar 2003 8:18 PM
Updated: Tue, 11 Mar 2003 9:28 PM
Environment: 1.0beta9 snapshot, java 1.4, java 1.3. its a null pointer, probably the env does not metter
Description:
$ maven
__ __
| \/ |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9-SNAPSHOT
java.lang.NullPointerException
at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:
362)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
at org.apache.maven.cli.App.doMain(App.java:524)
at org.apache.maven.cli.App.main(App.java:1080)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.werken.forehead.Forehead.run(Forehead.java:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
Total time: 0 seconds
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.werken.com/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Re: [maven-bug] Updated: (MAVEN-330) maven running in a directory
that has not a project.XML crashes
Posted by Jason van Zyl <ja...@zenplex.com>.
On Tue, 2003-03-11 at 22:28, bob@werken.com wrote:
> The following issue has been updated:
>
> Updater: Paulo Silveira (mailto:paulo@paulo.com.br)
> Date: Tue, 11 Mar 2003 9:28 PM
> Comment:
> ok, this is the issue:
>
> project.getContext().getWerkzProject() returns null at PluginManager when there is no project.xml (makes sense). So I verify in the same IF clause which checks the goals.size() == 0, and now if there is no project.xml, it simply "builds successful"
> this patch is just to see the problem, a real patch should return a new error code? NO_PROJECT_FILE or sth like that, and should verify this before.
> Changes:
> [Attachment] [patchWorkaround.txt] was added
>
Already fixed in the branch I'm working on.
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
Re: [maven-bug] Updated: (MAVEN-330) maven running in a directory
that has not a project.XML crashes
Posted by Jason van Zyl <ja...@zenplex.com>.
On Tue, 2003-03-11 at 22:46, Ben Walding wrote:
> Probably want to check CVS HEAD, Jason mentioned that he fixed this in
> the last few days.
Fixed as part of classworlds refactoring.
> bob@werken.com wrote:
>
> >The following issue has been updated:
> >
> > Updater: Paulo Silveira (mailto:paulo@paulo.com.br)
> > Date: Tue, 11 Mar 2003 9:28 PM
> > Comment:
> >ok, this is the issue:
> >
> >project.getContext().getWerkzProject() returns null at PluginManager when there is no project.xml (makes sense). So I verify in the same IF clause which checks the goals.size() == 0, and now if there is no project.xml, it simply "builds successful"
> >this patch is just to see the problem, a real patch should return a new error code? NO_PROJECT_FILE or sth like that, and should verify this before.
> > Changes:
> >[Attachment] [patchWorkaround.txt] was added
> >
> >---------------------------------------------------------------------
> >For a full history of the issue, see:
> >
> > http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-330&page=history
> >
> >---------------------------------------------------------------------
> >View the issue:
> >
> > http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-330
> >
> >
> >Here is an overview of the issue:
> >---------------------------------------------------------------------
> > Key: MAVEN-330
> > Summary: maven running in a directory that has not a project.XML crashes
> > Type: Bug
> >
> > Status: Assigned
> > Priority: Major
> >
> > Time Spent: Unknown
> > Estimate: 0 minutes
> >
> > Project: maven
> > Component: core
> > Versions:
> > 1.0-beta-9
> >
> > Assignee: Jason van Zyl
> > Reporter: Paulo Silveira
> >
> > Created: Tue, 11 Mar 2003 8:18 PM
> > Updated: Tue, 11 Mar 2003 9:28 PM
> >Environment: 1.0beta9 snapshot, java 1.4, java 1.3. its a null pointer, probably the env does not metter
> >
> >Description:
> >$ maven
> > __ __
> >| \/ |__ Jakarta _ ___
> >| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> >|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9-SNAPSHOT
> >
> >
> >java.lang.NullPointerException
> > at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:
> >362)
> > at org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
> > at org.apache.maven.cli.App.doMain(App.java:524)
> > at org.apache.maven.cli.App.main(App.java:1080)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >java:39)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >sorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:324)
> > at com.werken.forehead.Forehead.run(Forehead.java:543)
> > at com.werken.forehead.Forehead.main(Forehead.java:573)
> >Total time: 0 seconds
> >
> >
> >
> >---------------------------------------------------------------------
> >JIRA INFORMATION:
> >This message is automatically generated by JIRA.
> >
> >If you think it was sent incorrectly contact one of the administrators:
> > http://jira.werken.com/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: turbine-maven-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: turbine-maven-dev-help@jakarta.apache.org
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-maven-dev-help@jakarta.apache.org
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
Re: [maven-bug] Updated: (MAVEN-330) maven running in a directory that has
not a project.XML crashes
Posted by di...@multitask.com.au.
He mentioned he fixed his code @ home, not HEAD.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
Ben Walding <be...@walding.com> wrote on 12/03/2003 02:46:42 PM:
> Probably want to check CVS HEAD, Jason mentioned that he fixed this in
> the last few days.
>
> bob@werken.com wrote:
>
> >The following issue has been updated:
> >
> > Updater: Paulo Silveira (mailto:paulo@paulo.com.br)
> > Date: Tue, 11 Mar 2003 9:28 PM
> > Comment:
> >ok, this is the issue:
> >
> >project.getContext().getWerkzProject() returns null at PluginManager
> when there is no project.xml (makes sense). So I verify in the same IF
> clause which checks the goals.size() == 0, and now if there is no
> project.xml, it simply "builds successful"
> >this patch is just to see the problem, a real patch should return a
> new error code? NO_PROJECT_FILE or sth like that, and should verify this
before.
> > Changes:
> >[Attachment] [patchWorkaround.txt] was added
> >
> >---------------------------------------------------------------------
> >For a full history of the issue, see:
> >
> >
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-330&page=history
> >
> >---------------------------------------------------------------------
> >View the issue:
> >
> > http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-330
> >
> >
> >Here is an overview of the issue:
> >---------------------------------------------------------------------
> > Key: MAVEN-330
> > Summary: maven running in a directory that has not a project.XML
crashes
> > Type: Bug
> >
> > Status: Assigned
> > Priority: Major
> >
> > Time Spent: Unknown
> > Estimate: 0 minutes
> >
> > Project: maven
> > Component: core
> > Versions:
> > 1.0-beta-9
> >
> > Assignee: Jason van Zyl
> > Reporter: Paulo Silveira
> >
> > Created: Tue, 11 Mar 2003 8:18 PM
> > Updated: Tue, 11 Mar 2003 9:28 PM
> >Environment: 1.0beta9 snapshot, java 1.4, java 1.3. its a null
> pointer, probably the env does not metter
> >
> >Description:
> >$ maven
> > __ __
> >| \/ |__ Jakarta _ ___
> >| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> >|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9-SNAPSHOT
> >
> >
> >java.lang.NullPointerException
> > at org.apache.maven.plugin.PluginManager.
> attainGoals(PluginManager.java:
> >362)
> > at
org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
> > at org.apache.maven.cli.App.doMain(App.java:524)
> > at org.apache.maven.cli.App.main(App.java:1080)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.
> invoke(NativeMethodAccessorImpl.
> >java:39)
> > at sun.reflect.DelegatingMethodAccessorImpl.
> invoke(DelegatingMethodAcces
> >sorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:324)
> > at com.werken.forehead.Forehead.run(Forehead.java:543)
> > at com.werken.forehead.Forehead.main(Forehead.java:573)
> >Total time: 0 seconds
> >
> >
> >
> >---------------------------------------------------------------------
> >JIRA INFORMATION:
> >This message is automatically generated by JIRA.
> >
> >If you think it was sent incorrectly contact one of the administrators:
> > http://jira.werken.com/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:
turbine-maven-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail:
turbine-maven-dev-help@jakarta.apache.org
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-maven-dev-help@jakarta.apache.org
>
Re: [maven-bug] Updated: (MAVEN-330) maven running in a directory
that has not a project.XML crashes
Posted by Ben Walding <be...@walding.com>.
Probably want to check CVS HEAD, Jason mentioned that he fixed this in
the last few days.
bob@werken.com wrote:
>The following issue has been updated:
>
> Updater: Paulo Silveira (mailto:paulo@paulo.com.br)
> Date: Tue, 11 Mar 2003 9:28 PM
> Comment:
>ok, this is the issue:
>
>project.getContext().getWerkzProject() returns null at PluginManager when there is no project.xml (makes sense). So I verify in the same IF clause which checks the goals.size() == 0, and now if there is no project.xml, it simply "builds successful"
>this patch is just to see the problem, a real patch should return a new error code? NO_PROJECT_FILE or sth like that, and should verify this before.
> Changes:
>[Attachment] [patchWorkaround.txt] was added
>
>---------------------------------------------------------------------
>For a full history of the issue, see:
>
> http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-330&page=history
>
>---------------------------------------------------------------------
>View the issue:
>
> http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-330
>
>
>Here is an overview of the issue:
>---------------------------------------------------------------------
> Key: MAVEN-330
> Summary: maven running in a directory that has not a project.XML crashes
> Type: Bug
>
> Status: Assigned
> Priority: Major
>
> Time Spent: Unknown
> Estimate: 0 minutes
>
> Project: maven
> Component: core
> Versions:
> 1.0-beta-9
>
> Assignee: Jason van Zyl
> Reporter: Paulo Silveira
>
> Created: Tue, 11 Mar 2003 8:18 PM
> Updated: Tue, 11 Mar 2003 9:28 PM
>Environment: 1.0beta9 snapshot, java 1.4, java 1.3. its a null pointer, probably the env does not metter
>
>Description:
>$ maven
> __ __
>| \/ |__ Jakarta _ ___
>| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
>|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9-SNAPSHOT
>
>
>java.lang.NullPointerException
> at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:
>362)
> at org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
> at org.apache.maven.cli.App.doMain(App.java:524)
> at org.apache.maven.cli.App.main(App.java:1080)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at com.werken.forehead.Forehead.run(Forehead.java:543)
> at com.werken.forehead.Forehead.main(Forehead.java:573)
>Total time: 0 seconds
>
>
>
>---------------------------------------------------------------------
>JIRA INFORMATION:
>This message is automatically generated by JIRA.
>
>If you think it was sent incorrectly contact one of the administrators:
> http://jira.werken.com/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: turbine-maven-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-maven-dev-help@jakarta.apache.org
>
>
>
>