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/01 22:21:24 UTC
[jira] Closed: (MAVEN-1352) empty plugin directory causes uninformative exception to be printed.
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Thu, 1 Jul 2004 4:20 PM
Fixed.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1352
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1352
Summary: empty plugin directory causes uninformative exception to be printed.
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.0
Versions:
1.0-rc4
Assignee: Brett Porter
Reporter: Patrick Moore
Created: Tue, 29 Jun 2004 8:01 PM
Updated: Thu, 1 Jul 2004 4:20 PM
Environment: Debian Linux (sarge release)
java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
Description:
I had a build.properties in my home directory that set:
maven.plugin.dir=/usr/local/maven-storage/plugin
/usr/local/maven-storage/plugin is empty. Because (?) it is empty maven crashes with this useless exception. (Note that 'maven --info' also crashes when run.):
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc4
java.lang.UnsupportedOperationException
at java.util.AbstractMap.put(AbstractMap.java:227)
at java.util.AbstractMap.putAll(AbstractMap.java:316)
at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:244)
at org.apache.maven.MavenSession.initializePluginManager(MavenSession.java:207)
at org.apache.maven.MavenSession.initialize(MavenSession.java:174)
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)
You have encountered an unknown error running Maven. Please help us to correct
this problem by following these simple steps:
- read the Maven FAQ at http://maven.apache.org/faq.html
- run the same command again with the '-e' parameter, eg maven -e jar
- search the maven-user archives for the error at
http://nagoya.apache.org/eyebrowse/SummarizeList?listName=users@maven.apache.org
- post the output of maven -e to JIRA at
http://jira.codehaus.org/BrowseProject.jspa?id=10030 (you must sign up first)
- run 'maven --info' and post the output as the environment to the bug above
---------------------------------------------------------------------
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