Jason, > Maybe you should think about what your company policy is. What is your > company policy on the use of software components? Do you use your own > standard or something like a J2EE or Avalon standard? I think in most > cases people gravitate toward a standard. As developers we demand > standards: APIs, interfaces, components. Only recently, with > Maven, has > there been any movement toward standardizing building, artifact > location, documentation production and many other aspects of > development. If your policy is to roll your own, that's cool. If you > follow standards then why not move that way with your development > environment.
The answer is quite simple: our division doesn't control how our company repository looks like. Ever thought of that? Ringo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
