I'm so relieved to hear that other have the same issue building maven from CVS. I had no luck understanding which maven and maven-plugins to checkout to get the whole thing building shamelessly. As a matter of fact I took a cvs snapshot from feb 9 for both project (HEAD branch), and eventually managed to build maven without error.
When building the latest MAVEN_1.0-BRANCH The error I'm getting is somewhat different that yours (with a very strange Caused by: java.net.UnknownHostException: Users if you keep looking below):
[exec] Validating maven-reports.html
[exec] Validating project-info.html
[exec] Validating team-list.html
[exec] [echo] Generating /Users/Shared/Projects/third_party/maven_cvs/maven-plugins/html2xdoc/ src/plugin-test/target/docs/linkcheck.html from /Users/Shared/Projects/third_party/maven_cvs/maven-plugins/html2xdoc/ src/plugin-test/target/linkcheck/docs/linkcheck.xml
[exec] com.werken.werkz.UnattainableGoalException: Unable to obtain goal [test-html2xdoc-site] -- file:/Users/sebastiensahuc/.maven/plugins/maven-xdoc-plugin-1.6- SNAPSHOT/plugin.jelly:327:54: <j:include> could not include jelly script: file://Users/sebastiensahuc/.maven/plugins/maven-xdoc-plugin-1.6- SNAPSHOT/plugin-resources/site.jsl. Reason: org.apache.commons.jelly.JellyException: null:-1:-1: <null> Could not parse Jelly script
[exec] at com.werken.werkz.Goal.fire(Goal.java:646)
[exec] at com.werken.werkz.Goal.attain(Goal.java:575)
[exec] at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
[exec] at com.werken.werkz.Goal.attain(Goal.java:573)
[exec] at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
[exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java: 565)
[......]
[exec] ... 105 more
[exec] Caused by: java.net.UnknownHostException: Users
[exec] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:153)
[exec] at java.net.Socket.connect(Socket.java:452)
[exec] at java.net.Socket.connect(Socket.java:402)
[exec] at sun.net.NetworkClient.doConnect(NetworkClient.java:139)
[exec] at sun.net.NetworkClient.openServer(NetworkClient.java:118)
[exec] at sun.net.ftp.FtpClient.openServer(FtpClient.java:423)
[exec] at sun.net.ftp.FtpClient.<init>(FtpClient.java:692)
[exec] at sun.net.www.protocol.ftp.FtpURLConnection.connect(FtpURLConnection.java: 175)
[exec] at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnectio n.java:257)
[exec] at java.net.URL.openStream(URL.java:913)
[exec] at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
[exec] at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
[exec] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
[exec] at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
[exec] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
[exec] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
[exec] at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:357)
[exec] at org.apache.commons.jelly.JellyContext.compileScript(JellyContext.java: 489)
[exec] ... 108 more
[exec] Root cause
[exec] org.apache.commons.jelly.JellyException: null:-1:-1: <null> Could not parse Jelly script
[exec] at org.apache.commons.jelly.JellyContext.compileScript(JellyContext.java: 491)
[exec] at org.apache.commons.jelly.JellyContext.runScript(JellyContext.java:608)
[exec] at org.apache.commons.jelly.JellyContext.runScript(JellyContext.java:584)
[exec] at org.apache.commons.jelly.tags.core.IncludeTag.doTag(IncludeTag.java: 143)
[exec] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
[exec] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
[exec] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
[exec] at org.apache.commons.jelly.tags.core.FileTag.writeBody(FileTag.java:207)
[exec] at org.apache.commons.jelly.tags.core.FileTag.doTag(FileTag.java:103)
[exec] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
[exec] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
[exec] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
[exec] at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java: 145)
[exec] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
[exec] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
[exec] at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:125)
[exec] at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java: 145)
[exec] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
[exec] at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:125)
[exec] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
[exec] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
[exec] at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.j ava:117)
[exec] at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAc tion(MavenGoalTag.java:143)
On Feb 17, 2004, at 3:16 AM, Svetlin Stanchev wrote:
Hi Emmanuel,
I just deleted my maven installation and plugins directory, checked-out and built from scratch.
I am still getting the same error I reported in Jira for the 1.1 (see below).
Could somebody please confirm this, as I am a bit confused already not to make some basic mistake?
Moreover: I'd dare to suggest either tagging both the maven and maven-plugins with the same branch/revision or keeping a list of which versions of the one are known to work with which versions of the other.
If I can assist with this, I'll be more than happy!
I am sure many novices like me would appreciate such an arrangement, as I spent many hours trying to get a version which allows setting the changelog working directory while not breaking important functionality (like multiproject) and am still nowhere.
Thanks for your patience with a novice, -- Svetlin
--- multiproject:site: multiproject:site-init:
multiproject:create-nav:
[echo] Producing aggregate navigation...
PANIC : Velocity cannot find any of the specified or default logging systems in
the classpath, or the classpath doesn't contain the necessary classes to suppor
them. Please consult the documentation regarding logging. Exception : java.lan
.NoClassDefFoundError: org/apache/log/format/Formatter
PANIC : Velocity cannot find any of the specified or default logging systems in
the classpath, or the classpath doesn't contain the necessary classes to suppor
them. Please consult the documentation regarding logging. Exception : java.lan
.NoClassDefFoundError: org/apache/log/format/Formatter
BUILD FAILED
File...... file:/C:/Documents and Settings/sstanchev/.maven/plugins/maven-multi
roject-plugin-1.2-SNAPSHOT/plugin.jelly
Element... velocity:merge
Line...... 119
Column.... 11
org/apache/log/format/Formatter
Feb 17, 2004 11:55:21 AM org.apache.maven.cli.App doMain
INFO: Total time: 24 seconds
Feb 17, 2004 11:55:21 AM org.apache.maven.cli.App doMain
INFO: Finished at: Tue Feb 17 11:55:21 CET 2004
Feb 17, 2004 11:55:21 AM org.apache.maven.cli.App doMain
INFO:
---
Emmanuel Venisse wrote:
HEAD
----- Original Message ----- From: "Svetlin Stanchev" <[EMAIL PROTECTED]>
To: "Maven Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, February 17, 2004 11:21 AM
Subject: Re: first-timer build errorWhich version of maven-plugins should be used for build with this (there
is no 1.0-BRANCH branch for the maven-plugins in CVS)?
Thanks, -- Svetlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
