Jason van Zyl ha scritto: > > If you are using the IDE integration how is it going to know where to > find the sources and javadocs for debugging. That's one simple case. > By adding a tweak to make the deployment diverge from the standard you > potentially ruin the integration with other tooling. Separating the > deployment makes IDE integration not work, makes getting sources or > Javadocs not work for the command-line IDE integration. The > assumption, at a fundamental level, in Maven is that the secondary > artifacts are always deployed with the primary artifact. You're of course much more entitled in judging what is the worse assumption.
Btw, your answer was what I was looking for: now it is more clear why you are against the patch (previously you gave no motivation excluding "a good thing to do" and "doesn't seem to make much sense" :-) ). PS: If you add this in maven core then the IDE integrations might take care of it once. Otherwise maybe plugin author will find their own way to hack around this and IDE integrations will have no choice but fail. Of course If we cannot identify any reason to separate them, then there is no problem. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
