ARCHETYPE-520 (and ARCHETYPE-358) are indeed close to the problem I try to
describe, but not exactly the same.
These issues are about using the mirror configuration to access archetype data,
i.e. using http://myrepo.mycompany/maven/archetype-catalog.xml instead of
direct access to http://repo1.
Of course that content-based-storage system isn't a whole FS. That'll take
us back to where we were with some of the ClearCase modes of operaton where
all IO slowed down. Or worse - PVCS Dimensions in regular use. It's just
for read only pieces of our build-centric world.
-ph
On Thu, May 18, 20
You know, I think it would be cool if there were file systems that would
implement a form of a 'link' as part of a content-based-storage mechanism
like Git itself. Meaning if I ran the above git-clone/jar command twice in
two different directories it would only store the result once (assuming
idem
>
> I'm not sure I'm not mistaken for the read part: with the current repo
> format,
> one thing that is super easy is that each artifact version is just a path
> that
> you can use simultaneously in one build or in multiple builds
>
e.g.
build #1 using --classpath ~/.m2/repo/tw/xstream-1.4.3.jar
Hervé,
Maven Monitor was a Maven 2 artifact [1]
> It was dropped in Maven 3 "as an artifact": code was moved to maven-core
> during the Great Refactoring (TM) [2]
>
>
Thanks - it's a total red herring to chase that component then.
> Then you'll see that EventMonitor has been deprecated, in favo
