Hmm, I thought I had checked that and was still getting the error.  However, in 
the interim I reverted my build back to a previous state, and I was able to run 
again from within Eclipse.  However I was then getting an error when trying to 
install my Frameworks using WO Ant Tools->Install. 

More specifically, I'm using Lion/Eclipse3.7.1/Webobjects5.4.3, and the method 
described here for my WOLips intallation:

http://wiki.objectstyle.org/confluence/display/WOL/Using+WOLips+With+Multiple+Versions+of+WebObjects

but my framework build script wasn't picking up where to install my framework 
project, and continued to try to install it in /Library/Frameworks.

After looking more closely at my build file, I noticed the variables used in it 
weren't matching the variables used in my wolips.properties files.  e.g. The 
build file was using:

wo.wosystemroot
wo.wolocalroot

when my properties files were using:

wo.system.root
wo.local.root

After updating my build file to match, then the installation worked.  And 
honestly, this was the original problem I had that started me hacking at things 
in the first place that ended up with the previous jar file error.  

Now, I have to ask, does anyone have any idea how these files might have gotten 
out of sync in the first place so perhaps I can avoid such a scenario in the 
future?  I'm guessing it had to do with my recent update to the lastest Eclipse 
and WOLips builds and/or to Lion, since that's about when the build error 
started occurring originally.

Thanks!
Jeff

On Nov 21, 2011, at 2:06 PM, Chuck Hill wrote:

> Are they marked as exported?
> 
> <PastedGraphic-1.pdf>
> 
> 
> On 2011-11-19, at 8:59 PM, Jeff Schmitz wrote:
> 
>> Hello list,
>> 
>>   I have Eclipse projects that consist of a Wonder Application that 
>> references a Wonder Framework.  Everything compiles without error, including 
>> NBConfiguration which is resident in the Wonder framework project, but when 
>> I run I'm getting the below error about not being able to resolve a 
>> referenced import.  The jdom.jar file, which contains the class 
>> JDOMException, is in my project build path (otherwise there would be 
>> compilation errors).  Obviously something is out of whack, but I'm not sure 
>> where to look.  Any help would be mightily appreciated.
>> 
>>      The import org.jdom cannot be resolved
>>      The constructor NBConfiguration() refers to the missing type 
>> JDOMException
>>      JDOMException cannot be resolved to a type
>> 
>> [2011-11-19 22:45:19 CST] <main> java.lang.Error: Unresolved compilation 
>> problems: 
>>      The import org.jdom cannot be resolved
>>      The constructor NBConfiguration() refers to the missing type 
>> JDOMException
>>      JDOMException cannot be resolved to a type
>> 
>> _______________________________________________
>> 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/chill%40global-village.net
>> 
>> This email sent to [email protected]
> 
> -- 
> Chuck Hill             Senior Consultant / VP Development
> 
> Practical WebObjects - for developers who want to increase their overall 
> knowledge of WebObjects or who are trying to solve specific problems.    
> http://www.global-village.net/products/practical_webobjects
> 
> 
> 
> 
> 
> 
> 

 _______________________________________________
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]

Reply via email to