I am fine either way. Thanks for "explain"-ing :-)
On 4/21/07, Martin Cooper <[EMAIL PROTECTED]> wrote:
I'll assume that "explain" was intended between "you" and "your". ;-) In response to Wendy's question, you indicated that you are proposing one jar that includes the integration for multiple external libraries. If I want integration with Spring, for example, and not the other external libraries, Maven isn't going to help me. In my example from before, I need 1/6th of the integration jar, but I have to take the other 5/6ths of it as well. That 5/6ths is baggage that I don't want or need. -- Martin Cooper On 4/21/07, Paul Benedict <[EMAIL PROTECTED]> wrote: > > Martin, > > Point taken on the module naming: "integration" is better. > > Can you your focus on the "baggage"? With maven 2, dependencies can be > marked as optional. They all have to be there when compiling the source, > but > not when depending on the library. > > Paul > > On 4/21/07, Martin Cooper <[EMAIL PROTECTED]> wrote: > > > > First off, calling this "modules" would be very confusing, since Struts > 1 > > already has a concept of modules that is not at all related to what you > > are > > looking to create. Since the purpose is integration with other > libraries, > > I > > would suggest "integration". > > > > Second, I would strongly recommend against creating one all-encompassing > > jar > > file. The problem with that approach is that almost every user will be > > carrying around baggage that they don't want or need. If we provide > > integration with a half dozen other libraries, the chances are that any > > given developer will need at most one of them. That leaves 5/6 of the > jar > > as > > baggage. > > > > I like Wendy's suggestion - start with one struts-spring jar and see how > > that works out. > > > > -- > > Martin Cooper > > > > > > On 4/21/07, Paul Benedict <[EMAIL PROTECTED]> wrote: > > > > > > Wendy, I was thinking of the first. > > > > > > On 4/21/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > > > > > > > On 4/21/07, Paul Benedict <[EMAIL PROTECTED]> wrote: > > > > > > > > > I am proposing a new module for Struts 1.x called "modules" which > > > would > > > > > contain integration classes into popular open source libraries. > For > > > > > starters, it would contain a new command to let Spring wire up the > > CRP > > > > > using a command. > > > > > > > > I would suggest adding one new module called struts-spring, and see > > > > how things go from there. > > > > > > > > (It's not clear to me whether you want to add a jar called > > > > "struts-modules" which would have integration code with Spring and > > > > other third-party libraries, or whether "modules" is intended to be > a > > > > directory structure like "plugins" in the s2 build.) > > > > > > > > -- > > > > Wendy > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > >
