Plugin Development with 3rd Party libraries

How can I tell TeamCity, that my Plugin needs some libraries, containing in a separate folder.?

4 comments

Hi,

If you're talking about server-side plugin, corresponding jar files should be put to the same directory as plugin jar itself: webapps/ROOT/WEB-INF/lib

Regards,
KIR

0

Thanks, but I hoped there is another way possible. I have the problem, that some libraries, which my plugin uses, have conflicts with libraries that TC uses, so when I put them into this folder, my Plugin works, but TC not. BTW I'm talking about following libs (stax-api-1.0.1, jaxen-1.1-beta-9, jaxb-api-2.0, jaxb-impl-2.0.1, jaxb-xjc-2.0.1, wsdl4j-1.6.1, xfire-all-1.2.6, XmlSchema-1.4.2, wss4j-1.5.1, commons-lang-2.3, xmlsec-1.3.0, wstx-asl-3.9.2, xfire-jsr181-api-1.0-M1). Maybe s.o. knows which of them may be responsible for the conflicts or has an idea.

thanks

0

In new version we are going to support plugin folders. This would mean you do not need putting all the libraries to the same folder. Please feel free asking any details on that. This feature is about to appear in forthcoming(after 23 jun 2008) TeamCity EAP.

0

It sounds fantastic. Is there already certain date for release of the new version.? And where do I get information about using this new feature?

0

Please sign in to leave a comment.