Dependency management in the Play Framework application

I am trying to figure out the right tools for managing dependencies between JARs. I have a Play Framework application that imports a JAR (based on another project I'm writing). This JAR imports other JARs, some of which have dependencies for other JARs.

So far, I went through adding material to the build path in Eclipse. But when I deploy the Play application (export to .war, deployment to Glassfish), the necessary JAR files are not included. I need to manually copy them to play / lib. This is a pain because there are so many.

So my question is twofold:

  • For the JAR file I'm writing: what's the best way to manage dependencies? Maven?
  • Is there a way for the Play application to avoid copying files to / play / lib and still be able to deploy without pain?

In an ideal scenario, I would like to import a fully standalone JAR file into a Play application, i.e. I do not need to add JAR file dependencies for playback. How can I achieve this?

Thanks in advance.

+4
source share
2 answers

Here is the easiest way to achieve what you want: http://www.playframework.org/modules/ivy (and you can combine it with IvyDE, the Eclipse plugin for managing dependencies with Ivy).

+3
source

you can ask to ask on google list, they are usually very responsive ...

http://groups.google.com/group/play-framework

0
source

Source: https://habr.com/ru/post/1314934/


All Articles