• 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: Eclipse builds - force custom framework selections to be packaged
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Eclipse builds - force custom framework selections to be packaged


  • Subject: Re: Eclipse builds - force custom framework selections to be packaged
  • From: David Avendasora <email@hidden>
  • Date: Thu, 15 Mar 2012 23:26:25 +0800

Hi Daniel,

You seem to be working really hard to find a complex solution to a simple problem.

1) Why not just include _all_ the depended-upon frameworks in your app's .classpath? In other words, The App's class path has all of the WOFramework entries for the frameworks it depends upon, even if they are 2- or 3- or n-times removed from the App itself? They are just lines of text in 1 file. Other than duplication, which you are doing anyway by creating a secondary classpath file what is it you are trying to avoid? By including them all in the .classpath, both WOJenkins and WOLips would know what to do when you build.

2) If you are using Jenkins, why do you still use WOLips to build your App? WOLips does not _ever_ build your dependencies for you. You will always have to build them one at a time, in dependency order and you run the risk of forgetting a dependency and having WOLips build with an old version. If you've got Jenkins working, by hook or by crook, then _stop_ using WOLips to trigger Ant builds. It's like still keeping a MySQL version of your database synchronized with your production FrontBase database.

3) I think you already have this set, but make sure you have the Embed System and Local frameworks turned on in the WOLips build preferences, because that's what tells Ant to actually copy the frameworks denoted by the WOFrameworks entries into the app. Without those set, Ant will just use those entries to resolve dependencies for compiling. If those frameworks aren't available on your server, then your apps won't run.

Dave

On Mar 15, 2012, at 9:07 AM, Daniel Roy wrote:

Thanks Pascal for the ideas.  I already have something working in Jenkins where I modified the setupWorkspace shell script from WOJenkins to take parameter that is a custom classpath filename (which resides in the relevant project).  This custom classpath contains the required custom Frameworks, and compiles without issue, but then I'm back to the ant build problem where the ant build only includes the files in the original .classpath file, since this is hardcoded in the related WOLips classes.

I'll keep digging, and if I find any solutions I'll post back to the list :)

-Daniel


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: Eclipse builds - force custom framework selections to be packaged
      • From: Lachlan Deck <email@hidden>
References: 
 >Re: Eclipse builds - force custom framework selections to be packaged (From: Daniel Roy <email@hidden>)
 >Re: Eclipse builds - force custom framework selections to be packaged (From: Pascal Robert <email@hidden>)
 >Re: Eclipse builds - force custom framework selections to be packaged (From: Daniel Roy <email@hidden>)

  • Prev by Date: Re: Community Roadmap for 2012
  • Next by Date: Re: WOCommunity Apple Developer Account
  • Previous by thread: Re: Eclipse builds - force custom framework selections to be packaged
  • Next by thread: Re: Eclipse builds - force custom framework selections to be packaged
  • Index(es):
    • Date
    • Thread