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
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,
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
>
> 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
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
I would like to share my current pom configuration which lets me to
build and test java8 apps on latest and greatest jdk9
This profile is activated when using jdk9.
This is based on a suggestion of Robert, its suggestion for the
javadoc plugin is working great with surefire too
Le mercredi 17 mai 2017, 14:46:13 CEST Paul Hammant a écrit :
> > not to speak about read concurrency when one requires to use multiple
> > versions
> > of a lib. And of course, write concurrency is even harder.
>
> I'm not following, dude.
:)
I'm not sure I'm not mistaken for the read part:
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]
Then you'll see that EventMonitor has been deprecated, in favor of EventSpy in
Maven 3.0.2 I think: we should probably improve the javadoc...
Github user hboutemy commented on the issue:
https://github.com/apache/maven/pull/118
great, I'll merge your ideas with
https://github.com/apache/maven/commit/75b23eb01f913cf90d6ac4f9d2d5d7f6b9d69e1a
: removing the patching part will be a be a good benefit
issue tracked in
