[ 
http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137280#action_137280
 ] 

Michael Stevens commented on MSITE-332:
---------------------------------------

I did indeed try that.. I tried several previous beta versions of the site 
plugin and the project info plugin. But, regardless of the site plugin version 
beta-1 through beta-6, and the project info plugin version 2.0 or 2.0.1, I 
either saw the doxia/logging classpath problem, or another complicated error 
message I didn't want to dig into (sorry).

What I am seeing is that when the dependency for 
org.apache.maven.doxia:doxia-logging-api:1.0-beta-1-SNAPSHOT is resolved, maven 
doesn't seem to care about the jar file, only the pom.

If I remove doxia-logging-api artifacts from my local repository, only the pom 
is retrieved (e.g. doxia-logging-api-1.0-beta-1-20080531.193054-6.pom), not the 
jar file (doxia-logging-api-1.0-beta-1-20080531.193054-6.jar). Even if I 
manually put the matching snapshot jar in place with the downloaded pom in my 
repo, the NoClassDef problem still occurs.

Assuming no one else can reproduce the problem (it occurs with a generic 
project created with the archetype:create goal), I'm guessing there's something 
weird happening in my environment. 

> Unable to load parent project from a relative path: Could not find the model 
> file '<dir>/pom.xml'. for project unknown
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: MSITE-332
>                 URL: http://jira.codehaus.org/browse/MSITE-332
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>          Components: site descriptor
>    Affects Versions: 2.0-beta-7
>            Reporter: Michael Stevens
>            Assignee: Dennis Lundberg
>             Fix For: 2.0-beta-7
>
>
> Execute site:site
> The plugin seems to look for a pom file in the directory above the project 
> directory.
> This started occurring last night for us, using 
> maven-site-plugin:2.0-beta-7-SNAPSHOT.
> Note that the project in question uses a parent POM, but does not specify a 
> relative path.
> Here is the stack trace:
> [INFO] Unable to load parent project from a relative path: Could not find the 
> model file 'c:\workdir\projects\pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] SiteToolException: Error reading default site descriptor: 
> ${OUTPUTENCODING}
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: SiteToolException: 
> Error reading default site descriptor: ${OUTPUTENCODING}
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>         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:585)
>         at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: SiteToolException: 
> Error reading default site descriptor: ${OUTPUTENCODING}
>         at 
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:230)
>         at 
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
>         at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>         ... 16 more
> Caused by: org.apache.maven.doxia.tools.SiteToolException: Error reading 
> default site descriptor: ${OUTPUTENCODING}
>         at 
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:527)
>         at 
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226)
>         ... 20 more
> Caused by: java.io.UnsupportedEncodingException: ${OUTPUTENCODING}
>         at sun.io.Converters.getConverterClass(Converters.java:218)
>         at sun.io.Converters.newConverter(Converters.java:251)
>         at 
> sun.io.ByteToCharConverter.getConverter(ByteToCharConverter.java:68)
>         at sun.nio.cs.StreamDecoder$ConverterSD.<init>(StreamDecoder.java:224)
>         at sun.nio.cs.StreamDecoder$ConverterSD.<init>(StreamDecoder.java:210)
>         at 
> sun.nio.cs.StreamDecoder.forInputStreamReader(StreamDecoder.java:77)
>         at java.io.InputStreamReader.<init>(InputStreamReader.java:83)
>         at 
> org.codehaus.plexus.util.xml.XmlReader.prepareReader(XmlReader.java:483)
>         at 
> org.codehaus.plexus.util.xml.XmlReader.doRawStream(XmlReader.java:466)
>         at org.codehaus.plexus.util.xml.XmlReader.<init>(XmlReader.java:183)
>         at org.codehaus.plexus.util.xml.XmlReader.<init>(XmlReader.java:146)
>         at 
> org.codehaus.plexus.util.xml.XmlStreamReader.<init>(XmlStreamReader.java:90)
>         at 
> org.codehaus.plexus.util.ReaderFactory.newXmlReader(ReaderFactory.java:104)
>         at 
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:522)
>         ... 21 more

-- 
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

        

Reply via email to