On Thu, 9 Dec 2004 11:36:10 -0500, James Mitchell <[EMAIL PROTECTED]> wrote:
> No, this is not spam.
>
> Am I the only one frustrated with our current build situation?
>
> This is my selfish desire for a clean build of all things under struts/*
>
> A friend and I were discussing some of the recent goings-on and just for the
> hell of it I decided to try to build and deploy all of the example
> applications:
> struts-mailreader
> struts-examples
> struts-blank
> struts-documentation
> tiles-documentation
> mailreader-chain
> strutsel-exercise-taglib.war
> struts-faces
> struts-faces2
>
> Perhaps I'm missing something, but it took me quite a while to do this from
> scratch. I chose to use a common build.properties in my ${user.home}
> directory. So I had to constantly go back and forth adding/changing the jar
> references. It seems like almost all of the build.props.sample files were
> out of date. And some builds used one version of a jar, while others were
> using an older version.
>
> And to this day, I still cannot deploy the mailreader-chain by configuring a
> tomcat context to point to my local mailreader-chain/target/mailreader. It
> keeps barfing, saying it can't find
> /WEB-INF/struts-config/struts-config.xml, which, if I zip up the directory
> and deploy it to webapps, it's fine. :(
>
> What's even more confusing is how different the maven project jar
> dependencies are vs the ant jar for the SAME PROJECT. Can you say CLEAN UP
> TIME?
>
> When you look at each piece of the puzzle individually, they look fine. But
> when you try to put the entire puzzle together, it's pretty nasty.
>
> Anyway, sorry for venting.
>
> Is there any interest in cleaning some of this up?
Yes. I've been thinking about this too.
I've just finished up a generic build "framework" as part of a new
project in my day job. In the process, I learned a lot about some of
the more recent and very cool additions to Ant. That, in turn, set me
off thinking about how we could use that to significantly clean up and
simplify the Struts build(s).
I know there has been a lot of frustration about the Struts build
system, and I'm definitely interested in cleaning it up. I have the
itch and plan to scratch it. ;-)
> Can we remove all the maven build stuff? Since:
> a) Our Maven build does nothing except build a source and binary dist of
> struts.jar
> b) Our ant build does everything that needs to be done (and then some)
> c) Craig does the nightly builds and has no interest in changing to maven
>
> Note: Before anyone flames me, I actually prefer Maven over Ant for all new
> projects, it's just not working for us here and now.
I don't have a problem with tossing the Maven stuff. However, I
believe we do have some Maven mavens in our midst who likely feel
otherwise. This might sound odd, but perhaps, if we do have people who
are interested in actively pursuing Maven, we should move the Maven
stuff to contrib until such time as it provides a working replacement
for our Ant build system?
> Also, why do we have so many copies of the mailreader example all over the
> place? Why can't we just keep one copy and have a build that can handle
> building for core or chain or shale or xyz?
Can't answer that one. ;-)
--
Martin Cooper
> --
> James Mitchell
> Software Engineer / Open Source Evangelist
> EdgeTech, Inc.
> 678.910.8017
> AIM: jmitchtx
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
