regardless of the implementation, I think that it is of much more value to have dependency reason (use case 1) in the site that in the project as an xml comment. At my company that was decided, but I think that the project site is of great value to maven, and since there can be found the sources, tests, reports, just about everything, it makes sense to me that dependencies report includes a column 'reason, comment, or similar'. In a future, with transitive depdendencies this could be automatically adeded like 'required by hibernate' or similar, and with the ammount of dependencies a project can have, this information can be usefull.
On Fri, 26 Nov 2004 06:41:58 +1100, Brett Porter <[EMAIL PROTECTED]> wrote: > That said, there will be the ability to make changes for 1.1, so we > should decide whether it is really needed. > > You can use a property now to get this happening - I have no problem > with that. > > I don't believe a <comment> element under a dependency is really > necessary. The use cases I see are: > - describe why this project has such a dependency > - describe what the dependency is > > The first can be done with an inline XML comment, and I don't see the > value of automatically including it on the site. > The second will be solved properly by transitive dependencies, where you > read the <description/> of the dependency's project. > > So I don't see the need to add the element myself, and also there are > the reasons against making dependency different to the project that I've > listed earlier (or in another thread recently, I'm not sure). > > Cheers, > Brett > > > > Jason van Zyl wrote: > > >On Wed, 2004-11-24 at 18:36, Felipe Leme wrote: > > > > > >>Miguel, > >> > >>Applying such patches are not that easy, as the patch adds a new feature > >>to the dependency which I'm not sure if it's the right one. > >> > >> > > > >Supplying a patch which changes the POM itself is not likely to be > >absorbed rapidly. The POM is the fundamental unit of work in Maven and > >as such those changes will occur more slowly. So just a note that > >patches for changes in the POM will not be applied over night. In > >addition all further changes to the model will occur in maven-model > >where the sources for the model are generated. > > > > > > > > --------------------------------------------------------------------- > 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]
