Wouldn't adding the local tomcat install path as a classpath dependency
allow to use the same local tomcat version?
from the example given it seems that as long as the jars are added to the
classpath it should work isn't it?
buildscript {
dependencies {
def tomcatVersion = '6.0.29'
classpath "org.apache.tomcat:catalina:${tomcatVersion}",
"org.apache.tomcat:coyote:${tomcatVersion}",
"org.apache.tomcat:jasper:${tomcatVersion}"
classpath ':gradle-tomcat-plugin:0.6'
}
}
Ronen
On Tue, Apr 19, 2011 at 6:07 AM, Adam Murdoch
<[email protected]>wrote:
>
> On 19/04/2011, at 8:06 AM, StormeHawke wrote:
>
>
> Robert Winch wrote:
>
>
> I'm not sure if you have already seen the gradle tomcat plugin [1]. I'm
>
> not
>
> that familiar with it so I may be wrong, but I think it does quite a bit
>
> of
>
> what you are looking to do.
>
>
> [1] https://github.com/bmuschko/gradle-tomcat-plugin/
>
>
> HTH,
>
> Rob Winch
>
>
> I have seen it and experimented with it; however the plugin in question
> forces you to use a tomcat container that is embedded in the plugin itself
> rather than allowing you to use the installed tomcat instance on the
> machine
>
>
> At some point, we'd like to extend the jetty plugin so that it can deploy
> the webapp to an installed jetty instance on the local machine (and
> ultimately on a remote machine). It would be nice to do the same for the
> tomcat plugin. There's probably some common stuff we could extract from both
> plugins to make it easier to do this (and for whatever web container plugins
> come along in the future).
>
>
> --
> Adam Murdoch
> Gradle Co-founder
> http://www.gradle.org
> VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
> http://www.gradleware.com
>
>
