+0 to doing it for the maven: tags, -1 for the werkz additions (which I don't think you are referring to anyway).
There may be a problem here anyway because of the classloaders - so if they are split, I'm not sure if you can use different versions across projects. I'm ok with this happening if that is considered and proven to work ok, and also as long as the implications for beanshell or whatever tag libraries or equivalent are also considered so code duplication is a minimum going forward into supporting multiple scripting languages in maven2. - Brett > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Monday, 15 March 2004 11:11 AM > To: [EMAIL PROTECTED] > Subject: Suggestions for decoupling the core > > > As part of the ongoing process of decoupling the core, I > think we should > split the jelly tags out from the maven cvs repository into a > maven-tags > repository. > > One of the issues with maven releases has been that new tags are > introduced, and the tags are part of the core maven jar. This > would help > alleviate the issue, and allow us to correctly specify the > dependencies > between the tags and maven core. > > Comments? > -- > dIon Gillard, Multitask Consulting > >
