You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mathew Kuppe <ku...@360t.com> on 2004/02/13 11:15:24 UTC
first-timer build error
Hi,
I am trying to build maven from cvs, and am receiving compile errors
during the first phase of the compiling.
I am using the "ant -f build-bootstrap.xml" command.
The compilation error is the following;
[javac]
E:\sandbox\maven\src\java\org\apache\maven\DefaultProjectMarshaller.java
:72: package org.xmlpull.v1 does not exist
[javac] import org.xmlpull.v1.XmlPullParserFactory;
I am using ant 1.6.0 and 1.6.1.
Can you please suggest what this error may be?
Thank you in advance.
With kind regards,
Mathew Kuppe
Re: first-timer build error
Posted by Sean Kelly <ke...@seankelly.biz>.
> Is there a place where you specify a file url and set it to
> "file://home/kelly/..." ?
> If it is the case, Java thinks home is a host, so please change to:
Nope; I haven't done anything. This is with a fresh, untouched CVS
checkout of MAVEN-1_0-BRANCH of maven, and HEAD of maven-plugins.
Odd, huh? (At least I'm not the only one!)
--Sean
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Villevalois Didier <dv...@clever-age.com>.
Is there a place where you specify a file url and set it to
"file://home/kelly/..." ?
If it is the case, Java thinks home is a host, so please change to:
file:///home/kelly/...
First two / are from the URL scheme before the host, the third one is
for the root of your hard drive.
++didier
Sean Kelly wrote:
>
>> with a very strange Caused by: java.net.UnknownHostException: Users
>> if you keep looking below
>
>
>
> Interesting; I'm getting the exact same exception in the exact same
> place, but the unknown host isn't "Users", it's "home".
>
> Is there any chance your home directory is something like
> /Users/sebastien? Mine's /home/kelly.
>
> --Sean
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Sebastien Sahuc <ss...@intalio.com>.
Thanks Sean, I'm glad to hear I'm not the only person getting this
weird exception. And yes, my home dir is /Users/sebastiensahuc, which
might help hinting the issue. Good catch !
Seb
On Feb 17, 2004, at 8:43 AM, Sean Kelly wrote:
>
>> with a very strange Caused by: java.net.UnknownHostException: Users
>> if you keep looking below
>
>
> Interesting; I'm getting the exact same exception in the exact same
> place, but the unknown host isn't "Users", it's "home".
>
> Is there any chance your home directory is something like
> /Users/sebastien? Mine's /home/kelly.
>
> --Sean
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Sean Kelly <ke...@seankelly.biz>.
> with a very strange Caused by: java.net.UnknownHostException: Users
> if you keep looking below
Interesting; I'm getting the exact same exception in the exact same
place, but the unknown host isn't "Users", it's "home".
Is there any chance your home directory is something like
/Users/sebastien? Mine's /home/kelly.
--Sean
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
loader constraints violated ... eek!
Posted by Sean Kelly <ke...@seankelly.biz>.
OK, now that we've overcome the slash problem in the xdoc plugin.jelly,
the next hurdle is class loading related. (Yes, it would just /have/ to
be, huh?)
Using either HEAD or MAVEN-1_0-BRANCH of maven and HEAD of
maven-plugins, running the site goal for a simple project produces this
lovely gem:
BUILD FAILED
File...... file:/C:/Documents and
Settings/kelly/.maven/plugins/maven-xdoc-plugin-1.6-SNAPSHOT/plugin.jelly
Element... velocity:merge
Line...... 439
Column.... 9
loader constraints violated when linking
org/apache/velocity/context/Context class
There's no CLASSPATH defined, nothing in jre/lib/endorsed or jre/lib/ext
that shouldn't be, just ... unhappiness.
Any ideas anyone?
--Sean
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Sean Kelly <ke...@seankelly.biz>.
>Could you try to remove line 365 (if you cvs head for xdoc plugin) and
>certainly 346-347 of plugin.jelly?
>I have no time for test it.
>
>
Oddly, my reply to this never showed up. Well at the risk of
redundancy, here it is again:
Removing those lines caused other problems (unable to find navigation.xml).
However, changing line 365 from
<j:set var="stylesheet" value="file:/${plugin.resources}/site.jsl" />
to
<j:set var="stylesheet" value="file://${plugin.resources}/site.jsl" />
makes it work on Unix /and/ Windows. Makes sense, since
plugin.resources is a full path starting with /.
--Sean
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Sean Kelly <ke...@seankelly.biz>.
>Could you try to remove line 365 (if you cvs head for xdoc plugin) and
>certainly 346-347 of plugin.jelly?
>I have no time for test it.
>
>
Removing those lines caused other problems (unable to find navigation.xml).
However, changing line 365 from
<j:set var="stylesheet" value="file:/${plugin.resources}/site.jsl" />
to
<j:set var="stylesheet" value="file://${plugin.resources}/site.jsl" />
makes it work on Unix. I'm redoing it on Windows to make sure it's OK
there, too. Makes sense, since plugin.resources is a full path starting
with /.)
--Sean
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Emmanuel Venisse <em...@venisse.net>.
Could you try to remove line 365 (if you cvs head for xdoc plugin) and
certainly 346-347 of plugin.jelly?
I have no time for test it.
Emmanuel
----- Original Message -----
From: "Sean Kelly" <ke...@seankelly.biz>
To: "Maven Users List" <us...@maven.apache.org>
Sent: Tuesday, February 17, 2004 6:27 PM
Subject: Re: first-timer build error
>
> >Ok, so it's a bug in xdoc plugin. It works fine under windows.
> >
> >
> Confirmed. I get the error on Fedora Core release 1 Linux, but not on
> Windows XP Pro SP1.
>
> Some slashification bug, perhaps? :-/ :-\
>
> --Sean
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Sean Kelly <ke...@seankelly.biz>.
>Ok, so it's a bug in xdoc plugin. It works fine under windows.
>
>
Confirmed. I get the error on Fedora Core release 1 Linux, but not on
Windows XP Pro SP1.
Some slashification bug, perhaps? :-/ :-\
--Sean
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Emmanuel Venisse <em...@venisse.net>.
Ok, so it's a bug in xdoc plugin. It works fine under windows.
Emmanuel
----- Original Message -----
From: "Sebastien Sahuc" <ss...@intalio.com>
To: "Maven Users List" <us...@maven.apache.org>
Sent: Tuesday, February 17, 2004 5:58 PM
Subject: Re: first-timer build error
> Emmanuel,
>
> Where should the repository address be redefined ? I don't think I have
> anything specific for my env (no build.properties ) etc...
>
> The weird thing is that taking the feb/9/04 snapshot (HEAD) works fine,
> whereas using the 1.0 branch gives me the error reported here. Even
> more funny is that few days ago I had a completely entirely different
> error message when building maven from latest 1.0 branch. I truly
> confused, and since there is a patch I'd like to submit, I have to wait
> till I get the latest version up and running.
>
> Thanks again for such a quick response, this is truly appreciated.
>
> Seb
>
>
> On Feb 17, 2004, at 8:47 AM, Emmanuel Venisse wrote:
>
> > Apparently, you redefine repository address.
> >
> > Your protocol definition is incorrect. You use file:// instead of
> > file:///
> > (or eventually file:/)
> >
> > Emmanuel
> >
> > ----- Original Message -----
> > From: "Sebastien Sahuc" <ss...@intalio.com>
> > To: "Maven Users List" <us...@maven.apache.org>
> > Sent: Tuesday, February 17, 2004 5:33 PM
> > Subject: Re: first-timer build error
> >
> >
> >> Hi Emmanuel,
> >>
> >> 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.jav
> >> a:
> >> 175)
> >> [exec] at
> >> sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnect
> >> io
> >> 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.perform
> >> Ac
> >> 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"
> >>>> <sv...@acm.org>
> >>>> To: "Maven Users List" <us...@maven.apache.org>
> >>>> Sent: Tuesday, February 17, 2004 11:21 AM
> >>>> Subject: Re: first-timer build error
> >>>>> Which 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: users-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Sebastien Sahuc <ss...@intalio.com>.
Emmanuel,
Where should the repository address be redefined ? I don't think I have
anything specific for my env (no build.properties ) etc...
The weird thing is that taking the feb/9/04 snapshot (HEAD) works fine,
whereas using the 1.0 branch gives me the error reported here. Even
more funny is that few days ago I had a completely entirely different
error message when building maven from latest 1.0 branch. I truly
confused, and since there is a patch I'd like to submit, I have to wait
till I get the latest version up and running.
Thanks again for such a quick response, this is truly appreciated.
Seb
On Feb 17, 2004, at 8:47 AM, Emmanuel Venisse wrote:
> Apparently, you redefine repository address.
>
> Your protocol definition is incorrect. You use file:// instead of
> file:///
> (or eventually file:/)
>
> Emmanuel
>
> ----- Original Message -----
> From: "Sebastien Sahuc" <ss...@intalio.com>
> To: "Maven Users List" <us...@maven.apache.org>
> Sent: Tuesday, February 17, 2004 5:33 PM
> Subject: Re: first-timer build error
>
>
>> Hi Emmanuel,
>>
>> 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.jav
>> a:
>> 175)
>> [exec] at
>> sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnect
>> io
>> 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.perform
>> Ac
>> 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"
>>>> <sv...@acm.org>
>>>> To: "Maven Users List" <us...@maven.apache.org>
>>>> Sent: Tuesday, February 17, 2004 11:21 AM
>>>> Subject: Re: first-timer build error
>>>>> Which 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: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Emmanuel Venisse <em...@venisse.net>.
Apparently, you redefine repository address.
Your protocol definition is incorrect. You use file:// instead of file:///
(or eventually file:/)
Emmanuel
----- Original Message -----
From: "Sebastien Sahuc" <ss...@intalio.com>
To: "Maven Users List" <us...@maven.apache.org>
Sent: Tuesday, February 17, 2004 5:33 PM
Subject: Re: first-timer build error
> Hi Emmanuel,
>
> 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"
> >> <sv...@acm.org>
> >> To: "Maven Users List" <us...@maven.apache.org>
> >> Sent: Tuesday, February 17, 2004 11:21 AM
> >> Subject: Re: first-timer build error
> >>> Which 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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Sebastien Sahuc <ss...@intalio.com>.
Hi Emmanuel,
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"
>> <sv...@acm.org>
>> To: "Maven Users List" <us...@maven.apache.org>
>> Sent: Tuesday, February 17, 2004 11:21 AM
>> Subject: Re: first-timer build error
>>> Which 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Svetlin Stanchev <sv...@acm.org>.
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" <sv...@acm.org>
> To: "Maven Users List" <us...@maven.apache.org>
> Sent: Tuesday, February 17, 2004 11:21 AM
> Subject: Re: first-timer build error
>
>
>
>>Which 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Emmanuel Venisse <em...@venisse.net>.
HEAD
----- Original Message -----
From: "Svetlin Stanchev" <sv...@acm.org>
To: "Maven Users List" <us...@maven.apache.org>
Sent: Tuesday, February 17, 2004 11:21 AM
Subject: Re: first-timer build error
> Which 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
>
>
> Jason van Zyl wrote:
>
> > On Fri, 2004-02-13 at 05:31, Emmanuel Venisse wrote:
> >
> >>You must use MAVEN_1.0_BRANCH in cvs. The HEAD isn't for users for the
> >>moment.
> >
> >
> > MAVEN-1_0-BRANCH
> >
> > is the name of the branch, which I mispelled the first three times
> > trying to update :-)
> >
> >
> >>The 1.0 branch is the future rc2 that will be release in few days.
> >>
> >>Emmanuel
> >>
> >>----- Original Message -----
> >>From: "Mathew Kuppe" <ku...@360t.com>
> >>To: <us...@maven.apache.org>
> >>Sent: Friday, February 13, 2004 11:15 AM
> >>Subject: first-timer build error
> >>
> >>
> >>Hi,
> >>
> >>
> >>
> >>I am trying to build maven from cvs, and am receiving compile errors
> >>during the first phase of the compiling.
> >>
> >>
> >>
> >>I am using the "ant -f build-bootstrap.xml" command.
> >>
> >>
> >>
> >>The compilation error is the following;
> >>
> >>
> >>
> >>[javac]
> >>E:\sandbox\maven\src\java\org\apache\maven\DefaultProjectMarshaller.java
> >>:72: package org.xmlpull.v1 does not exist
> >>
> >>[javac] import org.xmlpull.v1.XmlPullParserFactory;
> >>
> >>
> >>
> >>I am using ant 1.6.0 and 1.6.1.
> >>
> >>
> >>
> >>Can you please suggest what this error may be?
> >>
> >>
> >>
> >>Thank you in advance.
> >>
> >>
> >>
> >>
> >>
> >>With kind regards,
> >>
> >>
> >>
> >>Mathew Kuppe
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Svetlin Stanchev <sv...@acm.org>.
Which 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
Jason van Zyl wrote:
> On Fri, 2004-02-13 at 05:31, Emmanuel Venisse wrote:
>
>>You must use MAVEN_1.0_BRANCH in cvs. The HEAD isn't for users for the
>>moment.
>
>
> MAVEN-1_0-BRANCH
>
> is the name of the branch, which I mispelled the first three times
> trying to update :-)
>
>
>>The 1.0 branch is the future rc2 that will be release in few days.
>>
>>Emmanuel
>>
>>----- Original Message -----
>>From: "Mathew Kuppe" <ku...@360t.com>
>>To: <us...@maven.apache.org>
>>Sent: Friday, February 13, 2004 11:15 AM
>>Subject: first-timer build error
>>
>>
>>Hi,
>>
>>
>>
>>I am trying to build maven from cvs, and am receiving compile errors
>>during the first phase of the compiling.
>>
>>
>>
>>I am using the "ant -f build-bootstrap.xml" command.
>>
>>
>>
>>The compilation error is the following;
>>
>>
>>
>>[javac]
>>E:\sandbox\maven\src\java\org\apache\maven\DefaultProjectMarshaller.java
>>:72: package org.xmlpull.v1 does not exist
>>
>>[javac] import org.xmlpull.v1.XmlPullParserFactory;
>>
>>
>>
>>I am using ant 1.6.0 and 1.6.1.
>>
>>
>>
>>Can you please suggest what this error may be?
>>
>>
>>
>>Thank you in advance.
>>
>>
>>
>>
>>
>>With kind regards,
>>
>>
>>
>>Mathew Kuppe
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Jason van Zyl <jv...@maven.org>.
On Fri, 2004-02-13 at 05:31, Emmanuel Venisse wrote:
> You must use MAVEN_1.0_BRANCH in cvs. The HEAD isn't for users for the
> moment.
MAVEN-1_0-BRANCH
is the name of the branch, which I mispelled the first three times
trying to update :-)
> The 1.0 branch is the future rc2 that will be release in few days.
>
> Emmanuel
>
> ----- Original Message -----
> From: "Mathew Kuppe" <ku...@360t.com>
> To: <us...@maven.apache.org>
> Sent: Friday, February 13, 2004 11:15 AM
> Subject: first-timer build error
>
>
> Hi,
>
>
>
> I am trying to build maven from cvs, and am receiving compile errors
> during the first phase of the compiling.
>
>
>
> I am using the "ant -f build-bootstrap.xml" command.
>
>
>
> The compilation error is the following;
>
>
>
> [javac]
> E:\sandbox\maven\src\java\org\apache\maven\DefaultProjectMarshaller.java
> :72: package org.xmlpull.v1 does not exist
>
> [javac] import org.xmlpull.v1.XmlPullParserFactory;
>
>
>
> I am using ant 1.6.0 and 1.6.1.
>
>
>
> Can you please suggest what this error may be?
>
>
>
> Thank you in advance.
>
>
>
>
>
> With kind regards,
>
>
>
> Mathew Kuppe
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
--
jvz.
Jason van Zyl
jason@maven.org
http://maven.apache.org
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: first-timer build error
Posted by Emmanuel Venisse <em...@venisse.net>.
You must use MAVEN_1.0_BRANCH in cvs. The HEAD isn't for users for the
moment.
The 1.0 branch is the future rc2 that will be release in few days.
Emmanuel
----- Original Message -----
From: "Mathew Kuppe" <ku...@360t.com>
To: <us...@maven.apache.org>
Sent: Friday, February 13, 2004 11:15 AM
Subject: first-timer build error
Hi,
I am trying to build maven from cvs, and am receiving compile errors
during the first phase of the compiling.
I am using the "ant -f build-bootstrap.xml" command.
The compilation error is the following;
[javac]
E:\sandbox\maven\src\java\org\apache\maven\DefaultProjectMarshaller.java
:72: package org.xmlpull.v1 does not exist
[javac] import org.xmlpull.v1.XmlPullParserFactory;
I am using ant 1.6.0 and 1.6.1.
Can you please suggest what this error may be?
Thank you in advance.
With kind regards,
Mathew Kuppe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org