On Thu, Jun 30, 2011 at 9:19 AM, Norman Maurer <nor...@apache.org> wrote: > Hi Robert, > > I don't get why this should improve things. IMHO its just another thing > which needs care, we already have to many projects for our current devs .. > Maybe you can give some more background..
Auditing and maintaining the final application is something that's going to need care however it's done. (It really takes me too much time and I'm going to need to start building tools to automate the process.) Bundling application assembly within the server components project introduces a conflict between * the need to develop these components * the need to have a fixed target to manually audit and review the final application assembled plus a very slow development cycle for work on the assembly descriptor. It would be much easier and quicker for me to audit and maintain the legal stuff if I could work on a fixed dependency set (using released server components) in an independent project isolated from the server components. And by introducing this unnecessary coupling, any problem in either the assembly or the library components means that neither can be released. Robert --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
