I didn't mean maven as opposed to other dependency management. I mean that Lift should use whichever jQuery is in the webapp, and let that be determined via maven etc. In other words, if there is a maven artifact for jQuery that can be used to put the .js file in the war, then at run time Lift could locate it and use it, and this way you can determine the version together with other dependencies, rather than hardcoding it in Boot or creating a new API. It's just an idea, no idea if it's even possible.
------------------------------------- Jeppe Nejsum Madsen<[email protected]> wrote: Naftoli Gugenheim <[email protected]> writes: > Is there any way to get maven to decide? If there was some way to set JQuery > as a dependency in the pom and have Lift locate it at runtime that may make > the most sense, if such a thing is remotely possible. Indrajit, any comment? I don't think this is optimal for people not using Maven. It's (sort of :-) ok to use maven for building the Lift jars, but I think we shouldn't put too much logic into maven for Lift users. /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
