Are my velocity templates technical debt?

[Paige L，修改在9 年前。]

It took our group awhile to get the SDK so we built up some technical debt. Apparently some of that technical debt is figuring out what is technical debt and what we did properly. One of our main sticking points are velocity templates.

We have a couple custom asset publisher and dynamic data list velocity templates to change their look. We need to save them so they're easily implementable for multiple Liferay instances. Currently, we just have them version controlled, but we were wondering if the correct policy was to have them saved as some sort of deployable plugin (possibly a hook) written in the SDK. Would this be possible/correct?

[Miroslav Ligas，修改在9 年前。]

I think that you can't currently include the ADT templates into a hook to be deployed in portal. You could probably create a update process that would read the template file and store it in the database but it is questionable if the effort if worth it.

[James Falkner，修改在9 年前。]

You can do it, but it's not very well documented and it's only possible to deploy ADTs programmatically to the global scope in a hook unless you are also willing to hard-code the name or ID of the group to which you wish to deploy (which is a terrible idea IMO).

Check out and vote for LPS-48095 and maybe it'll happen!

FYI I have also desired to have "real" versioning support for structures and templates -- and the good news is I believe it's going to be in the next major release (Liferay 7) - See LPS-52104 and LPS-50939! Woo!

[Miroslav Ligas，修改在9 年前。]

Interesting good to know that it is actually possible.

[Paige L，修改在9 年前。]

Thanks. That might not be what we want to do (if I'm understanding correctly), since we don't want any of the templates to apply universally (we've got a couple custom templates for asset publishers, for example). It's probably easiest and smartest for us to keep on doing what we've been doing (keeping the script source controlled externally), and if we upgrade to 7 eventually, we'll look into it then.

Thanks!

[Dave Weitzel，修改在8 年前。]

for the moment I would use a lar file

Allows you to then import into specific groups/sites. This doesn't help
with change control but certainly allows deployment. Some people I know
have an "init" portlet that will do this sort of thing but as stated it
goes to global scope by default.




On Thu, Apr 23, 2015 at 11:57 AM, Paige L from liferay.com <
[e-mail]> wrote:

> It took our group awhile to get the SDK so we built up some technical
> debt. Apparently some of that technical debt is figuring out what is
> technical debt and what we did properly. One of our main sticking points
> are velocity templates.
>
> We have a couple custom asset publisher and dynamic data list velocity
> templates to change their look. We need to save them so they're easily
> implementable for multiple Liferay instances. Currently, we just have them
> version controlled, but we were wondering if the correct policy was to have
> them saved as some sort of deployable plugin (possibly a hook) written in
> the SDK. Would this be possible/correct?
>
>
> To view the thread, follow the link below:
>
> https://www.liferay.com/community/forums/-/message_boards/view_message/52864894
> --
> Liferay.com <https://www.liferay.com>

[Dave Weitzel，修改在8 年前。]

for the moment I would use a lar file

Allows you to then import into specific groups/sites. This doesn't help
with change control but certainly allows deployment. Some people I know
have an "init" portlet that will do this sort of thing but as stated it
goes to global scope by default.




On Thu, Apr 23, 2015 at 11:57 AM, Paige L from liferay.com <
[e-mail]> wrote:

> It took our group awhile to get the SDK so we built up some technical
> debt. Apparently some of that technical debt is figuring out what is
> technical debt and what we did properly. One of our main sticking points
> are velocity templates.
>
> We have a couple custom asset publisher and dynamic data list velocity
> templates to change their look. We need to save them so they're easily
> implementable for multiple Liferay instances. Currently, we just have them
> version controlled, but we were wondering if the correct policy was to have
> them saved as some sort of deployable plugin (possibly a hook) written in
> the SDK. Would this be possible/correct?
>
>
> To view the thread, follow the link below:
>
> https://www.liferay.com/community/forums/-/message_boards/view_message/52864894
> --
> Liferay.com <https://www.liferay.com>

[Dave Weitzel，修改在8 年前。]

for the moment I would use a lar file

Allows you to then import into specific groups/sites. This doesn't help
with change control but certainly allows deployment. Some people I know
have an "init" portlet that will do this sort of thing but as stated it
goes to global scope by default.




On Thu, Apr 23, 2015 at 11:57 AM, Paige L from liferay.com <
[e-mail]> wrote:

> It took our group awhile to get the SDK so we built up some technical
> debt. Apparently some of that technical debt is figuring out what is
> technical debt and what we did properly. One of our main sticking points
> are velocity templates.
>
> We have a couple custom asset publisher and dynamic data list velocity
> templates to change their look. We need to save them so they're easily
> implementable for multiple Liferay instances. Currently, we just have them
> version controlled, but we were wondering if the correct policy was to have
> them saved as some sort of deployable plugin (possibly a hook) written in
> the SDK. Would this be possible/correct?
>
>
> To view the thread, follow the link below:
>
> https://www.liferay.com/community/forums/-/message_boards/view_message/52864894
> --
> Liferay.com <https://www.liferay.com>

[Dave Weitzel，修改在8 年前。]

for the moment I would use a lar file

Allows you to then import into specific groups/sites. This doesn't help
with change control but certainly allows deployment. Some people I know
have an "init" portlet that will do this sort of thing but as stated it
goes to global scope by default.




On Thu, Apr 23, 2015 at 11:57 AM, Paige L from liferay.com <
[e-mail]> wrote:

> It took our group awhile to get the SDK so we built up some technical
> debt. Apparently some of that technical debt is figuring out what is
> technical debt and what we did properly. One of our main sticking points
> are velocity templates.
>
> We have a couple custom asset publisher and dynamic data list velocity
> templates to change their look. We need to save them so they're easily
> implementable for multiple Liferay instances. Currently, we just have them
> version controlled, but we were wondering if the correct policy was to have
> them saved as some sort of deployable plugin (possibly a hook) written in
> the SDK. Would this be possible/correct?
>
>
> To view the thread, follow the link below:
>
> https://www.liferay.com/community/forums/-/message_boards/view_message/52864894
> --
> Liferay.com <https://www.liferay.com>

[Dave Weitzel，修改在8 年前。]

for the moment I would use a lar file

Allows you to then import into specific groups/sites. This doesn't help
with change control but certainly allows deployment. Some people I know
have an "init" portlet that will do this sort of thing but as stated it
goes to global scope by default.




On Thu, Apr 23, 2015 at 11:57 AM, Paige L from liferay.com <
[e-mail]> wrote:

> It took our group awhile to get the SDK so we built up some technical
> debt. Apparently some of that technical debt is figuring out what is
> technical debt and what we did properly. One of our main sticking points
> are velocity templates.
>
> We have a couple custom asset publisher and dynamic data list velocity
> templates to change their look. We need to save them so they're easily
> implementable for multiple Liferay instances. Currently, we just have them
> version controlled, but we were wondering if the correct policy was to have
> them saved as some sort of deployable plugin (possibly a hook) written in
> the SDK. Would this be possible/correct?
>
>
> To view the thread, follow the link below:
>
> https://www.liferay.com/community/forums/-/message_boards/view_message/52864894
> --
> Liferay.com <https://www.liferay.com>