archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nicolas de loof" <nico...@apache.org>
Subject Re: dependency on archiva-configuration -> archiva-model in r602916 for legacy paths
Date Thu, 27 Dec 2007 18:05:44 GMT
Just wanted to have LegacyArtifactPath hide the String representation used
in storage, but project dependencies is also valuable.

Why shouldn't archiva-configuration depend on achiva-model ? IMHO, the
"model" should have no dependency. But you can make any change required for
better architecture.

Nico.

2007/12/27, Brett Porter <brett@apache.org>:
>
> Hi Nicolas,
>
> I saw this added dependency in one of your commits and thought it
> might be best kept separated - do you think the toArtifactReference()
> might be better suited to being in the LegacyPathParser?
>
> Cheers,
> Brett
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message