Thanks Vincent,

I was more referring to adding a DEPRECATION message inside the
cactus:dependency-handle tag, for example, so no new code uses it.

- Brett

Quoting Vincent Massol <[EMAIL PROTECTED]>:

> 
> 
> > -----Original Message-----
> > From: Brett Porter [mailto:[EMAIL PROTECTED]
> > Sent: mardi 6 juillet 2004 14:30
> > To: Maven Developers List
> > Subject: plugin dependencies
> > 
> > Hi,
> > 
> > After dIon prompted me to take a look yesterday afternoon I figured a way
> > to
> > load the plugin contexts on the fly without messing up the order of
> > things, so
> > maven:get/maven:set (and their legacy versions pluginVar
> > and getPluginContext) now initialise a plugin if it is not already
> > initialised.
> > 
> > This means that all of the following are valid ways of introducing a
> > plugin, and
> > work together:
> > - using a dynamic tag library from it
> > - using a goal from it
> > - using maven:get/maven:set
> > 
> > The odd behaviour of <j:set working only before initialisation to push it
> > into
> > the plugin context will continue to work, but is not something we want to
> > encourage, so the documented way of manipulating plugin properties needs
> > to be
> > maven:get/maven:set. I won't document the dependency-handle stuff in this
> > case
> > as that really has nothing to do with the use of plugin properties. That
> > was
> > only the chosen preferred fashion last year because it was (marginally)
> > better
> > than a goal prereq.
> > 
> > I've added deprecation warnings to all the :load goals and :dependecy-
> > handle
> > tags I could find. Vincent, you might like to do this for cactus too.
> 
> Thanks for this change. Much needed and much appreciated. It was really a
> pain in the past...
> 
> I'll definitely modify the plugins I "manage". However, I'd prefer not to
> modify them for some time as I would like them to stay compatible with older
> versions of Maven (otherwise, it requires people to update their maven jelly
> tags jar). I think a few weeks after 1.0 is released should be ok though.
> 
> Thanks
> -Vincent
> 
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to