• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Switching from XCode to WOLips: ressources headaches
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Switching from XCode to WOLips: ressources headaches


  • Subject: Re: Switching from XCode to WOLips: ressources headaches
  • From: Timo Hoepfner <email@hidden>
  • Date: Wed, 16 Aug 2006 14:55:18 +0200


Am 16.08.2006 um 14:30 schrieb François Reboursier:

	Hi,

Following the recent buzz, I've decided to bite the bullet and migrate my project from XCode to WOLips (the project is fairly large; 500+ java files, many ressources, external frameworks and jars, etc-etc)

I've run into the following issues:

- to add a ressource to the build, I right-click on the ressource >> WOLips Tools >> Include as a ressource
Following this, is there a way to check wich ressources are included, and wich are not? (like XCode's build inspector window)

You can inspect the configured patters this way:

-Activate "Package Explorer" view
-Click the "down triangle" and select "Filters..."
-Uncheck "woproject (WOLips)" (it's at the very bottom for me)
-"OK"
-Now you can see a "Folder" named "woproject" at your project root. In it, you will find e.g. "resources.include.patternset". Double- click it to see/modify the patterns


- Only the 'index.plist' file of my EOModel is copied to the build ressources. I could manually add the others .plist and .fspec files, but I don't want to do this manually every time I add an entity. Is there a way to automate this ?


Probaby a problem with the patternsets above. my "resources.include.patternset" includes the entry


**/*.eomodeld/

If that's missing (I guess the trailing slash is important), that will likely cause the problem you are describing.


- When the project is built, no executable is created within the .woa bundle, but the project can be run nevertheless (this one is really weird... )


That's ok. the "build" folder is only for use by eclipse. If you want to deploy, you'll have to use ANT:


-configure the filter (like above) to show the "build.xml" file
-Add the ANT view: Menu->Window->Show View->Other, Select Ant/Ant from there
-drag the build.xml form the Package Explorer to the Ant View
-To build a deployable App, double-click the "build" task. It'll create a deployable WOA in the dist folder (probably also hidden by the default filter settings).


Any help will be greatly appreciated: I've been trying to make this work for 2 days...



HTH,

Timo

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Switching from XCode to WOLips: ressources headaches
      • From: François Reboursier <email@hidden>
    • Re: Switching from XCode to WOLips: ressources headaches
      • From: Mike Schrag <email@hidden>
References: 
 >Switching from XCode to WOLips: ressources headaches (From: François Reboursier <email@hidden>)

  • Prev by Date: Switching from XCode to WOLips: ressources headaches
  • Next by Date: Re: Switching from XCode to WOLips: ressources headaches
  • Previous by thread: Switching from XCode to WOLips: ressources headaches
  • Next by thread: Re: Switching from XCode to WOLips: ressources headaches
  • Index(es):
    • Date
    • Thread