Hi,

> Steitz:
>> just that each project then looses its "atomic" status and is
dependent
>> on commons-build, I think we need to try to get back to only the site
>> generation being dependent on commons-build, I really starting to
>> believe everything else should be standalone.
>
>I agree with the basic sentiment above; but one thing that has not been
>mentioned in this thread is that site generation also needs to be
possible
>from the source distro, since several components include xdocs user
guides
>or other important info that users should be able to build.

Yup, +1 to both of those.

> 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.  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).  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



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to