Re: Two questions about latest build system
Re: Two questions about latest build system
- Subject: Re: Two questions about latest build system
- From: Mike Schrag <email@hidden>
- Date: Sun, 23 Nov 2008 16:42:25 -0500
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....
I spent some unquality time with both Maven and Ivy recently and I'm
completely put off by both of them ... I am looking around at several
other options either for drop-in replacments or for inspiration for a
better solution (including the Ruby Gems system, which seems to "just
work" with not much pain, although it is not a exactly solving the
same problem as maven). I pretty steadfastly maintain that build
files are programs and for some reason all of the Java answers to this
problem are a combination of huge XML files and Java plugin classes,
which, IMO, are just a really lousy way to manage this process. I'm
far more intrigued by Ruby's answers to some of these problems (rake,
gems, etc), and buildr is on my "to review" list as well). So I don't
exactly have anything up my sleeve (yet) but I'm definitely looking at
the problem. I refuse to believe that this problem has to has such a
complicated solution.
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.
The default build files are written to include all jars in the
Libraries folder for deployment. Having them in the eclipse build
path (currently) is not enough (though if the jars are inside your
project, there's no particular reason we COULDN'T do this in our
custom ant file, i think).
I'm not exactly catching what your problem is, but it sounds to me
like you're saying you have another project that you deploy inside
your app as a binary jar built from your source. I usually recommend
just making that a framework of its own. Obviously Maven and friends
address this problem, though your mileage may vary.
ms
_______________________________________________
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