Currently, the release plugin resolves snapshot dependencies by using the XXX-snapshot-version file in the remote repo. This is fine as far as it goes, but has 2 severe limitations for us:
1) SnapshotResolver is hardcoded to only check ibiblio, the remote repositories specified in our build properties are totally ignored. Is this a known issue? I can find nothing in JIRA on this.... 2) In this scenario, the developer is working on artifact A which normally depends on a snapshot of artifact B. He/she has some heavy duty debugging to do on A and wants to temporarilly stabilize on a fixed version of artifact B. At the same time, others are actively working on B and deploying new snapshots. Ideally, the snapshot-version file should be downloaded to the local repo alongside the snapshot jar. In this way, the user always knows exactly what version timestamp they are using. It also allows them to easily convert their local snapshot dependency into a timestamped version. This avoids the issue of another developer updating B's snapshot in the remote repo behind their back. Item 2 is really important for us so that each developer can know exactly each dependency version they are using when they use snapshots. The only way I see to implement this is to hack the DependencyVerifier. I can think of some other scenarios where it would be useful to plugin customized verifiers. Is there any thought to making this possible via a factory? Currently, Project.initialize() is hardcoded to instantiate and set the DependencyVerifier instance on itself. -------------------------------------- David Zeleznik ILOG - Changing the rules of business mailto:[EMAIL PROTECTED] http://www.ilog.com -------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
