[emmanuel]

I refer to https://www.genuitec.com/forums/topic/external-jars-closed/

🙂 Although this feature is addressed in 2.7 GA, I cannot see what I should do to deploy external jars, which are used in a project and therefore added to java build path. 😕

Could you assist please? 😳

Kind regards
Emmanuel

[Scott Anderson]

Emmanuel,

For deployment of your jars in a web project, they need to be located in the WEB-INF/lib directory. We’ll be working on making this more flexible in MyEclipse 2.8.

[emmanuel]

Hello Scott,

Firstly thank you for the reply; but; you’ve got me puzzled.

Please advice what the following is if it didn’t address this point.

1. roadmap states;
MyEclipse 2.7 (Q1, GA end of Februrary)
Project Deployment
Deployment of linked resources

2.https://www.genuitec.com/forums/topic/external-jars-closed/

I was under the impression above covered this point.

Kind regards
Emmanuel

[Riyad Kalla]

Emmanuel,
Deployment of linked resources is supported, but if you have tried to use it, you’ll see its incredibly restrictive. I think Scott assumed that given your setup you weren’t going to be able to make use of the linked resources, and instead answered the more general question of “when will the project structure be more flexible”.

You are free to try and use the linked resources, but keep in mind when you add them to your project, the parent of the link resource must be a project root node, which is a PIA. This is an Eclipse limitation that Michael has informed me they have no intention of extending any time soon.

[emmanuel]

Hello Riyad,
Thank you for bringing some clarity; but please look at;

https://www.genuitec.com/forums/topic/external-jars-closed/

In that post on Posted: Mar 07, 2004 – 02:16 PM your comments and subsequently closing the post, gave me the impression that external jars would now deploy with the web project; now it seems not.

BTW., I suggest if it is not being catered for yet, or if development of the deployment of external jars has not yet started, that the external jars as added to the build path (in project properties), get deployed from their location; without any further deployment set-up. That’ll be a simple but very effective deployment strategy.

But, please advise why above post is closed if 2.7GA did not address the request.

Kind regards
Emmanuel

[Riyad Kalla]

Emmanuel,
I think you are misreading my posts. Note the 2nd post (mine), I say that if you want external JARs deployed, you need to do it with an Ant script and then down near the bottom I make another comment about ‘linked resources’ and do not mention external JARs.

I do not know if we had plans to support the deployment of ‘External Jars’ because quite a lot of the time these external JARs can be Application Server-specific JARs that are needed during development, but do not need to be deployed as the App Server already has them installed (e.g. servlet-api.jar, jsp-api.jar, etc.).

I will check with S/M about this however as I could be wrong.

[Author]

Posts