Shapira, Yoav wrote: >>Diggory: >>Now, I'm starting to see headaches in all this. Its looking alot like >> a >> >>premature optimization to me. I'm becomeing more tempted to suggest we >> >> > > > >>loose the extend of commons-build/project.xml in each project. We >> >> >simply > > >>maintain consistent project.xml's across all the projects. >> >> > >Ditto +1 on that. > >What's the big deal with using src/java or src/share? Commons projects >are separate projects, and each project's developers can do what suits >them. > There really is none. This isn't an issue, it just seemed to be an example that was brought up about differences between projects.
>If we want to enforce a common look and feel, that's one thing >(that I don't think is that important, but no biggie as long as it >doesn't get in the way of more important things, like users downloading >and building easily without extra dependencies). > I agree >But to add this >dependency on commons-build and raise the bar of required Maven >expertise for release managers at least, and probably component >developers as well, is not cool. > >Yoav Shapira > Its important to understand that we are attempting to use Maven for two goals: 1.) Common Site L&F 2.) Common Distribution Packaging Strategy. Now, using Maven or Ant to do your packaging is up to you. If you use Maven to package, the bar doesn't need to be "raised", there is alot we can do to establish a simple an common strategy for building the distro's. -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
