axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepal jayasinghe <deep...@gmail.com>
Subject Re: Supporting hierarchical service deployment
Date Fri, 28 Aug 2009 16:33:58 GMT

>
>
> On Fri, Aug 28, 2009 at 3:18 PM, Deepal jayasinghe <deepalk@gmail.com
> <mailto:deepalk@gmail.com>> wrote:
>
>     >
>     > Anyway, I was not around when module versioning was implemented,
>     and I
>     > strongly feel that trying to derive a version from an artifact is a
>     > "tried & failed" approach.
>     But most people use that approach (including you)
>
>
> Yes, only in the case of module versions, since we do not have any
> other options.
I was not talking about Axis2 :)
>  
>
>
>     > Even Maven does not do that. Just take a look at the directory
>     > structure of a Maven repo. The folder structure reflects the
>     artifact
>     > version, even though you see a number in the artifact that looks
>     like
>     > a version number to a human being.
>     it is just data duplication. I am not in the favor of maven file
>     structure. And I am -1 on introducing such a thing into Axis2.
>
>
> So what is your proposal for an artifact management system such as
> Maven? Derive the version from the artifact name? That approach does
> not scale.
I am not an expert on artifact version I can not make any proposal, but
I do see some data duplication in that approach. I think for Axis2, we
can have enough flexibility just having archive name to be anything, and
if you want then do the version using services.xml (as OSGi).

Mime
View raw message