[
http://jira.codehaus.org/browse/MNG-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-2693:
------------------------------
Fix Version/s: (was: Reviewed Pending Version Assignment)
3.0-alpha-3
may be fixed by now, needs review
> Error executing post-site: java.util.MissingResourceException: Can't find
> bundle for base name site-plugin, locale en
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-2693
> URL: http://jira.codehaus.org/browse/MNG-2693
> Project: Maven 2
> Issue Type: Bug
> Components: Sites & Reporting
> Affects Versions: 2.0-alpha-1
> Reporter: Stepan Roh
> Fix For: 3.0-alpha-3
>
>
> I use Maven 2.1 embedder - if I build it from current SVN HEAD of
> maven-components (together with all components), I get this exception if I
> try to execute post-site:
> Caused by: org.apache.maven.reactor.MavenExecutionException: Error executing
> project within the reactor
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:214)
> at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:797)
> ... 19 more
> Caused by: java.util.MissingResourceException: Can't find bundle for base
> name site-plugin, locale en
> at
> org.codehaus.plexus.i18n.DefaultI18N.cacheBundle(DefaultI18N.java:394)
> at org.codehaus.plexus.i18n.DefaultI18N.getBundle(DefaultI18N.java:157)
> at org.codehaus.plexus.i18n.DefaultI18N.getString(DefaultI18N.java:206)
> at
> org.apache.maven.plugins.site.AbstractSiteMojo.populateReportsMenu(AbstractSiteMojo.java:400)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.locateDocuments(AbstractSiteRenderingMojo.java:587)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:438)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:391)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:178)
> ... 21 more
> If I try revision 480835, it works. I see that there are some classworlds and
> container changes since that revision, so it can be related to that.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
