It's definitely clean-up time, Jim.
The plan for 1.3.x is to separate the core, taglibs, and apps into separate
projects.
The reason our current Maven build is ineffective is because project layout has
"grown in the telling".
The next step is to create standard Maven project layouts for each of the
subprojects, so that they are easy to build with Maven or Ant.
All someone has to do is "make it so".
-Ted.
On Thu, 09 Dec 2004 11:36:10 -0500, James Mitchell 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?
>
> 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.
>
>
> 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?
>
>
> --
> 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]
