Hi Michael,

why is Maven storing the stuff in the file system everywhere? Locally, on
the developers' desktop it is ok.
You mean /home/username/.m2/repository ....this is the usual location for all artifacts which are used once...the intention to increase speed during building...which is not "everywhere" and not on the desktop....only per user base....(Unix, Windows and Mac OS as well).

If you really like to change that behaviour you can make a configuration to use a system wide storage...instead of a user based storage...but this would pin you on a particular system.....


Centrally, why not in a common version
control system?
It might be a possible solution, but the setup is very simple without such an requirement...and would usually reduce build time....

On the other hand you can use a simple Web-DAV Setup for a deployment area which uses a Version Control tool to store the deployed artifacts (may be SVN etc.).

And one other thought is coming into my mind....your build should be repeatable if you do things right (pinning version of Plugin etc.) it shouldn't matter where you build...

>
What are the design decisions for that?
I can only assume what the intentions are...

Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise        ICQ#: 135949029
Hauptstrasse 177                         USt.IdNr: DE191347579
52146 Würselen                           http://www.soebes.de

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to