For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 3 replies, 3 voices, and was last updated 21 years, 11 months ago by
.
-
Posts
-
I’m not having much fun with ‘Smart Deployment’. It seems to ignore the ‘export’ checkbox in the export/order tab. Here’s why a care.
Some of my projects have associated JNI. This means that they can’t be in the per-web-app classloader. Now, it would be a wonderful thing if you could support deployment of such projects’ jar files into the tomcat common/lib directory. In the interim, I wish I could configure some of my dependent projects to auto-deploy, saving me the trouble of copying jars, while leaving some out of the process, since I have to manually configure them into common/lib.
p.s. When the notes on this feature talk about ‘manual merging’, just how would you suggest that I go about manually arranging for the deploy button to copy a jar or two?
Benson,
Currently, smart deployment can be set on a per-web project basis but it will handle all dependent projects the same way based on that setting. Dependent project support is really intended to support in-house frameworks, taglibs, or other such utility projects that are needed when the web app is deployed. As a result, what gets deployed from each dependent project is all the class files built on any output path on that project. Libraries used by dependent projects are ignored, whether exported or not, because that devolves into deploying the “full closure” of all dependent projects and configuration of such a facility could be quite difficult.
Think of smart deployment as a quick way to package and add libraries that you have as source into your web app’s WEB-INF/lib directory.
This means that they can’t be in the per-web-app classloader. Now, it would be a wonderful thing if you could support deployment of such projects’ jar files into the tomcat common/lib directory.
Such a deployment into tomcat’s common/lib directory would only be needed precisely one time. As such, we view this as application server configuration and currently don’t support it. I’d suggest that you simply copy the JNI libraries to the lib directory manually, one time, and then add the libraries as an exported external library on a dependent project to your web application. This will assure that the libraries are available at compilation time, but won’t be deployed as part of the web application.
just how would you suggest that I go about manually arranging for the deploy button to copy a jar or two?
All libraries configured on you web app’s build path through inclusion in WEB-INF/lib, as a jar, or as an external jar, will be packaged and copied to your web application’s lib directory.
