> -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Saturday, November 08, 2003 11:54 AM > To: 'Maven Users List' > Subject: RE: war plugin : [maven.caller.call.compile-java] is not defined > > > Ok, I think I understand what you mean now. You want to have a > distributed workflow instead of a centralized one. So you want to move > from WKG to WKP (Well-Known Plugins). > > What I don't like is that it means not all plugins will be equal, some > will be more equal than others ;-) It also means that 'other' plugins > will be tied to all WKPs. > > I think I may agree with you, if the WKP are empty shells only, unlike > what is currently the case. It means that instead of having one caller > plugin, you'll have a caller-compile, caller-test, caller-whatever > plugins... delegating to the real implementations like java:compile, > aspectj:compile, etc. > > In the end, your proposal looks like an extension to the caller plugin, > i.e. having several call plugins instead of one. It may or may not be > better. >
I don't want to introduce a bunch of new plugins. In first place we can reuse existsing plugins (java, test) with some resonable defaults (e.g java:compile goal will call javac:compile). We are alredy providing skeletal workflow with well defined states ( I like names of the goals like java:compile etc.). but simply some of the states of our workflow are not customizable. > However, I do think this workflow stuff has to be in Maven core. With > the current Maven implementation, I'd say it's a tag. Actually if I find > a few hours, I'll reimplement the caller plugin as a jelly tag in Maven > core. > I am not sure what you mean by " workflow stuff has to be in Maven core". It's alredy there. Also I am not sure if we need something as fancy as "caller taglib". Take a look at "multiproject:install-callback" goal. Such logic should be sufficient for the most of the cases. Special things might be needed when we will have to load implementor plugin from the repository. But this can be handled by maven core. [..] Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
