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 Fri, 28 Dec 2007 06:45:53 GMT
I'll look to refactor this next week.

cheers,

Nico.


2007/12/27, Brett Porter <brett@apache.org>:
>
>
> On 28/12/2007, at 5:05 AM, nicolas de loof wrote:
>
> > Just wanted to have LegacyArtifactPath hide the String
> > representation used
> > in storage, but project dependencies is also valuable.
>
> Your reasoning makes sense :)
>
> >
> >
> > 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.
>
> That's why I was saying it - configuration is a model also and so I
> was trying to avoid a dependency (note that archiva-model drags in JDO
> among other things - though this is really a problem with archiva-
> model...). I was also trying to avoid code in the configuration class
> where possible - but your reason made sense.
>
> It's not a big deal - just something to think about :)
>
> Cheers,
> Brett
>
>

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