Hello,
My dev team has been using Maven2 full-time for about 2 months now,
and we're starting to notice a problem that we hadn't really
considered until now. I don't know a safe way to deal with it, but
I'm getting very close to having to do something that might be
unsafe.
The issue is that snapshot builds of our half-million LOC in
30-some-odd modules ends up chewing up 80GB of space in the short time
we've been using Maven. Developers are doing several snapshot builds
each day, while several modules are under heavy development, and when
we do a QA milestone build, we promote modules to release versions,
and development toward the next milestone goes on a new version number
(as well as on a new scm branch).
I've not seen any instance where more than a few snapshot builds are
actually needed to be maintained, but I'm concerned that deleting old
snapshots will leave the repository metadata in a state that doesn't
reflect the reality.
Can anyone comment on this? Is it really safe to roll old snapshots
off the disk, keeping just a few for the not-uncommon case of
incompatible API change?
Thanks,
--
Tommy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
