I agree that it can be a pain. Currently, I only maintain 2 applications with the appfuse directory structure - one is appfuse, the other is struts-resume. It can certainly become cumbersome to keep these two applications in synch. However, I like being able to download appfuse and nothing else to get going on an application. Maintaining classpaths in Eclipse can be a pain, but since it only takes a few seconds to update, I'm not too concerned with this.

The best bet for you, on your projects, is to try playing with different scenarios and see if you can come up with something better than the current solution. I've also thought of using Maven, I just haven't got time to poke around and try to get AppFuse running with it - and even if I did, I wouldn't want to break the existing Ant functionality - if it ain't broke, don't fix it! ;-)

HTH,

Matt

On Tuesday, October 21, 2003, at 10:11 AM, [EMAIL PROTECTED] wrote:

Hi Matt,

Last night I decided I would spend the time to start using Ant, Hibernate,
and XDoclet. Better late than never! :) Just never enough time to do it
all.


Anyway, from your blog entries about AppFuse and Eclipse, I figured that
you had probably developed it in Eclipse. That being the case, I pretty
confident that I could pick and choose the pieces that I needed from
AppFuse to insert into my own project. After a couple of false starts, I
was able to figure out the surface relationship between the build.xml,
properties.xml, and lib/lib.properties. So, thanks to you, I learned a lot
in a very short period of time. :)


After I got Ant to build my hbm files, I couldn't help but wonder about the
fact that I now had to maintain a classpath in Eclipse and quite a few in
the properties.xml file. For one project this doesn't seem too bad;
however, when I start using this build process on multiple projects it
seems like it can very quickly get out of hand. Is this really how you
suggest managing multiple projects? Do you really copy the libs to each
project or do you have a central repository that you manage them from? And
do you really manage the build script on a per project basis? It seems
generic enough that it should also be able to be managed centrally. And
what about the Maven that you have off the root of the project? Do you
somehow have it manage the lib.properties for you? Finally, since I am not
going to be in a position, like you, where I might be using multiple IDEs,
why don't I just buy into the Ant classpath features that Eclipse has built
into it?


Thanks for providing AppFuse!  It has really been an educational  time
saver!

Andy

**********************************************************************
This message is intended only for the designated recipient(s).  It may
contain confidential or proprietary information and may be subject to
the attorney-client privilege or other confidentiality protections.
If you are not a designated recipient, you may not review, use, copy
or distribute this message.  If you receive this in error, please
notify the sender by reply e-mail and delete this message.  Thank you.

***********************************************************************



------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Struts-apps mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/struts-apps

Reply via email to