Order of module's starting

[Csaba Meszaros, geändert vor 7 Jahren.]

I have a fragment module, and a resource module, which provides the fragment with additional strings. It would work normally but I have a serious problem: the fragment starts after the resource module, so the keys in the resource module are not recognized on fragment's JSPs.
The only solution is to restart the resource module with Gogo shell after the server is started.
Since I am working on a project with nearly 100 modules already, I really need to address this behavior.

My question is: how could I force the resource module to start after all other modules did start?

Thanks!

[David H Nebinger, geändert vor 7 Jahren.]

See my blog post https://web.liferay.com/web/user.26526/blog/-/blogs/adding-dependencies-to-jsp-fragment-bundles

If you have a dependency declared, the fragment will not start until the dependency is satisfied.

[Csaba Meszaros, geändert vor 7 Jahren.]

Hi! It nearly works...
Nearly, because your example is a service, while my is a Resourcebundle loader module. I cannot add the dependency gradle would accept:
my module for that is minthaka.registration.resource. How can I add it to fragment's build.gradle file, because this doesn't work:

dependencies {
compile group: "minthaka.registration.resource", name: "minthaka.registration.resource", version: "1.0.0"
}

It simply fails to compile.

[David H Nebinger, geändert vor 7 Jahren.]

If it's part of the gradle workspace you should be using the project form:

    compile project(":modules:resource-bndl")

[Csaba Meszaros, geändert vor 7 Jahren.]

Dont't take it as offence but that style of answers doesn't help me at all. I would really appreciate something more clear:
I have fragment minthaka.registration.fragment and bundle minthaka.registration.resource. These are two separate modules inside the Liferay workspace. I intend to use the latter to provide me extra strings and it does, but only if I restart this using Gogo shell.
So where do I have to implement this

dependencies {
compile project(":modules:resource-bndl")
}
part?

This :something:otherThing is not very understable.

[Csaba Meszaros, geändert vor 7 Jahren.]

dependencies {
compile project(":modules:minthaka.registration.resource")
}

in fragment's build.gradle compiles, but the strings remain unrecognized, and the fragment happily did start without the resource module.