Morgan Delagrange <[EMAIL PROTECTED]> wrote on 27/01/2003 12:06:49 PM:
> > --- [EMAIL PROTECTED] wrote: > > Morgan Delagrange <[EMAIL PROTECTED]> wrote on > > 27/01/2003 04:35:21 AM: > > > > > I don't think Maven is a replacement for the > > build-all > > > script when it comes to thorough regression > > testing. > > > The build-all script is much closer to the GUMP > > > environment, so it's a good script to check when > > Maven > > > is building fine but GUMP is puking. Especially > > > problematic is the fact that Maven uses Jelly > > > internally; I'm not sure the classpath isolation > > is > > > all there yet. Also, the build-all script is set > > up > > > > This can be solved by using jar:install-snapshot in > > the builds and > > building Jelly core first. After the jelly build, > > copying the jelly > > snapshot to $MAVEN_HOME/lib will force the latest > > version. > > > > Not entirely. Many of the tags have interdependencies > on one another (some build time, some test time), and > unless you're very careful about your build order, > Maven will cheat and use the repo veresion. Also, I've changed the tags-build goal in my copy of project.xml to use jar:install-snapshot. That means that as a tag lib gets built by the reactor, it gets copied to the repo. The reactor builds them in dependency order, so thats working fine. The only issue I've found is if the SNAPSHOT is used by maven and there's a copy in MAVEN_HOME/lib. That's jelly core and a couple of taglibs. And I think I could work a way around that one too as part of install-snapshot (copy to /lib). > once the 1.0 release happens, many if not all of the > tags will point to Jelly 1.0, so you won't be able to > do the install-snapshot trick anymore to build against > HEAD. You're gonna stop me editing the files? :) -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
