It's not you. I should have tested this myself.

It's doing the same thing for me too, but you may be right about the fork.

You can set JAVA_HOME in an environment wide way by setting it in your ~/.MacOSX/environment.plist file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ANT_HOME</key>
<string>/Users/steve/tools/apache-ant-1.5.2</string>
<key>CVS_RSH</key>
<string>ssh</string>
<key>JAVA_HOME</key>
<string>/Library/Java/Home</string>
<key>MAVEN_HOME</key>
<string>/Users/steve/tools/maven-1.0-beta-8</string>
<key>ORACLE_HOME</key>
<string>/Users/oracle/9iR2/orahome</string>
</dict>
</plist>

The "Property List Editor" in the Apple Developer tools provides a convenient way to build/edit this file.

You need to log out and log back in before it takes effect.

It's possible that this may eliminate your problem for now.

In the meantime, I'm looking at updating the xdoclet in the 3.0 and 3.2 branches.

Steve Coy


On Tuesday, March 18, 2003, at 09:22 PM, Lennart Petersson wrote:

don't know if it's me being stupid... but this wont help me anyway :(

When building with -verbose flag it correctly reports that it has detected a 1.3.1 jvm but then it still craches when it's time for the xdoclet task. Any ideas? Has it anything to do with the fact that it is forking the xdocletXDocletMain?

/L

tisdagen den 18 mars 2003 kl 01.24 skrev Stephen Coy:

Unfortunately, all versions of xdoclet (except the one David J fixed) have the same bug - using InputStream.available() to see how many bytes are left in the file.
I'm part way thru getting JBoss 3.0.x to build with Apple's 1.4.1, but I had to migrate HEAD's xdoclet into the source base and fix almost every build.xml to suit.

In retrospect, it's probably simpler to get the version of xdoclet from CVS that we've used here (I think David tagged it), fix it, and use that.

As has been previously mentioned, you can still build with 1.3.1 by setting:

JAVA_HOME= /System/Library/Frameworks/JavaVM.framework/Versions/1.3.1/Home

Steve Coy

On Tuesday, March 18, 2003, at 01:36 AM, Lennart Petersson wrote:

Was Mr. Jenk's fix only for head? Because I get problems when building 3.0/3.2 also. Here is output from 3.0:

compile-mbean-sources:
[mkdir] Created dir: /Users/lepe/projects/JbossSources/jboss-3.0/common/output/gen-src
sourcepath is deprecated. the preferred way to design sources is via nested <fileset>
Running xdoclet.XDocletMain loaded by sun.misc.Launcher$AppClassLoader. Forked:true
[xdoclet] Running <mbeanInterface/>
[xdoclet] Generating output for 'org.jboss.util.property.jmx.SystemPropertyClassValue' using template file 'jar:file:/Users/lepe/projects/JbossSources/jboss-3.0/tools/lib/xdoclet.jar!/xdoclet/jmx/mbean.j'.
[xdoclet] Running XDoclet failed
[xdoclet] <<Running XDoclet failed.>>
[xdoclet] java.lang.RuntimeException: Error running XDoclet
[xdoclet] at xdoclet.XDocletMain.start(XDocletMain.java:77)
[xdoclet] at xjavadoc.ant.XJavaDocMain.main(XJavaDocMain.java:94)

Using OSX jdk 1.4.1 official release and latest 3.0



-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!Get cracking and register here for some mind boggling fun andthe chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink?You could win a Tablet PC. Get a free Tablet PC hat just for playing.What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to