Someone please help me walk through this -

I can run the app in eclipse just fine.

I use new Ant 1.8 to build to install, and unpack the tar ball in /tmp

unlike on my server, the app runs, and reports a likely candidate for a clue:

Exception in thread "main" java.lang.NoClassDefFoundError: 
er/sync/api/ERXSyncAuthenticator

this is an addition since last deployment - I added ERXSync although I'm not 
yet using it.

I figure while running Eclipse, my frameworks are from the wonder frameworks 
there right in Eclipse? I know there are also copies of Frameworks from a build 
of Wonder which at some point I put into my /Library/Frameworks somewhere.

I notice the ERSync framework is indeed in my app bundle

Contents/Frameworks/

So, I'm unable to run on my server - no error is reported at all.

On my developer machine, it runs normally in Eclipse.

On my developer machine, the unpack of the tarball runs with that error 
regarding ersyncauthenticator

I also notice ERXSyncAuthenticator.class is my contents resources.

Do I need to update those /Library/Frameworks on my developer and server system 
even if I'm bundling frameworks in my app?

I can't figure what I've got hosed here.

Any Ideas?


On Aug 1, 2012, at 11:18 AM, Tim Worman <[email protected]> wrote:

> Jesse:
> 
> No, I haven't seen what you're experiencing here.
> 
> Tim
> UCLA GSE&IS
> 
> On Jul 31, 2012, at 4:38 PM, Jesse Tayler <[email protected]> wrote:
> 
>> 
>> Thanks again Tim,
>> 
>> This seems to be related -
>> 
>> I'm unable to launch the newly built app on my server, even though the new 
>> ant build seems to work etc.
>> 
>> If I just launch at the command line I can see the new app report output 
>> along with the older install - the older install launches just fine, the new 
>> install fails without report but for a NEXT_ROOT variable.
>> 
>>> WOMan.woa/WOMan
>> WOMan: NEXT_ROOT environment variable is not set! Terminating.
>> 
>> At first I thought -- ah, what's this missing NEXT_ROOT
>> 
>> But I see the app normally has that as a first line, but then quickly move 
>> through
>> 
>>> WOMan.woa/WOMan
>> WOMan: NEXT_ROOT environment variable is not set!
>> Reading UNIXClassPath.txt ...
>> Launching WOMan.woa ...
>> ...
>> and continues launch.
>> 
>> 
>> obviously, the app launches as I'd expect on my developer machine.
>> 
>> did you run into any of that Tim?
>> 
>> anyone have an idea?
>> 
>> 
>> 
>> On Jul 31, 2012, at 3:32 PM, Tim Worman <[email protected]> wrote:
>> 
>>> The build failure is not due to the 'includeantruntime' error. The build 
>>> failure is due to not being able to write to the framework directory as set 
>>> in ~/Application Support/WOLips/wolips.properties.
>>> 
>>> If the directory doesn't exist, you do need to create it. If it isn't 
>>> writeable, the ownership/permissions must be changed.
>>> 
>>> Tim
>>> UCLA GSE&IS
>>> 
>>> On Jul 31, 2012, at 12:12 PM, Jesse Tayler <[email protected]> wrote:
>>> 
>>>> I'm fairly certain you do NOT need to create any directory -- that's 
>>>> simply an end-failure result of the build termination.
>>>> 
>>>> I can see also some people outside the WO community having this trouble 
>>>> and ironically, they too simply "added" that property to their build.xml 
>>>> but I don't see how they did it and I must be doing it wrong or something.
>>>> 
>>>> So, either I'm confused or I'm doing it wrong -- but it's not yet working 
>>>> for me.
>>>> 
>>>> I don't really understand how the build.xml works so maybe I'm not setting 
>>>> the environment variable properly?
>>>> 
>>>> my build.xml now starts off like this:
>>>> 
>>>> <project name="WOMan" default="build" basedir=".">
>>>>    
>>>>    <presetdef name="javac">
>>>>            <javac includeantruntime="false" />
>>>>    </presetdef>
>>>>    
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Jul 31, 2012, at 2:25 PM, David Holt <[email protected]> wrote:
>>>> 
>>>>> I am having the same issues. And no, I cannot create the directory from 
>>>>> the command line. What should the permissions be?
>>>>> 
>>>>> David
>>>>> 
>>>>> 
>>>>> On 2012-07-23, at 10:22 AM, Henrique Gomes <[email protected]> wrote:
>>>>> 
>>>>>> 
>>>>>> On Jul 23, 2012, at 4:59 PM, Theodore Petrosky wrote:
>>>>>> 
>>>>>>> 
>>>>>>> BUILD FAILED
>>>>>>> /Users/asacksadmin/Documents/workspaceAS_II/ASPOOpenProjectsFW/build.xml:57:
>>>>>>>  Directory /Library/Frameworks/ASPOOpenProjectsFW.framework creation 
>>>>>>> was not successful for an unknown reason
>>>>>>> 
>>>>>>> Total time: 3 seconds
>>>>>>> 
>>>>>>> ------------------
>>>>>>> for "Unknown reason".
>>>>>> 
>>>>>> Can you create de dir on the command line?
>>>>>> 
>>>>>> $ mkdir  /Library/Frameworks/ASPOOpenProjectsFW.framework 
>>>>>> 
>>>>>> HG
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>> Webobjects-dev mailing list      ([email protected])
>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/programmingosx%40mac.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:
>>>>> https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.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:
>>>> https://lists.apple.com/mailman/options/webobjects-dev/lists%40thetimmy.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:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to