Decoupling the build is probably a good idea. Struts Flow shouldn't depend on the trunk version of core since it is targetted to existing Struts applications.
As for a Maven build, I'm not against using it, I just don't know how to convert the tasks to Maven, particularly building the examples. I also have this problem with BSF, code I want to start a release on, but am hung up on whether (or more accurately, how) to fully convert to Maven. Don On 10/12/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > From: "Don Brown" <[EMAIL PROTECTED]> > > > Thanks, I'll look at it tonite. > > I just looked at it and I think this is another case where we need to > decouple a sub-project from the common build. You're picking up a couple > of > dependencies that you don't need (antlr and fileupload) and I'm having > trouble getting Maven to pick up additional files (**/*.conf) from the > src/test directory. The test is failing because it can't find sqlmap.conf. > > So... for now I'm just going to add a project.properties file to make > Maven > skip the tests for Struts Flow, and (unless you want to work on the Maven > build) I'll get back to it eventually and give it a separate build file. > And maybe even get the example webapp into the nightly build. :) Right now > I just need the website build to work. > > James, can you check the nightly builds? They should be failing as well, > but they're not. The project.xml in the 20051013 Struts Flow nightly build > does not have Don's changes from 10/8. > > -- > Wendy > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
