• 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: XcodeMigration tool and Perforce
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XcodeMigration tool and Perforce


  • Subject: Re: XcodeMigration tool and Perforce
  • From: Chuck Hill <email@hidden>
  • Date: Thu, 23 Oct 2008 13:58:10 -0700


On Oct 22, 2008, at 7:53 PM, email@hidden wrote:


-------------- Original message ---------------------- From: Chuck Hill <email@hidden>
Hi Denise,


On Oct 22, 2008, at 7:07 PM, email@hidden wrote:

I'm in the process of migrating our frameworks and apps from Xcode
to Eclipse and WOLips.  We use Perforce for SCM, so my Perforce
workspace is at a particular location on my machine (/Users/dhoward/
DevP4) and Xcode is fine with that.  I need my Eclipse workspace for
a given project to continue talking to Perforce.  I already
discovered that the /tmp/migrations directory where the
XcodeMigration tool constructs its Eclipse versions of Xcode
projects is not a good final destination.  How can I do this?  Must
I reorganize the file structure of the project as it is in Perforce
now?


I strongly suggest that you do the opposite: reorganize the structure
of the project in Perforce to match the Eclipse project.  The layout
is a convention supported by the standard Ant builds.  You can change
it, but you are going to be working against the tools.

We actually use ant to do our builds, both for local testing and for deployment. Perhaps I just need to somehow ensure that Eclipse uses the ant build scripts we have already, and the project structure will be okay as it is?


You can set Eclipse up to do all builds with Ant and not the Incremental Builder. I do this as I want to use a code generation tool. I do NOT recommend this unless you get real value from doing this. Avoiding a re-org in Perforce is NOT real value. The incremental builder is much faster and gives a better development experience. And even using all Ant builds, I am still moving my structure toward the conventional structure from a modern WOLips. I expect that this convention will be more and more supported by the tools and there are benefits to adhering to it.


Chuck


-- 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@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: XcodeMigration tool and Perforce
      • From: Mike Schrag <email@hidden>
  • Prev by Date: Re: [SOLVED] How do I add user Info in nightly's entity modeler?
  • Next by Date: Re: help - subcomponent won't update
  • Previous by thread: Re: XcodeMigration tool and Perforce
  • Next by thread: Re: XcodeMigration tool and Perforce
  • Index(es):
    • Date
    • Thread