[jjcantri]

Is there a way to deploy dependent JARS with a project deployment. For example, our EJB manifest has a classpath entry which specifies the dependent jars it needs. Subsequently, we have constructed our EAR project to look like:

EAR
|-EJB.jar
|-lib
| |-jar1.jar
| |-jar2.jar
|-WAR.war

The lib directory needs to be deployed along with the deployment of the EAR. Is there a way to add this to the deployment process. The jars can not be added to the server system classpath due to class visibility issues.

[jjcantri]

I figured out if you add the lib folder to the EAR project the libraries get deployed with the project deployment. You can also create a custom build target to be run

[Scott Anderson]

You can also create a custom build target to be run

Not at the moment. It’s an interesting idea though. If you can give it some thought and decide what type of support in this area would be most beneficial to you, it would make a good post for the ‘Enhancements’ forum. We’re currently kicking around ideas in this area so some external viewpoints would be great.

–Scott
MyEclipse Support

[jjcantri]

I guess what I was refering to was that you can add an External Tool Builder to the project and specify where it gets called in your ‘build’ order.

[Scott Anderson]

Ah, I see. Well, our deployment isn’t really part of the build process, but it does respond to changes made during it. You might experiment with adding your custom builder, rebiulding the project, and then see if the changes you made are picked up by the deployer as you’d expect. Interesting idea.

–Scott
MyEclipse Support

[Author]

Posts