Re: manifest updates - dependencies - cornerstone - excalibur
Stephen McConnell <[email protected]> Sun, 12 Jan 2003 02:10:00 +0100
| Newsgroups | gmane.comp.jakarta.avalon.apps.devel,gmane.comp.jakarta.avalon.devel |
|---|---|
| Message-ID | <[email protected]> |
Peter Donald wrote: >On Sun, 12 Jan 2003 11:43, Stephen McConnell wrote: > > >>An immediate question I has is if the excalibur-pool package should be >>updated to build against commons collections package (involving updates >>of the build file and pool manifest)? Secondly, I think we should up >>the version of excalibur-thread from 1.0 to 1.1. >> >>Any thoughts? >> >> > >Don't add dependencies as it will break certain deployment environments and >none of those packages are released so the versions mean nothing. > Sorry Pete but your going to have to give me a bunch more information. There is one deployment environment called the JVM which recognizes package depedencies. We have a bunch of jar files with package dependencies that are not documented in the manifest entries and should be updated to correctly reflect the real case. As to other deployment environments - can you please provide the details of the specific environment your referring to. Steve. -- Stephen J. McConnell mailto:[email protected] http://www.osm.net