On Fri, 2004-01-09 at 13:09, Lester Ward wrote: > > Would this be more or less work than actually changing > > the POM and necessary plugins? > > > > <dependency> > > <groupId>foo</groupId> > > <artifactId>bar</artifactId> > > <type>jar</type> > > <version>1.2</version> > > <properties> > > > > <maven.dependency.type>runtime|compile|test</maven.dependency.type> > > </properties> > > <dependency> > > > > I think runtime should be the default property if none is specified. > > +1. > > This is exactly how it should work.
No, I don't think so. The properties were specifically introduced for the benefit of plugins and while the properties could certainly be used the type element was specifically made for the handling of a type of dependency. > It will avoid having to retrofit huge > amounts of project files. Why would you have to retrofit any POMs? In fact if you used the properties you would have to. > Plus, this is sort of the point of having a > properties section. It's not what it was intended for actually. > One other thing, if you are going into the dependency code: the clean goal > should ignore .all. dependencies. Definitely. It happens to be like that as we never designed a facility where the requirements of a goal could be stated or cleaned. Obviously for a clean you don't care if you have the dependencies or not but we have no way of stating that anywhere currently. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
