Jason van Zyl <[EMAIL PROTECTED]> wrote on 21/01/2003 12:56:15 AM: > Hi, > > Just a FYI for those trying to use some of the new Jelly tag libs that > have been separated. > > I'm sure a couple of you have run into the problem where you can't use > the separated Jelly tag libs from within your maven.xml files. > > This is due to a design flaw on my part where the dependencies for a > project are not made available to the classloader that runs the > maven.xml Jelly script. This wasn't a problem before because all the tag > libs were in the Jelly JAR which was loaded by forehead. We definitely > want to support the Jelly break down that is happening so I hope to flip > Maven over to using Classworlds (http://classworlds.werken.com) and > allow access to any arbitrary tag libs. > > So the plan is if you plan to use any Jelly tag libs you will declare > them in your project.xml file. I'm going to make the dependencies > available to the maven.xml when it runs.
Jason, I did this last week.... project dependencies are currently processed for classpath entries. I've been successfully using this in the taglib split up. -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
