On Sun, 2003-07-06 at 06:32, Michal Maczka wrote:
> Changes/breaking in API not necessarily are so bad, as long as
> the tools which are helping user to switch to new API are provided.
Yah, I've tried that in the past and my experience is something goes
wrong and you ulimately end up with annoyed users.
> In this case writing such tool - POM transformer seem to be fairly easy.
It is, but don't assume anyone else will find it easy. I would really
just leave the old method and we should come up with a way to set
properties in general for plugins. In the refactoring I have all plugin
properties are accessed via:
plugins.<short-plugin-id>.<property>
so something like
plugins.java.compileTarget
So maybe something like:
<plugins>
<java>
<compileTarget>1.1</compileTarget>
<debug>on</debug>
</java>
<plugins/>
Where that's pretty much 1:1 mapping to the property notation. Not
saying this is ideal just throwing out an idea. We probably actually
need a <properties/> element to separate property manipulation from any
other type of manipulation we might want to do with plugins. At one
point in the past I suggested a class or category for a plugin, say, for
compiler plugins and you could choose the compiler plugin to use in the
<plugins/> element. The Eclipse compiler versus the AspectJ compiler
versus Javac.
> But I was also convinced by Vincent.
>
> regards
>
> Michal
>
> > -----Original Message-----
> > From: Juergen Heidak [mailto:[EMAIL PROTECTED]
> > Sent: Saturday, July 05, 2003 11:51 PM
> > To: Maven Developers List
> > Subject: RE: [war plugin] - Proposition by default include instead
> > ofexclude
> >
> >
> > Hi
> >
> > Breaking API's or configuration settings is always bad. The much better
> > way is to keep compatibility and make the new feature configurable so
> > that it can be turned on easily.
> >
> > I dont use the war plugin I just wanted to say that I agree with
> > Vincent.
> >
> > Regards
> >
> >
> > > > >
> > > > >
> > > > > 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]
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > ----------------------------------------------------------------------
> > SPORT!!! Wyniki na zywo!!! >>> http://link.interia.pl/f174a
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
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]
