You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Stefan Bodewig <bo...@apache.org> on 2003/01/28 10:27:54 UTC
Re: xdocs Gump (was [PATCH] Velocity task)
On 28 Jan 2003, Stefan Bodewig <bo...@apache.org> wrote:
> On Tue, 28 Jan 2003, Erik Hatcher
> <ja...@ehatchersolutions.com> wrote:
>> But this should be a one-liner that only takes a second for you to
>> set up, right?
>
> Unlikely, I'd bet it will take at least five lines 8-)
Actually
<project name="ant-xdocs-proposal">
<ant basedir="proposal/xdocs" target="docs-from-scratch">
<property name="ant.home" reference="home" project="jakarta-ant"/>
</ant>
<depend project="jakarta-ant"/>
<depend project="xml-xerces"/>
<depend project="xdoclet" inherit="runtime"/>
<nag to="ant-dev@jakarta.apache.org"
from="Erik Hatcher <jakarta-ant@ehatchersolutions.com>"/>
</project>
Man is this noisy, literally hundreds of lines looking like
[antdoclet] (ConfigParamIntrospector.fillConfigParamsHashMapUsingReflectionFor 232 ) configs.size()=55
[antdoclet] (XDocletMain.start 32 ) Context successfully loaded.
Some strange messages like this
[antdoclet] Error parsing File /home/bodewig/dev/gump/jakarta-ant/src/main/org/apache/tools/ant/listener/AnsiColorLogger.java:Lexical error: xjavadoc.TokenMgrError: Lexical error at line 163, column 44. Encountered: "u" (117), after : "\"\\"
for a perfectly valid unicode escape.
And in the end
BUILD FAILED
java.lang.OutOfMemoryError
Total time: 46 seconds
Which is likely to happen in nightly builds as well.
I'll see whether I can patch Gump to accept JVM arguments and up the
memory and will commit what I currently have as-is.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: xdocs Gump
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 3 Feb 2003, Erik Hatcher <ja...@ehatchersolutions.com>
wrote:
> So, is there any special logging configuration in place?
Not that I was aware of.
This is the snippet that I would use to run the build next night:
export CLASSPATH=$JAVA_HOME/lib/tools.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-ant/dist/lib/ant.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-ant/dist/lib/nodeps.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-ant/dist/lib/ant-junit.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-ant/dist/lib/ant-stylebook.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-ant/dist/lib/ant-swing.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-ant/dist/lib/ant-trax.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-ant/dist/lib/ant-xalan2.jar
export CLASSPATH=/home/bodewig/dev/gump/xml-xerces2/java/build/xercesImpl.jar:$CLASSPATH
export CLASSPATH=/home/bodewig/dev/gump/xml-xerces2/java/build/xmlParserAPIs.jar:$CLASSPATH
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-apache-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-bea-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-borland-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-caucho-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-ejb-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-exolab-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-hibernate-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-hp-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-ibm-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-java-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-jboss-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-jdo-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-jmx-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-libelis-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-macromedia-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-mvcsoft-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-mx4j-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-objectweb-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-orion-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-pramati-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-solarmetric-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-sybase-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-tjdo-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-web-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-webwork-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xdoclet/target/lib/xdoclet-xdoclet-module-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-commons/logging/dist/commons-logging.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-commons/logging/dist/commons-logging-api.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-log4j/log4j-20030203.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-commons/collections/dist/commons-collections.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-bcel/bin/bcel.jar
export CLASSPATH=/home/bodewig/dev/gump/xml-commons/java/external/build/xml-apis.jar:$CLASSPATH
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/xjavadoc/build/lib/xdoclet-xjavadoc-uc-20030203.jar
cd /home/bodewig/dev/gump/jakarta-ant/proposal/xdocs $OUT 2>&1
/usr/local/bin/timeout 1200 java -Xbootclasspath/p:/home/bodewig/dev/gump/xml-xerces2/java/build/xercesImpl.jar:/home/bodewig/dev/gump/xml-xerces2/java/build/xmlParserAPIs.jar:/home/bodewig/dev/gump/xml-commons/java/external/build/xml-apis.jar -Xmx256m org.apache.tools.ant.Main -Dbuild.sysclasspath=only -Dant.home=/home/bodewig/dev/gump/jakarta-ant/dist $TARGET </dev/null $OUT 2>&1
Stefan
Re: xdocs Gump
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
On Monday, February 3, 2003, at 09:41 AM, Stefan Bodewig wrote:
> On Mon, 3 Feb 2003, Erik Hatcher <ja...@ehatchersolutions.com>
> wrote:
>
>> XDoclet uses Commons Logging exclusively, so if log4j is there then
>> its using that, or JDK 1.4 logging (but Gump isn't running JDK 1.4,
>> I don't think).
>
> Gump *is* running JDK 1.4.
Ah, cool.
So, is there any special logging configuration in place? Or just using
the default? It seems a lot of DEBUG level output is coming out in the
Gump runs.
I'm still running JDK 1.3.1 (until Apple releases JDK 1.4 in final
form).
Erik
Re: xdocs Gump
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 3 Feb 2003, Erik Hatcher <ja...@ehatchersolutions.com>
wrote:
> XDoclet uses Commons Logging exclusively, so if log4j is there then
> its using that, or JDK 1.4 logging (but Gump isn't running JDK 1.4,
> I don't think).
Gump *is* running JDK 1.4.
Stefan
Re: xdocs Gump
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
On Monday, February 3, 2003, at 09:16 AM, Stefan Bodewig wrote:
> I still find it hard to move to all the information and filter out
> relevant parts. Is there any way to make the output less noisy?
>
Its not noisy for me at the command-line, so it has to do with the
logging JAR's that are available to the Gump run, I presume. XDoclet
uses Commons Logging exclusively, so if log4j is there then its using
that, or JDK 1.4 logging (but Gump isn't running JDK 1.4, I don't
think). Is there a log4j.properties file that is perhaps being made
available to it somehow?
I'll dig into this more after the next Gump run.
Thanks again, Stefan.
Erik
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 3 Feb 2003, Erik Hatcher <ja...@ehatchersolutions.com>
wrote:
>> There are two occurances of
>>
>> java.lang.IllegalStateException: Engine is null?!
>
>
> But last night was not with the 256m setting, right?
Correct.
> The OutOfMemory is still the kicker here, I think.
So wait for next night's nag 8-)
I still find it hard to move to all the information and filter out
relevant parts. Is there any way to make the output less noisy?
Stefan
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
On Monday, February 3, 2003, at 09:04 AM, Stefan Bodewig wrote:
> actually there are error messages even in last nights build, I don't
> know whether they are significant:
> <http://cvs.apache.org/builds/gump/latest/ant-xdocs-proposal.html>
>
> There are two occurances of
>
> java.lang.IllegalStateException: Engine is null?!
But last night was not with the 256m setting, right? The OutOfMemory
is still the kicker here, I think. Until that is resolved I don't
think any of the other junk is spews is that relevant. Although I
could be wrong about that. I know I saw lots of errors until I got the
memory thing solved for myself.
Erik
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Stefan Bodewig <bo...@apache.org>.
actually there are error messages even in last nights build, I don't
know whether they are significant:
<http://cvs.apache.org/builds/gump/latest/ant-xdocs-proposal.html>
There are two occurances of
java.lang.IllegalStateException: Engine is null?!
Stefan
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
On Monday, February 3, 2003, at 08:36 AM, Stefan Bodewig wrote:
> On 03 Feb 2003, Stefan Bodewig <bo...@apache.org> wrote:
>
>> I've committed something that is supposed to work.
>
> "supposed to" because:
>
> Scrolling back through all the noise I find this one here
>
> ,----
> | [antdoclet] java.lang.ClassNotFoundException:
> org.apache.tools.ant.taskdefs.optional.sound.SoundTask
> `----
>
> Is this the cause? Can XDoclet deal with finding sources without the
> corresponding classes? Gump will not compile all optional tasks
> because we have not added all possible third party libraries.
I've cloned all the <selector>'s from Ant's main build.xml - so it
should only process the source files that it has classes for, but
perhaps there is an issue with it. I'll look into it sometime soon.
Erik
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Stefan Bodewig <bo...@apache.org>.
On 03 Feb 2003, Stefan Bodewig <bo...@apache.org> wrote:
> I've committed something that is supposed to work.
"supposed to" because:
,----
| BUILD FAILED
| file:///home/bodewig/dev/gump/jakarta-ant/proposal/xdocs/build.xml:387: Unexpected error
|
| Total time: 2 minutes 31 seconds
`----
Scrolling back through all the noise I find this one here
,----
| [antdoclet] java.lang.ClassNotFoundException: org.apache.tools.ant.taskdefs.optional.sound.SoundTask
`----
Is this the cause? Can XDoclet deal with finding sources without the
corresponding classes? Gump will not compile all optional tasks
because we have not added all possible third party libraries.
Stefan
Re: xdocs Gump
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
On Monday, February 3, 2003, at 08:46 AM, Conor MacNeill wrote:
> Erik Hatcher wrote:
>> Wow!
>> You're my hero. So do I need to lobby for the 256m, or did you set
>> that up already too?
>
> Erik, just curiosity more than anything else since I don't know the
> internals of xdoclet at all - why does it need so much memory?
Its actually xjavadoc that needs the memory - the parsing of source
code (using a JavaCC-based Java parser) apparently takes a lot of
memory. I'm clueless to what is going on under the hood of xjavadoc,
so I can't say for sure.
Erik
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Conor MacNeill <co...@cortexebusiness.com.au>.
Erik Hatcher wrote:
> Wow!
>
> You're my hero. So do I need to lobby for the 256m, or did you set that
> up already too?
>
Erik, just curiosity more than anything else since I don't know the
internals of xdoclet at all - why does it need so much memory?
Conor
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
Wow!
You're my hero. So do I need to lobby for the 256m, or did you set
that up already too?
I look forward to the lack of a nag mail tomorrow :))
Erik
On Monday, February 3, 2003, at 08:30 AM, Stefan Bodewig wrote:
> On 31 Jan 2003, Stefan Bodewig <bo...@apache.org> wrote:
>> On Thu, 30 Jan 2003, Erik Hatcher
>> <ja...@ehatchersolutions.com> wrote:
>>
>>> Again, it'd take a Gump expert only a little bit of time probably,
>>
>> I'm not sure.
>
> It didn't take a Gump expert or an XSLT expert, it turned out to be
> rather easy 8-)
>
> I've committed something that is supposed to work.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: ant-dev-help@jakarta.apache.org
>
>
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Stefan Bodewig <bo...@apache.org>.
On 31 Jan 2003, Stefan Bodewig <bo...@apache.org> wrote:
> On Thu, 30 Jan 2003, Erik Hatcher
> <ja...@ehatchersolutions.com> wrote:
>
>> Again, it'd take a Gump expert only a little bit of time probably,
>
> I'm not sure.
It didn't take a Gump expert or an XSLT expert, it turned out to be
rather easy 8-)
I've committed something that is supposed to work.
Stefan
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Stefan Bodewig <bo...@apache.org>.
On Sat, 01 Feb 2003, Conor MacNeill <co...@cortexebusiness.com.au>
wrote:
> Then run
>
> ant -Dworkspace=erik.xml
And make sure you have an XSLT transformer on your CLASSPATH (or use
JDK 1.4). The full JAXP 1.1 program is all you should need AFAIK.
Stefan
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Conor MacNeill <co...@cortexebusiness.com.au>.
Erik Hatcher wrote:
> On Friday, January 31, 2003, at 05:48 AM, Stefan Bodewig wrote:
>
>>> Or is this back in my hands?
>>
>>
>> Why not?
>
>
> I got jakarta-gump from CVS yesterday, and tried:
>
> ant
>
I created a workspace file (conor.xml) as follows
<?xml version="1.0" ?>
<workspace basedir="[gump_home]" pkgdir="/opt"
sync="rsync -r -a --delete" version="0.3">
<property name="build.sysclasspath" value="only"/>
<profile href="profile/gump.xml"/>
</workspace>
Let's call your's erik.xml (if you use gen.sh, it needs to be the hostname,
I think)
Replace the basedir value with wherever you want to have Gump download and
build things.
Then run
ant -Dworkspace=erik.xml
If you want to check for packages you will need to download and install do this
ant -Dworkspace=erik.xml check
HTH
Conor
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Stefan Bodewig <bo...@apache.org>.
On Sat, 1 Feb 2003, Erik Hatcher <ja...@ehatchersolutions.com>
wrote:
> Neither succeeded for me.
There is some hardcoded path to Xalan in it, that may need to get
overridden (I use the XALAN env variable for this).
> Is Gump runnable out-of-the-box these days?
More or less, yes. You have to define a workspace, though.
>> Do you want to do some of the things that are higher on my priority
>> list so we can swap 8-)
>
> I don't think you'd want to swap with my TODO list either :)
;-)
Didn't mean to imply that. I know that you know, but ...
Stefan
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
On Friday, January 31, 2003, at 05:48 AM, Stefan Bodewig wrote:
>> Or is this back in my hands?
>
> Why not?
I got jakarta-gump from CVS yesterday, and tried:
ant
and
gen.sh
Neither succeeded for me. Is Gump runnable out-of-the-box these days?
I got compile errors on Jenny. Missing the DOM classes (Element, for
example). Do I need to tweak with my environment to add dependencies
just to get Gump to build?
>> Again, it'd take a Gump expert only a little bit of time probably,
>
> I'm not sure. You'd basically have to modify XSLT stylesheets, and
> even if I'd consider myself above the rookie level when it comes to
> Gump, I'm more or less XSLT ignorant.
>
> Do you want to do some of the things that are higher on my priority
> list so we can swap 8-)
I don't think you'd want to swap with my TODO list either :) In fact,
I wouldn't wish mine upon my worst enemies at this point. But we're
all in the same boat with things to do, no question. I'll see what I
can do with this when time permits. Thanks for your help in getting
the build set up as much as you have so far.
I know XSLT ok enough to probably get this working, but I'll need a
functioning Gump first. I'll get on the Gump list when I start
fighting with this again and get it going.
Erik
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 30 Jan 2003, Erik Hatcher <ja...@ehatchersolutions.com>
wrote:
> Is this in progress?
If you are waiting for me, well it might be in progress but at a
rather low priority, sorry.
> Or is this back in my hands?
Why not?
> Again, it'd take a Gump expert only a little bit of time probably,
I'm not sure. You'd basically have to modify XSLT stylesheets, and
even if I'd consider myself above the rookie level when it comes to
Gump, I'm more or less XSLT ignorant.
Do you want to do some of the things that are higher on my priority
list so we can swap 8-)
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
On Thursday, January 30, 2003, at 03:40 AM, Stefan Bodewig wrote:
> On Wed, 29 Jan 2003, Erik Hatcher <ja...@ehatchersolutions.com>
> wrote:
>
>> What else needs to be done?
>
> Gump's stylesheets need to get patched to understand some kind of
> <jvmarg> element inside <ant> and add the content to the generated
> build scripts.
Is this in progress? Or is this back in my hands? Again, it'd take a
Gump expert only a little bit of time probably, and it'd take me a fair
bit longer - but I know the open-source way, if you want it done, do it
yourself :)
But I think the effort will be well worth it - and folks will then get
to see first hand what can be generated and evolving it will be much
more visible and effective I think.
Thanks,
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 29 Jan 2003, Erik Hatcher <ja...@ehatchersolutions.com>
wrote:
> What else needs to be done?
Gump's stylesheets need to get patched to understand some kind of
<jvmarg> element inside <ant> and add the content to the generated
build scripts.
After that, add the new born element to the docs and to the descriptor
for the xdocs stuff (and maybe ask whether 256m is OK with all people
using the default Gump profile before that).
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
Stefan,
I just checked the Gump e-mail archives and see the two commits you did
yesterday to get started on this. What else needs to be done?
Many thanks for your work to get this incorporated into the nightly
Gump builds!
Erik
On Tuesday, January 28, 2003, at 12:07 PM, Erik Hatcher wrote:
> On Tuesday, January 28, 2003, at 04:47 AM, Stefan Bodewig wrote:
>>> ANT_OPTS = -Xmx1000m
>>
>> Uhm, that's a little too tough IMHO.
>
> 256m works fine on my machine also.
>
> Erik
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
On Tuesday, January 28, 2003, at 04:47 AM, Stefan Bodewig wrote:
>> ANT_OPTS = -Xmx1000m
>
> Uhm, that's a little too tough IMHO.
256m works fine on my machine also.
Erik
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 28 Jan 2003, Erik Hatcher <ja...@ehatchersolutions.com>
wrote:
> The JAR is xdoclet-xjavadoc-uc-<VERSION>.jar
>
> Chances are both were built with Gump, right?
Both get built, but Gump doesn't know about the uc one. Yet.
> But the classpath ordering is crucial here.
I'll drop the xjavadoc in favor of xjavadoc-uc from Gump completely.
> ANT_OPTS = -Xmx1000m
Uhm, that's a little too tough IMHO.
> Definitely more VM memory is needed to run this.
Any idea how much? If it turns out to be more than I'd like to see
consumed on say nagoya, I'll remove the descriptor from Gump's default
profile and tell people who are interested how to put it into their
own workspace.
As for your request to publish the stuff: gump@jakarta.apache.org may
be the better list.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: xdocs Gump (was [PATCH] Velocity task)
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
On Tuesday, January 28, 2003, at 04:27 AM, Stefan Bodewig wrote:
> [antdoclet] Error parsing File
> /home/bodewig/dev/gump/jakarta-ant/src/main/org/apache/tools/ant/
> listener/AnsiColorLogger.java:Lexical error: xjavadoc.TokenMgrError:
> Lexical error at line 163, column 44. Encountered: "u" (117), after :
> "\"\\"
This is because the wrong xjavadoc JAR is being used in the classpath.
The Unicode JAR is needed, which apparently runs slightly slower than
the non-Unicode parser - but its needed to get the '\...' stuff to
parse.
The JAR is xdoclet-xjavadoc-uc-<VERSION>.jar
Chances are both were built with Gump, right? But the classpath
ordering is crucial here.
> BUILD FAILED
> java.lang.OutOfMemoryError
>
> Total time: 46 seconds
>
> Which is likely to happen in nightly builds as well.
>
> I'll see whether I can patch Gump to accept JVM arguments and up the
> memory and will commit what I currently have as-is.
I run with this:
ANT_OPTS = -Xmx1000m
-
Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLo
g
Definitely more VM memory is needed to run this.
Erik
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>