So you could overlay createmenu.soy in your Plugin (or Theme), and change the @depends entry for main.js accordingly (or add another @depends).
I am having a similar issue. However in my case, I have added a new .soy file with my own namespace (I'm not trying to overlay anything, just trying to create new UI in my own soy files). In the SoyTemplateRegistryImpl class, it sees my file in readThemes, but its not being parsed in parseAll. Also because I'm in devMode, the files aren't being compiled.
Am I missing something? In the admin console, my file shows up. When I try rendering my file using:
<@soy.render template="mynamespace.nav.navbar" data=skin.navBarViewProvider.getNavBarInstance(selLink) />
I get the error in the console:
java.lang.IllegalArgumentException: No associated path found for template 'mynamespace.nav.navbar'. Please verify that this template exists.
[INFO] [talledLocalContainer] at com.jivesoftware.community.web.soy.SoyResourceBundler.getTofu(SoyResourceBundler.java:307)
I'm hitting the same thing. I need to break up the navbar Soy template into two pieces, and I'm trying to do it in the theme. Jive picks up the customizations to the existing 'navbar' template but using the new template I added to navbar.soy throws the same error:
No associated path found for template
Anyone find a solution for this? I really don't want to create an entire plugin for a single soy file.
Looks like it's a Known Issue with 5.0.1 (JIVE-8629):
5.0.2 release notes don't have it as fixed but it's not on the 5.0.2 Known Issues list either. I have to assume this hasn't been fixed yet. Plugin hack it is I suppose.