Hi!
I think you should even in this case use a different directory on your local
filesystem to deploy your proprietary artifacts to. Isn't that best practise?
Think of making backups of your deployed artifacts and not of the whole cached
artifacts from the internet. Mixing things in the same type of repositories
leads to more confusion and is not reproducable.
Best
Alex
> It's not a cache for another reason...
>
> mvn install:install-file
>
> where you install proprietary artifacts into your local repo
> when working on proprietary code and you don't have a proper
> repository manager to host them on.
>
> So you really have to know why each artifact is there and
> where it came from before you can just delete it at random.
-----------------------------
Bruker Daltonik GmbH
Fahrenheitstrasse 4 Gesch?ftsf?hrer
Sitz der Gesellschaft
28359 Bremen Frank Laukien, Ph. D. Bremen
Germany Gerd H?lso
Sebastian Meyer-Plath
Bruker Daltonik GmbH Stefan Ruge
Handelsregister
Zweigniederlassung Leipzig Dr.Ian Sanders, Ph. D. Amtsgericht
Bremen
Dr. Michael Schubert
HRB 8150
Permoserstrasse 15 Dr. Michael Schubert
www.bdal.de
04318 Leipzig
Germany
Haftungsausschluss: Die Bruker Daltonik GmbH ist nicht verantwortlich f?r die
ordnungsgem??e, vollst?ndige und verz?gerungsfreie ?bertragung der Nachricht.
Der Inhalt der E-Mail ist nur rechtsverbindlich, wenn er unsererseits durch
einen Brief oder ein Fax entsprechend best?tigt wird.
Exclusion from liability: Any liability of Bruker Daltonik GmbH referring to
the correct, complete and immediate transmission of the message shall be
excluded. The content of the e-mail including its attachments is only legally
binding if confirmed by Bruker Daltonik GmbH by letter or fax.
-----------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
