Ok, now the build seems to work. But the eomodel file isnt included
into the build. I've explicitely marked it as resource. Still no
success. Any ideas?
Thierry
Am 06.08.2008 um 16:28 schrieb Mike Schrag:
if yours work, don't mess with them ... many of mine still use javac
because they work, i hate build systems, and the thought of messing
with them makes me grumpy.
On Aug 6, 2008, at 10:27 AM, David Avendasora wrote:
On Aug 6, 2008, at 10:15 AM, Mike Schrag wrote:
This is the line 229: <javac srcdir = "src" destdir = "bin">
You want wocompile rather than javac ... I don't know if this is
an ant bug or just some way that our build files abuse something,
but ant has this asinine behavior where it tries to traverse the
entire directory structure to find files that match the given
patternsets, only you don't have read access for some of those
files, which causes it to explode. wocompile does not have this
problem. I believe a modern build.xml does not use javac, so you
can create a new project to get a template to work from.
Mike,
Is there a difference in the resulting build between javac and
wocompile if the build is executing successfully?
My heavily modified (for Java Client) build.xml file still uses
javac as well and if I don't _need_ to mess with it, I don't want to.
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/mailinglist%40seabix.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
