Support for multiple module repositories

[7uc0]

I the 3rd party dependency tools (maven, Ivy) where custom repository location can be set in configuration file, It would be handy to be able to integrate custom module repository location.
This would lead to enterprise project development adoption, with flexibility and modularity.

[7uc0 (erwan-legoulven-gmail)]

My understanding of current repository mgt is the following :

-one version of Play environment comes with bundled modules
-module dependency is handled by configuration (within application conf file)

Taken this into consideration, I think it would be relevant :
-to provide module repository location within Play environment configuration (file or cmd line)
-to provide module version download, with compatibility check within Play environment
-to provide module version dependency within application configuration file

I 've got a question regarding a specific Play version compatility matrix with modules. How is this currently handled ? Manually ? one could think of a declarative way to deal with modules (as for Maven / Ivy artifact).

It may be smart to use mavent / Ivy dep formalism to spread the good news to many adopters, what do you think ?

[Erwan Loisant (eloisant)]

I don't think we need do manage dependencies, but being able to configure your repositories (not be limited to playframework.org) would be a good thing.

So this bug is only about (1) support multiple repositories (2) make that configurable. Feel free to fill bugs for the other stuff, but Maven and friends are unlikely to gets a lot of attention among Play devs.

[7uc0 (erwan-legoulven-gmail)]

A given play version is not compatible with all modules availables. With the current (and nice) module feature, I can :
 * list existing modules
 * install a version of a module
 * activate / deactivate a version of a module

There is no way I can :
* handle incompatibilities between a play version and a module version
* install dependent modules which my module eventually depends on

This kind of feature is handled nicely by 3rd party deps tools such Ivy or Maven, for modules -I'm not talking about 3rd party libs for a module, an Ivy module exists so far for this-.

Anyway I may create a new feature request for this, and let this thread for the module repositorie configuration at play level

[Erwan Loisant (eloisant)]

Committed in r887. Now there's a file called "repositories" in the root of the play install, you can add as many repositories as you want.

You just need to fake the behavior of play-framework.org, that can be done with static JSON files.

[7uc0 (erwan-legoulven-gmail)]

Nice, thanks alot