- This topic has 3 replies, 2 voices, and was last updated 15 years ago by
.
-
Posts
-
I currently evaluating myeclipse blue as our alternative to RAD. Our application is consist of more than 15 projects and uses more than 20 libraries. During deployment I’m using “Jar dependent Java projects” and “Jars exported from dependent Java projects” and “user library jars exported from dependent Java projects” as deployment policies. But with big application, the deployment to server will took a very long time.
I’m just wandering if there is other option wherein i’ll just manage them manually and specify the classpath to my libraries and dependent projects instead? In this way I’ll be able to minimize the classes that i;m deploying. How can do this?
Thanks in advance!
ampanis,
Under the dependent java project deployment policy we have an option to Ignore the deployment of dependent project of you want to manage it manually. Doesn’t this option work for you? This deployment mode instructs the Deployment Service to disregard dependent projects during the deployment process. A consequence of this policy is that your deployed application may experience ClassNotFoundExceptions yet within your MyEclipse workspace the project may compile cleanly.Are you looking for something else?
I tried already what you suggest but as what you said I encounter ‘ClassNotFoundExceptions’ . I’m trying to look for a workaround to avoid the error. Basically, what i trying to do is to shorten the deployment time due to size of our project. What i’m thinking is to generate the jar files of my dependend project then I just specify them in the classpath. Where can I specify them so that during deployement I will not encounter the ‘ClassNotFoundExceptions’ exception?
