On Mar 15, 2008, at 10:06 AM, Archibald Singleton wrote:
> Hi Bill,
>
> On 14 Mar 2008, at 22:44, William Hatch wrote:
>
>> Thanks Archibald,
>>
>> Let me attempt to clarify:
>>
>> I have a project that's dependent on some third party frameworks,
>> in this case they happen to be Wonder frameworks; specifically
>> ERJars, Ajax, and a few other. I"m just using the Wonder Ajax
>> stuff, not a full blown Wonder app. I have the source Wonder
>> projects referenced in my workspace, but do not reference the
>> Wonder projects in my project; instead I just include the actual
>> installed framework on my build path. After updating the Wonder
>> source and reinstalling the frameworks, my project now complains
>> that it can't find a specific jar. I believe that this jar has
>> been updated and really shouldn't need to be referenced any longer
>> as it appears that there is a newer version of this jar, which is
>> also now referenced under the WebObjects Frameworks Library and is
>> also available on the file system. If I edit the WebObjects
>> Framewors library entry under Build Path -> Configure Build Path,
>> I can remove all the references to ERJars, Ajax, ERExtensions ,
>> and WOExtensions and this pesky reference will go away (and
>> obviously I'll have a bunch of other problems now). But when I add
>> the ERJars reference back in, the missing Jar is once again
>> referenced and I"m unable to build again. Also, if I create
>> another project with a dependency on ERJars.framework, I"ll get
>> the same error relating to icu4j_2_8.jar. I thought initially that
>> all I really needed to do was somehow get the projects build path
>> to stop referencing that specific jar, and I was unable to do that
>> by configuring the build path with conventional means, so I
>> thought there might have been some file that I could edit directly
>> that would allow me to remove the dependency. After further
>> investigation, I think this problem is due to some oddness with
>> ERJars; either with the source or due to some bug on my local
>> system. I'll do some more digging and post this to the Wonder list
>> or file a bug if I still can't figure it out.
>
> Very strange indeed. If I understand correctly, even if you create
> a new project from scratch, and link it to the ERJars frameworks
> and then you build this project, you get the missing jar error?
Yes, the missing jar is included in the build path when linking to
the ERJars.framework in /Library/Frameworks/ in any app that I try to
include ERJars in. I was installing this from Source using Keiran's
example script for updating source, removing existing frameworks and
finally rebuilding and installing from updated source. The source
frameworks in ~/Roots/ look good; the info plist doesn't mention the
missing jar, although I'm not sure exactly what impact that file has
on anything. I did not try (because I just thought of it now;-)
referencing the jar only version from /Library/WebObjects/lib/ to see
if it still gave me the bad reference. Next update when this happens....
I eventually relented and just downloaded the binaries and wacked/
installed ERJars only. It's not a big deal; just trying to learn more
about how both WOLips and Wonder work and thought perhaps there was a
deeper messier access point to build/class path configuration.
>
> Have you tried cleaning up all the projects in Eclipse (Projects ->
> Clean...) or at least the ERJars project?
> I sometimes need to do that to get rid of weird errors in Eclipse /
> WOLips especially after updating my WOnder sources.
Yes, I tried cleaning and manually rebuilding and even relaunching
Eclipse. No love...
>
>
>> If I look at the source for ERJars in the workspace, there's a
>> Libraries folder which shows as empty in Package Explorer.
>> However, there are four jars in it on the file system; and the one
>> that my project complains about missing is not there and it's not
>> referenced in the ERJars project Build Path. I'm also not able to
>> build this ERJars project with either Ant or Eclipse.
>
>
> Your ERJars setup sounds identical to mine. I don't see the *.jar
> files in WOLips Package Explorer either, I thought it was due some
> filter settings but a quick look didn't not reveal any *.jar
> specific filter, the 4 jars are there in the Finder though and they
> are referenced from the
Yeah, I'd think the directory contents would be viewable, or at least
indicate there's contents in that directory; not sure what the
intention is there.
>
> What do you mean by not being able to build ERJars? In my case, in
> Eclipse everything is build automatically incrementally (I think
> that's the default) and I'm not sure the Ant building does much
> since there's nothing to compile (the ERJars.jar is essentially
> empty), do you get an error message from Ant?
I'm new to Wonder and am not sure about how the ant scripts are set
up - per project/framework/ or the entire collections, or a
combination of both( more likely). Yes, I could look I suppose lol. I
just noticed that there was no ant script in the project source, but
there was a build.properties. I was using "build" in a generic sense;
I guess more accurate would be "install";-) Anyway, my first thought
was to run the ant install task for that one project as a first step
to fixing my underlying problem, which would seem logical. The only
thing I was able to do was generate an new ant script, which was not
appropriate for the project. Not wanting to spend more time on it
yesterday and desiring to get back to real code and productivity, I
opted for the easy way out this time. I think Mike is right, this is
probably more a Wonder issue, or maybe even some little bug with
Keiran's script or a problem on my rig. Problems are always a good
teacher;-)
Bill
>
> = tmk =
This archive was generated by hypermail 2.0.0 : Sat Mar 15 2008 - 20:26:12 EDT