|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MNBMODULE-188) would be nice make n... Eric Barboni (JIRA)
- [mojo-dev] [jira] (MNBMODULE-188) would be nice m... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-188) would be nice m... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-188) would be nice m... Eric Barboni (JIRA)
- [mojo-dev] [jira] (MNBMODULE-188) would be nice m... Eric Barboni (JIRA)
- [mojo-dev] [jira] (MNBMODULE-188) would be nice m... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-188) would be nice m... Milos Kleint (JIRA)

please see which mojos define the brandingToken parameter, AFAIK its mostly the nbm-app mojos, maybe also the branding one. That means that branding module and application have to share the same brandingToken. regular modules should be brandingToken agnostic.
Where it's read from depends entirely on the setup of your project. if archetype defines it in the parent, then it's only a property of the archetype that assumes just one application. But that can be changed by you.
I would suggest the following setup for multiple applications
root (pom)
--> app1-parent (pom)
----> app1 (nbm-application)
----> app1-branding (nbm)
--> app2-parent (pom)
----> app2 (nbm-application)
----> app2-branding (nbm)
--> cluster1 (pom)
----> .. here come modules..
... here come additional clusters if your app is big and needs clusters..