I’ve imported the Wonder source projects that I just cloned into Eclipse. I’m
seeing other errors such as this DocsByExample/Session.java where Double.vaueOf
is used instead of Double.valueOf. I’m guessing the ‘ant frameworks’ command
didn’t need the files containing these types of errors.
I think it does, yes. Of course, I’m clueless outside of having a lot of
compiler issues over the years...Frankly, I’m always about 50% confused during
these circumstances so I’m certain someone else knows for sure.
But I’m guessing you can solve even command-line ant build settings by
attendin
I running ant from the command line to build in the WonderSource git
repository that I cloned per the below link. Would that use an eclipse setting?
https://wiki.wocommunity.org/display/documentation/Building+and+Installing+a+Framework+with+Ant
> On Dec 31, 2019, at 10:04 AM, Jesse Tayler w
I suspect your compiler settings.
Check those in eclipse to be certain about your target and compiler being used
by your build.
> On Dec 31, 2019, at 10:56 AM, Jeffrey Schmitz via Webobjects-dev
> wrote:
>
>
> Also, now when I manually fix the Override error I’m getting additional
> erro
Also, now when I manually fix the Override error I’m getting additional errors:
global.dummy:
[wocompile] Compiling 11 source files to
/Users/netBrackets/Roots/classes/ERProfiling
[wocompile] warning: [options] bootstrap class path not set in conjunction with
-source 8
[wocompile]
/Users/netBr
I switched to java 8:
java -version
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_232-b09)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.232-b09, mixed mode)
But am still getting the error.
[wocompile]
/Users/netBrackets/git/WonderSource/Frameworks/Core
Hi Jeffrey,
What Java version are you using to compile the code? If it's Java 11 or
greater, this error is expected because the method destroy of the Thread class
was removed. It's deprecated since Java 8.
Currently, it's advisable to build Wonder with Java 8. You can still use the
resulting b
Hello List (again),
I’m trying to build the latest wonder source and am getting the below error.
I was able to build by deleting the @Override annotation, but am not sure if
this is the right thing to do .
[wocompile]
/Users/netBrackets/git/WonderSource/Frameworks/Core/ERExtensions/Sources/e
Never saw this error before. What is on line 83 in your build.xml? Do you use a
custom / old one or do you have the most recent from the Wonder templates?
jw
> Am 02.06.2017 um 16:49 schrieb ece :
>
> Hello all
>
> macOS:
> When I tried to build application from within eclipse I get the follo
No takers?
If any one has any ideas please..
> On 2 Jun 2017, at 16:49, ece wrote:
>
> Hello all
>
> macOS:
> When I tried to build application from within eclipse I get the following
> error message:(Context Menü on build.xml -> run as Ant task)
> Any idea what this could be?
> Message and r
Hello all
macOS:
When I tried to build application from within eclipse I get the following error
message:(Context Menü on build.xml -> run as Ant task)
Any idea what this could be?
Message and relevant build.xml section s. below.
We have a Windows machine on a customers site having the same prob
9, 2015 at 3:19 AM
To: WebObjects-Dev Mailing List List
mailto:webobjects-dev@lists.apple.com>>
Subject: Build error java.lang.NoClassDefFoundError:
Hi everyone,
I am gettiong an error since i build wonder to too be able to deploy my app.
Before build wonder i have just imported wonder fram
Thank you all. I believe I have identified the problem.
Never never hide an old version of woproject.jar in your ~/.ant/lib directory.
If you are getting standalone ant build errors and weirdness after upgrading,
always always check. It also breaks ant builds from within eclipse.
I should have
I had strange seemingly recursion issues just because my project had some
parent folder containing a space in the name once. Just throwing that out
there.
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list
Thanks Chuck,
No links in my projects.
Have searched elsewhere and there are links in the wonder sources (build.xml).
I created an empty project and it compiled with ant.
I then repeatedly added frameworks into the build path.
My application frameworks added without problems.
I then started addi
ong wolips.properties files.
Mark
On 20 Feb 2015, at 15:54, Mark Wardle
> wrote:
Forgot to cc. list
Begin forwarded message:
Subject: Re: ant build error - too many open files
From: Mark Wardle
>
Date: 20 February 2015 15:54:30 GMT
Message-Id:
<605a3035-0a99-45f7-bbc4-4f95ec615...
ardle wrote:
>>
>> Forgot to cc. list
>>
>>> Begin forwarded message:
>>>
>>> Subject: Re: ant build error - too many open files
>>> From: Mark Wardle
>>> Date: 20 February 2015 15:54:30 GMT
>>> Message-Id: <605a3035-0a99-45f7
properties files.
Mark
On 20 Feb 2015, at 15:54, Mark Wardle > wrote:
Forgot to cc. list
Begin forwarded message:
*Subject: **Re: ant build error - too many open files*
*From: *Mark Wardle >
*Date: *20 February 2015 15:54:30 GMT
*Message-Id: *<605a3035-0a99-45f7-bbc4-4f95ec615..
Forgot to cc. list
> Begin forwarded message:
>
> Subject: Re: ant build error - too many open files
> From: Mark Wardle
> Date: 20 February 2015 15:54:30 GMT
> Message-Id: <605a3035-0a99-45f7-bbc4-4f95ec615...@wardle.org>
> To: Fabian Peters
>
> Thanks Fa
Hi Mark,
Have you tried a reboot? Maybe you've somehow managed to exceed kern.maxfiles
or kern.maxfilesperproc?
Fabian
Am 20.02.2015 um 13:53 schrieb Mark Wardle :
> I’ve upgraded to java8, eclipse4.4 and latest Wonder.
>
> Can compile and run from within eclipse but command line ant build fa
I’ve upgraded to java8, eclipse4.4 and latest Wonder.
Can compile and run from within eclipse but command line ant build failing with
“too many open files”.
Has anyone encountered this error? Rather stuck - have tried cleaning and
re-cleaning and re-installing wonder frameworks.
Mark
[woapp
move the /Developer/WebObjects/Versions/WebObjects533/Library/
Frameworks folder somewhere else or delete it -- does the build fail
in a different way?
On Aug 12, 2009, at 2:29 PM, Miguel Angel Torres Avila wrote:
I used FileMerge to compare the info.plist of an old framework (that
not caus
On Aug 12, 2009, at 11:18 AM, Miguel Angel Torres Avila wrote:
By the way.
I thing the Framework is well constructed, at least for development,
because I had no problems developing my app,
That means nothing.
the problems started once I tried to deploy it.
Maybe something is missing th
By the way.
I thing the Framework is well constructed, at least for development,
because I had no problems developing my app, the problems started once
I tried to deploy it.
Maybe something is missing that Ant needs for consider it as a
Framework but not WOLips.
On Aug 12, 2009, at 12
Hi Miguel,
On Aug 12, 2009, at 9:44 AM, Miguel Angel Torres Avila wrote:
Hi, David
Thanks for your patience.
You were right, the problem is in the Project.
I found the following difference between an old project and the new
one.
In the woproject folder of the old project I found this:
Hi, DavidThanks for your patience.You were right, the problem is in the Project.I found the following difference between an old project and the new one.In the woproject folder of the old project I found this: In the new one I found this:There are no ant.x files at all.Never before I had to worr
Hi Miguel,
just recently I had a similar problem. I could not make it to work the
standard way as our frameworks will be build in a custom subfolder of
the standard framework location.
This is what worked for me in our ant file for building an application
(some targets omitted):
How old is the original project that this framework is included in?
If it is too old, the build.xml file may not be using the variables in
your wolips.properties file. I ran into this with an old version of
Wonder. It was looking for a variable wosystem.root instead of
wo.system.root. Since
goofy info.plist?
ms
On Aug 11, 2009, at 2:37 PM, Miguel Angel Torres Avila wrote:
Hi, thanks Mike.
This is the content of my wolips.properties
wo.system.root=/Developer/WebObjects/Versions/WebObjects533/System
wo.user.frameworks=/Users/dev3/Library/Frameworks
wo.system.frameworks=/Develope
Hi, thanks Mike.
This is the content of my wolips.properties
wo.system.root=/Developer/WebObjects/Versions/WebObjects533/System
wo.user.frameworks=/Users/dev3/Library/Frameworks
wo.system.frameworks=/Developer/WebObjects/Versions/WebObjects533/
System/Library/Frameworks
wo.bootstrapjar=/Develo
to build, your framework has to be installed into one of the root
locations (default /Library/Frameworks, for instance)
ms
On Aug 11, 2009, at 12:28 PM, Miguel Angel Torres Avila wrote:
Hi list,
I am getting an error trying to build my project.
This is my first project using wonder and in
Hi list,
I am getting an error trying to build my project.
This is my first project using wonder and in this project I am using a
framework that I created in eclipse using the option New Wonder
Framework.
That framework is named TORATools_3_0
The error I am getting is
BUILD FAILED
/Users/
Hi!
Yes, it should be, I solved a similar problem some days ago doing
that.
Yours
Miguel Arroz
On 2008/10/30, at 18:06, Amedeo Mantica wrote:
I created a new wonder project and then I copied the build.xml file
content into the old project
it's right?
Amedeo
On 30/ott/08, at 18:50
I created a new wonder project and then I copied the build.xml file
content into the old project
it's right?
Amedeo
On 30/ott/08, at 18:50, Amedeo Mantica wrote:
Buildfile: /Users/Shared/amedeomantica/Eclipse/imarsite/build.xml
setProps:
init.build:
build.woapp:
BUILD FAILED
/Users/Shared/
Buildfile: /Users/Shared/amedeomantica/Eclipse/imarsite/build.xml
setProps:
init.build:
build.woapp:
BUILD FAILED
/Users/Shared/amedeomantica/Eclipse/imarsite/build.xml:50:
woapplication doesn't support the "stdFrameworks" attribute
Total time: 172 milliseconds
_
No, it wasn't in there, I've no copied into the Resources directory.
And now it works.
Thanks for your kind help.
Am 06.08.2008 um 16:57 schrieb David Avendasora:
I assume it's in the project's Resources directory?
If so, there is something horribly wrong with everyone's favorite
woprojec
If you're using fluffy bunny layout (/Components, /Resources, /
WebServerResources) you shouldn't be setting ANYTHING explicitly to be
a resource, you should just drop it into the Resources folder and let
it do its thing. If you're not using fluffy bunny layout, you should
be. Make a new p
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 wo
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:
On Aug 6, 2008, at 10:15 AM, Mike Schrag wrote:
This is the line 229:
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 s
This is the line 229:
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 pattern
On Aug 6, 2008, at 10:02 AM, Thierry Kramis wrote:
This is the line 229:
Where did this build.xml file come from? Is it the one that was
automatically created for you when you createed the project?
I believe the problem is that new WO and Wonder projects don't store
their source fi
This is the line 229: srcdir = "src" destdir = "bin">Here is the whole build file:
What is at line 229 of your build.xml file?
If you don't see it at the root of your project, you'll need to turn
off the filtering in Eclipse. See: http://wiki.objectstyle.org/confluence/display/WOL/WOLips-Eclipse+beginner+mistakes+and+questions#WOLips-Eclipsebeginnermistakesandquestions-Whydon
Hi all
We're trying to build our new 5.4 project on Leopard and get the
following error:
BUILD FAILED
/Volumes/harddisk/workspace/appname/build.xml:229: IO error scanning
directory '/.fseventsd'
has anyone had the same?
Regards Thierry ___
Do n
Oops, dropped in the Wonder 5.4 frameworks instead of 5.3. That took
care of everything. Sorry.
On Mar 17, 2008, at 10:49 PM, Daniel Brajkovic wrote:
I just did a brand new install of Eclipse 3.3.2, WOlips nightly
build and the latest Project wonder. I created a new project, an
EOModel, E
I just did a brand new install of Eclipse 3.3.2, WOlips nightly build
and the latest Project wonder. I created a new project, an EOModel,
EOGenerated Classes and then tried to run the Application, just to
make sure everything is OK. (BTW, I'm using WO 5.3.3)
Well, lo and behold, I get this
See
http://www.google.com/search?client=safari&rls=en&q=ant+XML+parser
+factory+has+not+been+configured+correctly:+Provider
+org.apache.xerces.jaxp.SAXParserFactoryImpl+not+found&ie=UTF-8&oe=UTF-8
Maybe a problem with the new Ant version? You could try installing
1.6.5 and using that.
Chu
I'm reading all email here regarding similar problem, but I'm still
stuck here building ant
Buildfile: /Users/Shared/amedeomantica/Eclipse/apellSite/build.xml
BUILD FAILED
XML parser factory has not been configured correctly: Provider
org.apache.xerces.jaxp.SAXParserFactoryImpl not found
T
49 matches
Mail list logo
