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
