John Casey wrote:
The dowload of regular artiafcts will only be made if any of them is missing and build is going to fail.-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
See inline reply:
Michal Maczka wrote:
John Casey wrote:
Hi Everyone,
I wanted to take a few minutes and submit some thoughts I've documented regarding offline mode in m2. My hope is to start a discussion of what parts of the m2 system can reasonably be assumed to be offline-sensitive. The goal is to factor as much of this offline sensitivity as possible into APIs for plugins, phases, etc. to use, so that plugging new pieces into the offline mode will be as easy as possible.
Thanks for your patience in reading and responding to such a large email. Now, having said all that :), here are the contents of an APT document I've started on this topic:
----------------------------------------------------------------------
Just a naive question:
Wasn't the offline mode in maven needed only for avoiding checking if newer snapshots are available every time maven was run?
To me, offline mode is extremely valuable, not only as a way of keeping m2 from attempting to download artifacts, but also in determining what level of success we can expect from other network-related operations.
No, it's not only related to snapshots. Even if you were to ignore the other network operations that mojos might attempt, you still have to consider that the download of regular artifacts will be affected by offline status.
Maybe I am not seeing a full picture here and thinking about loking too much at m1:
why do you think it might be useful not to perform such operations?
Is it still needed if better control if and when such checks have to be made is going to be given?
I'm not sure I follow what you're trying to say here. Can you clarify?
Sure.
I meant that if you could :
- precisly control when snapshot artifacts are updated (via setting some repository or even dependecy properties).
Brett recently stared implementing some simple strategies for that. It will be nice to test how they work in pratice
and if anything is missing and if even finer control is needed.
- define which repositories contain snapshot artifacts so for example you are never going to hit ibiblio
for checking if newer version of one of your company "private" artifacts which obviosly never can be uploaded there
is present in it (so snapshot checking will always be very fast). Note that the same can be also applied to regular artifacts.
then imo there won't be a big need for "offline mode".
I personally use offline mode in m1 only for avoiding slow connection to ibiblio during every run of maven.
If only intranet repos were checked I would not need it.
Other remark:
In offline mode in m1 snapshots are not dowloaded from any repository including those accessed by file:// protcol.
best regards
Michal
------------------------------------------------------------------
Jan Pawel II 1920 - 2005
http://link.interia.pl/f1871
