One "unwritten?" rule of Maven good practice is that you change the undefined dependency version definitions to fixed versions before release. If you have done that, resolution will not be effected by certlist on or off status.
The value (benefit) what certlist would provide to a Maven user, is that the user will not need to evaluate many artifact, which are not worth to spend time on looking at. This could result to saving our valuable spare time which we spend on contributing to different open source projects. On Mon, Sep 28, 2009 at 11:32 AM, Brian Fox <[email protected]> wrote: > On Mon, Sep 28, 2009 at 9:02 AM, Albert Kurucz <[email protected]> > wrote: >> Any other flaws? >> >>> A build then becomes dependent on the certlist in order for it to function. >> The project's build will not become dependent of the certlist. >> If it was able to build with certlist feature turned on, it will >> certainly build without the certlist. > > If the build at all depends on the cert list for proper resolution, > then yes it is a defacto dependency of the build. In other words, if > the resolution is at all different without the certlist than it is > with it, then the build is dependent on it for proper resolution. If > the certlist isn't required, then what value does it provide? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
