• 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: Frameworks and versioning
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Frameworks and versioning


  • Subject: Re: Frameworks and versioning
  • From: Tonny Staunsbrink <email@hidden>
  • Date: Thu, 5 Jan 2006 16:18:14 +0100

Hi All

I'm don't think there is a "right" answer on this issue. Embedding your frameworks solves the problem of breaking API or introducing bugs. On the other hand it makes it cumbersome to deploy bugfixes to frameworks (when multiple apps are using the frameworks). It's the same discussion as dynamic vs. static linking - the same pros and cons (well, almost) - and i think it's worth to note that dynamic linking is used alot.

I prefer to have my frameworks deployed seperately from the applications (due to the ease of deploying updates). The risk of breaking API should be a matter of developer discipline ;-) and sometimes biting the bullet (rebuilding and redeploying every app when some used API fetaure is completly removed).

Cheers
/Tonny
On Jan 5, 2006, at 2:40 AM, Chuck Hill wrote:

Hi Lachlan,

On Jan 4, 2006, at 3:56 PM, Lachlan Deck wrote:

I prefer to use the classpath to control versions.
I long ago abandoned /Library/Frameworks and /Library/WebObjects/ Extensions for deployment. As soon as you have multiple deployed apps with multiple framework / jar versions you have a mess.

Hmm.

I either do what Guido said and package all this in the .woa bundle, or have directories for these specific to one or a few apps. Thus I can update one without fear of altering others.

Aha, a little archive search: the Project Wonder perl script seems to be the best fit for this.
http://cvs.sourceforge.net/viewcvs.py/*checkout*/wonder/Wonder/ Utilities/woaFrameworkMerger/Readme.html


perl. Don't much care for the taste of perl :-), but it does what I was trying to describe. The only possible addition is to also copy the contents of /Library/WebObjects/Extensions to
App.woa/
Contents/
Extensions/


That way the only shared jars are the JDBC etc in /Library/Java/ Extensions.

Chuck

--
Coming in 2006 - an introduction to web applications using WebObjects and Xcode http://www.global-village.net/wointro


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:
40phonofile.dk


This email sent to email@hidden


_______________________________________________ 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: Frameworks and versioning
      • From: Arturo Perez <email@hidden>
References: 
 >Frameworks and versioning (From: Lachlan Deck <email@hidden>)
 >Re: Frameworks and versioning (From: Chuck Hill <email@hidden>)
 >Re: Frameworks and versioning (From: Lachlan Deck <email@hidden>)
 >Re: Frameworks and versioning (From: Chuck Hill <email@hidden>)

  • Prev by Date: Problems with WOFileUpload over DirectAction and large files
  • Next by Date: Re: Frameworks and versioning
  • Previous by thread: Re: Frameworks and versioning
  • Next by thread: Re: Frameworks and versioning
  • Index(es):
    • Date
    • Thread