Farr, Aaron wrote:

-----Original Message-----
From: Stephen McConnell [mailto:[EMAIL PROTECTED]

Here I disagree.  There are multiple cases where an API artifact does
not change version bu the implementation artifact does.  For example,
the change made to the Avalon Meta package impacts the meta tools
project and the plugin project.  The api remains unchanged.  I think we
should avoid a "group" version model as this move us away from the
reflection of notion of major and minor version changes that correlate
with interface/implementation changes.


<snip/>


If JIRA supports nested categories I would agree with.  If it does not
then I think we need multiple categories simply because of the number of
independence versionable projects.


Okay, so that means we'll have:

Category: Avalon

avalon-extension avalon-framework avalon-meta avalon-repository logkit <-- or should these 4 be separate categories? merlin <--| phoenix <--| fortress <--|


Logkit and fortress represent single versionable deliverable so I don't see a need to seperate these out. Merlin contains a suite of version artifacts and should be seperated out.

Here is an updated list of the Avalon group artifacts (taking into account released group ids and avalon-xxx consolidation).

avalon-extension-spi
avalon-extension-impl
avalon-framework-api
avalon-framework-impl
avalon-meta-api
avalon-meta-impl
avalon-meta-spi
avalon-meta-tools
avalon-meta-plugin
avalon-composition-api
avalon-composition-impl
avalon-composition-spi
avalon-activation-api
avalon-activation-impl
avalon-activation-spi
avalon-util-exception
avalon-util-criteria
avalon-util-defaults
avalon-util-env
avalon-plugin
avalon-repository-api
avalon-repository-impl
avalon-repository-main
avalon-repository-spi
avalon-repository-util

Merlin versionable projects include:

merlin-api
merlin-cli
merlin-impl
merlin-plugin
merlin-unit

<snip>


That's a LOT of projects to administer and, to me, it seems like overkill.
I mean, that puts something like excalibur-datasource on the same level as
Merlin and Phoenix. There are still project components that can handle a
lot of this. For example, can't we at least have the Cornerstone API and
IMPL parts just be components of the same cornerstone-xxx project?

Only if you assume that the api and impl versions are aligned. If you do this it eliminates the possibility for a frequent update rapid release process on an impl behind a stable API.


I guess
that could mess up the versioning. Grrr.

I know .. what we really need is subcategores in JIRA.


Stephen.

--

|------------------------------------------------|
| Magic by Merlin                                |
| Production by Avalon                           |
|                                                |
| http://avalon.apache.org/merlin                |
| http://dpml.net/merlin/distributions/latest    |
|------------------------------------------------|

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to