• 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: Exception only when framework is embedded
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Exception only when framework is embedded


  • Subject: Re: Exception only when framework is embedded
  • From: Florijan Stamenkovic <email@hidden>
  • Date: Fri, 08 Aug 2008 20:27:29 -0400


On Aug 08, 2008, at 11:46, Mike Schrag wrote:

You want them running through the normal eclipse java launching process so you can do hot-code replacement, etc, when it runs in debug mode. Plus we get a lot of behaviors for free by piggy- backing on the Java launching process.

I see your point.

<mini-rant>If it doesn't work like in deployment like it does in Eclipse it's either a failure of the build system which (should be replaced|is being replaced) or it's a failure of WOBoostrap which (should be replaced|is being replaced).

Exactly my point. It wasn't too hard to bump into this as soon as I started fiddling with the build process. It is fairly easy to kick the two building systems out of sync.


There's no reason why all the features that Eclipse provides in terms of dependencies and classpath ordering should not be fully supported during build and deployment.

:D Sure there is. WO doing it's own thing. If it wasn't, WOProject would not be necessary.


Anjo and I have talked about this several times that the framework Info.plist needs to support the definition of framework dependencies and/or its internal jar ordering, which should be interpreted by a replacement WOBootstrap to dynamically build what is currently the MacOSClassPath.txt file, which I personally despise. In general, the WO build process and deployment process is way too complicated and nasty, and it would be nice to have the tools make this suck less.

Well, I like the WOProject ant stuff (however I at times passionately hate ant). If one counts the fact that it is imitating a very different build structure then java normally does. And I like the Eclipse goodness too, I guess :) It all seems, as well as one could expect (and when not the community is great about helping out), it would just be nice to be able to define a launch config that does the isolated end woa launch.


Also, please don't think that I am not appreciative of WOLips. It rocks. If I just think back of Xcode, well, I feel like I am in WO development heaven.

F

then again, I've been slamming my head for the last week against a build process. I have not done any relevant work on the apps themselves. That is just bad productivity, regardless of how intriguing it might have been :)
_______________________________________________
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: Exception only when framework is embedded
      • From: Mike Schrag <email@hidden>
References: 
 >Exception only when framework is embedded (From: Art Isbell <email@hidden>)
 >Re: Exception only when framework is embedded (From: Florijan Stamenkovic <email@hidden>)
 >Re: Exception only when framework is embedded (From: Mike Schrag <email@hidden>)

  • Prev by Date: Re: Inheritance and relationships
  • Next by Date: Re: Inheritance and relationships
  • Previous by thread: Re: Exception only when framework is embedded
  • Next by thread: Re: Exception only when framework is embedded
  • Index(es):
    • Date
    • Thread