Andreas Gudian wrote: > Am Freitag, 1. Februar 2013 schrieb Jason van Zyl : > >> >> On Jan 31, 2013, at 7:13 PM, Arnaud Héritier >> <[email protected]<javascript:;>> wrote: >> >> > Hi Olivier, >> > >> > Thx a lot for the fix. It will help a lot the community. >> > But from my point of view it's perhaps not yet enough. >> > We should : >> > 1/ change the default behavior to deactivate this control which is >> > difficult to understand >> >> I disagree. We may want to change it slightly but it's only a problem for >> people who flip between Maven a repository manager and without but it's >> to ensure the identity of a component. I haven't seen a huge number of >> complaints. I do not want to turn this off. Improve it, sure, but turning >> it off by default I believe is not the right thing to do. >> >> > How about turning it into a warning by default and only fail if you enable > some meaningful option (or implicitly in some plugins such as the release > plugin). > > But I must admit that I don't really have a use case in mind where failing > is crucial.
We have a private plugin from an internal repository which has a goal that is executed during the build and a goal to generate a report. Unfortunately the jar of the plugin can no longer be resolved when it should generate the report. As it turns out, the site plugin is too old (3.0-beta-3). However, any newer version has a bug (MSITE-604) and site:deploy fails i.e. we cannot release with it. Catch-22. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
