Roughtly my ideia is to have a repository, which can contain 3 category of 'Modules'
Components ( of which can be a normal Component, or an API Component, or a ComponentGroup )
Applications
Projects ( That's for large scale projects which will produce components and applications )
the internals of those are to be *everything* that might be of interest relating to a project, even to the point of including the possibility to associate/attach emails, posts, etc...
Stephen McConnell wrote:
Berin Loritsch wrote:
Yannick Menager wrote:
Yes that would be easy to put in place, all that's really needed is a standard XML format to describe projects, components, etc... I'm starting to work on that first :)
J Aaron Farr wrote:
Wouldn't the Maven project.xml work?
IMVHO - no.
Two reasons:
1. The Maven project.xml defines an artifact from the viewpoint of building the artifact. It does not define a product. There is significant overlap but at the same time there are quantum differences. I have been playing with (but never completed) a product.xml and counterpart service.xml. The notions I've been focussing on are "product" == "physical tool to do something" whereas "service" == "usage of a tool by a provider to deliver a value proposition". The combination of the two has the ability to deliver a "solution model".
2. In defining a new abstraction - don't depend on a schema that you don't control.
Steve.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
