I think I'm -1 for making this change now. As you say there are just too many who are using it the other way.
I'm +0 if you want to introduce a war plugin property such as: maven.war.dependency.behavior=exclude|include so that the current behavior is the default. -Vincent > -----Original Message----- > From: Michal Maczka [mailto:[EMAIL PROTECTED] > Sent: 05 July 2003 21:04 > To: [EMAIL PROTECTED] > Subject: [war plugin] - Proposition by default include instead of exclude > > I realized that in POMs of my web projects I have very long lists > of dependencies marked with: > > <dependency> > ... > <properties> > <war.bundle>true</war.bundle> > </properties> > </dependency> > > > I always want to "bundle" most of deps (or all of them) > while if I exclude I do exclude only few of them > > > I think that war plugin will be bit easier to use if by default > all dependencies are bundled and only those specially marked: > > > <dependency> > ... > <properties> > <war.bundle>false</war.bundle> > </properties> > </dependency> > > will be excluded. > > Anybody will oppose if I will change the war plugin and make it work this > way. > > I do believe that this is a change for better ... but also I myself will > have to edit > a lot POMs, that's why I prefer to know opinion of other users of this > plugin. > > Michal > > > > --------------------------------------------------------------------- > 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]
