Le 09-11-23 à 14:05, Calven Eggert a écrit :

hmmm, I did that, checked off the local/system frameworksin WOLips Deploy and the install includes all the libraries except mine. :-(

Looks like the Build path stuff is wrong. In the Projects tab I include my project folder and in the Libraries Tab I added myframework.jar file from the /Library/Framework/ myframework.framework/Resources/Java/ folder. This can't be right because you say that I don't need to include my /LibraryFramework any more.

No need to include your framework as a project in the Build Path, you should add it as a WebObjects Library Framework, just like other frameworks instead. In 3.4, this is where the major change was done. So the "new" steps is to include your framework as a Library Framework and if your framework source project is open in Eclipse, WOLips will pick up the source, if your framework project is closed in Eclipse, it will pick up the one in /Library/Frameworks.

BUT you do need to install your framework in /Library/Frameworks (on your development machine) before you build your app, or else you have an old version of your framework (or no framework at all) in your app. When I said you don't need to worry about /Library/Frameworks, I meant on the deployment side, for development you still need it.

So the steps is : when you are ready to deploy, run a Ant install on your framework, after run the Ant install on your app and your framework should be embed in your app just like Wonder and the WO frameworks. I think David A. covered this in his WOWODC West session.

hmmm, how to I make this right?



On 2009-11-23, at 1:42 PM, Pascal Robert wrote:

Embed your frameworks (and any other frameworks) into your app and you won't have to worry about /Library/Frameworks anymore. Right- click on your project name -> Properties, and in the WOLips Deploy, check the boxes to say that you want to embed local and system frameworks. Run the ant install again and your app will now have all needed frameworks inside itself.

Ah, the Project.name= entry was NOT filled in in the build.properties file and so that fixed the problem of my Framework not appearing. Thanks for that.

The problem now is that installing my app on the server can't find the framework and this time IT IS located in /Library/Frameworks because I put it there on the server. I know this because I get the error "java.lang.NoClassDefFoundError" for a class in my framework.

My original WO application projects are from a long time ago and so I suspect that this may be the problem. I am using build.xml files from newly created WO projects in eclipse. What should I check for in my build settings to make sure the WO app is connecting to the framework properly? (The app runs no problem from eclipse)

Current configuration:
Eclipse 3.4.2
WO5.4.3
WOLips from here(http://webobjects.mdimension.com/wolips/stable)
Java 1.5
Wonder 54 binaries


Calven





On 2009-11-23, at 12:07 PM, David LeBer wrote:

On 2009-11-23, at 11:51 AM, Calven Eggert wrote:

I just updated to Snow Leopard last week and I'm having trouble building my WO framework and projects.

The first build I attempt is my framework. It builds with no errors, although lots of warnings like ...should be parameterized, but when I do the install the framework is NOT in the /Library/Frameworks folder. It is in the /Build folder, but looking in there, in the .framework/Resources/Java folder the .jar is not there. hmmm

Are you sure?

Did you check the /Library/Framworks with the terminal (ls -al)? You might find a .frameworks folder with the correct creation/mod time. That would mean that you are missing the project.name= entry in your project's build.properties.

If that is the case, how old was the WOLips you were updating from?



Here is the output:

Buildfile: /Users/ceggert/Projects/COREFW/build.xml
init.properties:
init.install:
init.build:
compile:
build.woframework:
[woframework] Installing  in /Library/Frameworks
javaclient:
install:
BUILD SUCCESSFUL
Total time: 873 milliseconds

I do have the wolips.properties in ~/Library/Application Support/ WOLips.

I have read the last two articles here (http://wolips.blogspot.com/ ) but I can't say i fully understand it all.

Any suggestions?

Calven

_______________________________________________
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/dleber_wodev%40codeferous.com

This email sent to [email protected]

;david

--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site:   http://codeferous.com
blog:   http://davidleber.net
profile:        http://www.linkedin.com/in/davidleber
twitter:        http://twitter.com/rebeld
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org







_______________________________________________
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/probert%40macti.ca

This email sent to [email protected]

----
Pascal Robert
[email protected]

AIM: MacTICanada
Twitter : MacTICanada
LinkedIn : http://www.linkedin.com/in/macti



----
Pascal Robert
[email protected]

AIM: MacTICanada
Twitter : MacTICanada
LinkedIn : http://www.linkedin.com/in/macti

 _______________________________________________
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