On Wed, 29 Dec 2004 07:29:46 -0500, Ted Husted <[EMAIL PROTECTED]> wrote: > > On Fri, 24 Dec 2004 14:30:24 -0800, Martin Cooper wrote: > > Struts as a group and Struts subprojects as artifacts within that > > group (using Maven terminology here ;). > > +1 > > The big difference here being that there would only be one top-level Struts > entry in a Maven repository, and the various Struts JARs would be nested > under that. >
Yes, that's what we get by using a 'struts' group and then artifacts within it. > Probably, the same thing should be done for Jakarta Commons. There are way > too many Commons-This and Commons-That. > Agreed. The Maven <dependency> elements support this for obtaining the dependencies, but I don't know what changes we'd need to make to the project.xml files to get the deploy to deal with that. Hopefully someone on the Commons list will know. > > It looks like EL "solved" this by copying the build files. > > Obviously, this is, um, less than optimal, but until the new build > > is ready, perhaps we should do the same thing. On the other hand, I > > don't think we want to put a lot of effort to making this all work > > when the build system is changing (hopefully next week). > > Thanks for all you hard work on this, Martin. Working on build systems drives > me batty :) > > And I do hope you and yours have a happy Hogmanay! Thanks! And a Happy Hogmanay to you too! -- Martin Cooper > -Ted. > > --------------------------------------------------------------------- > 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]
