The same argument can be made for quite a few of the specific java libraries as well. Those that are not included in maven require you to manually install them in your repository for builds, since they cannot be distributed. I understand the warning, but I fail to see how this is a showstopper. If it's an important library for the project, then all we need are release notes to know what needs to be installed separately from the distribution.
After all, we're going to run into the same kinds of issues when packaging public webapps to be distributing via tomcat/jboss/etc for libraries that can't legally be packaged in an application. Cheers. On Jan 3, 2008 3:38 PM, Kevin Menard <[EMAIL PROTECTED]> wrote: > Correct, but that makes it practically useless as a core component :-/ > > -- > Kevin > > > On 1/3/08 3:23 PM, in article > [EMAIL PROTECTED], "Paul Cooley" > <[EMAIL PROTECTED]> wrote: > > > Actually it appears it can be listed as a system requirement: just not > > included for distribution. > > > > On Jan 3, 2008 2:21 PM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > > >> Sounds like the policy has shifted again. It's like quicksilver. > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Gotta find my destiny, before it gets too late.-- Ian Curtis
