Dependencies and local repository clean-up

[Christian Clausen]

Hi,

I have noticed the following behaviour concerning maven dependencies:

Suppose a dependency named D is in the remote repository (think of D as a snapshot jar file matching the pattern "*-SNAPSHOT.jar"). The first time a goal of a project depending on D is attained, the artifact is downloaded to the local repository. Suppose now that a new version of D is deployed to the remote repository, and that the version of D is kept unchanged (hence the final name including version is unchanged). When the goal of the depending project is attained now, the new version of D is NOT installed in the local repository. Consequently, we are still using the old version of D.

How do I avoid this situation? Is there a standard way of flushing the local repository (per groupId)? Or is it somehow possible to have maven use an HTTP header to check the remote file date against the local file date?

An obvious workaround is to code a simple goal which removes some or all files of a given groupId from the local repository.

The described situation is not so common if you are developing a single project depending on 3rd party or own production versions (x.y.z) since such files are never modified. But during development in a larger project consisting of several maven projects, I think it is good to be able to share "newest deployed versions" without having to be explicit about the "z" in x.y.z.

Regards,
Christian




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]