> -----Original Message----- > From: Michal Maczka [mailto:[EMAIL PROTECTED] > Sent: 05 July 2003 23:24 > To: Maven Developers List > Subject: RE: [war plugin] - Proposition by default include instead of > exclude > > > > > -----Original Message----- > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > Sent: Saturday, July 05, 2003 10:57 PM > > To: 'Maven Developers List' > > Subject: RE: [war plugin] - Proposition by default include > > instead of exclude > > > > > > 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. > > > But from the other hand - such change will be never easier from this > perspective > and there are much more "painful" changes coming (e.g. naming schema of > plugins' properties) > I think that we have a right to change things even drastically while maven > in still in beta stage.
I think I'll disagree here (and lot of person will also disagree with me). OpenSource projects has the word open in it. That is person will start to use it if they think it is useful. And Maven certainly is. The fact that it's been more than 1 year without any release is indeed problematic but persons who like Maven have to live with this. I am one of them and I use Maven on big production projects. My view is that when you're doing open source development you have to respect your user base. It is your duty to do so. Some projects have a problem with doing releases and Maven is one of them. MockObjects is another one (it is still at version 0.09). This is not right. The very least you can do is make it painless for your users and avoid breaking things at each beta release. > > I agree that for some users this will be a bit painful, but for those who > are going > to start using maven or for those who are just going to make another > webapp > with maven, this change means simplification. I don't agree. I'm using the war plugin on a big project (5 years span, 200 persons, 70 developers, 2 geographic locations, 300+ Maven projects). I'm also using it on about 3-4 other projects. It's working for us and it's never been a pain to declare our war dependencies. Now, if you want to break APIs, I'd suggest we release Maven 1.0 and start working on Maven 2.0. But we *MUST* release 1.0 before. Now, I don't know if you were already working on Maven but not long ago, the Maven team decided that from now on (that was about 2-3 months ago) there would be no breaking of APIs and that we would put all our efforts in fixing bugs and release 1.0... I don't believe this promise has been completely fulfilled but we have tried. And adding more incompatibilities will not help. I'll continue to veto this change. I'm still -1 :-) -Vincent > > > > 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. > > > Also thought about that. > If still prefer to update my POMs... but certainly this is an option. > > > regards > > 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]
