Re: Two questions about latest build system
Re: Two questions about latest build system
- Subject: Re: Two questions about latest build system
- From: Chuck Hill <email@hidden>
- Date: Sun, 23 Nov 2008 09:41:44 -0800
On Nov 23, 2008, at 2:46 AM, Paul Hoadley wrote:
Hello,
I'm running Eclipse 3.4.1, and WOLips nightly 3.4.5561. I have two
questions about the new build system:
1. I have an application project that depends on a framework
project (actually, more than one). I'm back to using the
incremental build system for development, in which case it seems
like (after running Project > Clean... on everything) it's
sufficient to run Project > Build Project on the application.
Everything else builds, and the application runs. Using Ant to
create a WOA (or WAR) for deployment, though, I seem to need to run
the 'install' target on all the dependencies (and on any of their
dependencies, in the correct order).
Mike was grumbling about this a while ago. He may have something up
his sleeve....
So here's my (two part) question: I take it WOLips is using ~/
Library/Application Support/WOLips/wolips.properties now---can I
delete ~/Library/wobuild.properties?
Yes. Can and should (to avoid future confusion).
The 'install' target puts the framework in ${wo.local.frameworks} (/
Library/Frameworks)---I don't really need them available outside
Eclipse on the dev machine, would they be better off in $
{wo.user.frameworks}, and if so, can I get them there without
modifying build.xml? (If they're actually better off in /Library/
Frameworks, tell me.)
Yes, that is where I put them. You can just edit wolips.properties
and change wo.local.frameworks to
wo.local.frameworks=/Users/paul/Library/Frameworks
I don't think that will cause problems with the same definition as
wo.user.frameworks, but it might. I have a common (shared) build file
and I changed it there.
2. This application also depends on two plain-Java JAR projects in
the same workspace. I've got those JARs listed under "Referenced
Libraries", but that doesn't seem to get them copied into the
deployment products. Copying the JARs into Libraries does,
obviously, but then I'll have to remember to update those copies
every time I change their source. Is there a better way to
reference JAR projects?
That I don't have an answer for.
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