Re: WO Framework build ant woes
Re: WO Framework build ant woes
- Subject: Re: WO Framework build ant woes
- From: Florijan Stamenkovic <email@hidden>
- Date: Fri, 11 Jul 2008 11:28:08 -0400
Yeah, that chimes with my own conclusions about it, all the fuss
inside seems to be primarily classpath oriented. Any idea then why
is it there? Why not simply rely on Eclipse's compiling?
For deployment, I do a deep clean and build totally from the
command line. It also allows you to check out and build on the
server (deployment, test, continuous integration, whatever) without
needing GUI access to Eclipse.
Ah, OK.
Short is good. I have tried to apply the DRY principal to my Ant
files.
Admirable :P
May I ask what does project.classpath resolve to? Does it tap into
Eclipse's project cp stuff, or?
<snip>
These have to be maintained manually when the classpath is updated
in Eclipse. This is just a temporary measure until Mike's
Classpath Magic is ready. BUT it is WAAAAY better than the
woproject/ madness. Thanks go to Anjo for this.
Yeah, well, so much about DRY. Mike Magic starts to sound really
appealing :)
Thanks a lot for all the info... There just does not seem to be a
really *good* way to do this. And my server side WO stuff is really
simple, the client apps are complicated, but do not use ANT at all,
only Eclipse's stuff. YAY! I feel sorry for people who have to
maintain really complicated WO projects. *shrug*
F
_______________________________________________
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