On Jul 17, 2007, at 4:15 PM, Joshua Archer wrote:
> On Jul 17, 2007, at 3:40 PM, Chuck Hill wrote:
>
>>
>>>>>>> which it never used to do (and which is set in the project
>>>>>>> settings).
>>>>>>
>>>>>> Which "project settings"?
>>>>>
>>>>> Sorry, not being precise in my language. I meant the Properties
>>>>> settings for 'WOLips Build'
>>>>>
>>>>> <Picture 1.png>
>>>>
>>>> That looks OK, assuming your Application.java is not in a package.
>>>
>>> Looks like the Application.java *is* in a package:
>>>
>>> package org.nmc.pachyderm.authoring;
>>>
>>> Guess I should pull that, and move Application.java to the
>>> default package?
>>
>> Having classes in the default package is just a Bad Idea. I don't
>> know how that setting got out of synch with reality, but that is
>> at least part of your problem. Add the package in there.
>
> So wait, Application.java *should* be in a package? I'll add it
> back in.
As of Java 1.6, packages are required. I stopped using the default
package a version or two back.
>>> I had added the jar to the build path in the 'Libraries' tab, and
>>> the framework to the "required projects on the build path" under
>>> Projects. I've removed them from the latter, and things are
>>> moving along differently now...
>>
>> Um, no. You should check / select the framework in the WebObjects
>> Frameworks library and add the project in Eclipse to Required
>> Projects.
>
> That's what I meant to say. I added the projects to the Required
> Projects, and I checked the frameworks in the WebObjects Frameworks
> library, which appears to index the jars inside the frameworks.
Make sure the projects come before (above) the frameworks on the
Order and Export tab.
Chuck
--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
This archive was generated by hypermail 2.0.0 : Tue Jul 17 2007 - 19:19:23 EDT