You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Aaron Digulla <di...@hepe.com> on 2008/04/14 15:55:29 UTC

java.lang.IllegalStateException: The PluginDescriptor for the plugin ... was not found (Was: Re: problem with site-plugin 2.0-beta-6)

Quoting Aaron Digulla <di...@hepe.com>:

After an epiphany, I found the problem: A corrupt JAR file in the  
repository. I've opened http://jira.codehaus.org/browse/MNG-3523

>> The bug is still there in 2.0.9. I've downloaded the source and the bug
>> lurks in this code:
>>
>> MavenPluginCollector.java:
>>
>>    public PluginDescriptor getPluginDescriptor( Plugin plugin )
>>    {
>>        // TODO: include version, but can't do this in the plugin
>> manager as it is not resolved to the right version
>>        // at that point. Instead, move the duplication check to the
>> artifact container, or store it locally based on
>>        // the unresolved version?
>>        return (PluginDescriptor) pluginDescriptors.get( plugin.getKey() );
>>    }
>>
>> Obviously, the plugin isn't in pluginDescriptors. Why not? It seems
>> that the component is not discovered but if that was the case, then why
>> would maven try to invoke it??
>
> After some more time spent on this, I've added debug output to
> MavenPluginCollector. I had to debug with getLogger().info() because it
> seems that the debug level is not set when this code is called. :(
>
> What I found is that after the POMs for the site plugin have been read,
> I get a ComponentDescriptor event with an
> "org.apache.maven.usability.diagnostics.ErrorDiagnoser" entry. This
> seems to indicate that something went wrong during the loading of the
> site plugin but the error handling has a bug and the error message was
> lost.
>
> Any hints where I can look now? I'm pretty sure that one of the
> artifacts in my repository or the proxy is broken but I'd rather find
> out which one instead of downloading 1.27GB again...
>
>>
>>> Aaron Digulla schrieb:
>>>> Brian E. Fox schrieb:
>>>>
>>>>> I think it's safer to leave it at beta-6. Most people aren't     
>>>>> expressing any issues and if anyone has trouble, they can    
>>>>> manually lock to beta-5. This is safer than potentially    
>>>>> downgrading everyone.
>>>>
>>>> beta-6 doesn't work for me at all. I suddenly get:
>>>>
>>>> java.lang.IllegalStateException: The PluginDescriptor for the plugin
>>>> Plugin [org.apache.maven.plugins:maven-site-plugin] was not found
>>>>
>>>> This error is definitely not true; I can see the file on disk and maven
>>>> can read it (I can see that it resolves parent POMs from it in the debug
>>>> log).
>>>
>>> Here is the output from the log:
>>>
>>> [DEBUG] maven-site-plugin: resolved to version 2.0-beta-6 from
>>> repository central
>>> [DEBUG] Retrieving parent-POM:
>>> org.apache.maven.plugins:maven-plugins::10 for project:
>>> null:maven-site-plugin:maven-plugin:2.0-beta-6 from the repository.
>>> [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::7 for
>>> project: org.apache.maven.plugins:maven-plugins:pom:10 from the repository.
>>> [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project:
>>> org.apache.maven:maven-parent:pom:7 from the repository.
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] FATAL ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] The PluginDescriptor for the plugin Plugin
>>> [org.apache.maven.plugins:maven-site-plugin] was not found.
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [DEBUG] Trace
>>> java.lang.IllegalStateException: The PluginDescriptor for the plugin
>>> Plugin [org.apache.maven.plugins:maven-site-plugin] was not found.
>>>       at
>>> org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:321)
>>>       at
>>> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:208)
>>> [code]
>>>
>>> As you can see, the plugin exists and the POM could be loaded. So what
>>> is wrong in this case?
>>>
>>> --
>>> Aaron "Optimizer" Digulla a.k.a. Philmann Dark
>>> "It's not the universe that's limited, it's our imagination.
>>> Follow me and I'll show you something beyond the limits."
>>> http://darkviews.blogspot.com/          http://www.pdark.de/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>>
>>
>>
>>
>> -- 
>> Aaron "Optimizer" Digulla a.k.a. Philmann Dark
>> "It's not the universe that's limited, it's our imagination.
>> Follow me and I'll show you something beyond the limits."
>> http://www.pdark.de/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> -- 
> Aaron "Optimizer" Digulla a.k.a. Philmann Dark
> "It's not the universe that's limited, it's our imagination.
> Follow me and I'll show you something beyond the limits."
> http://www.pdark.de/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org



-- 
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://www.pdark.de/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org