There are numerous examples of this in the Jenkins source code.
One is in AbstractBuild's index.jelly, including actions' summary.jelly to the
main page of the build:
<j:forEach var="a" items="${it.actions}">
<st:include page="summary.jelly" from="${a}" optional="true"
it="${a}" />
</j:forEach>
https://github.com/jenkinsci/jenkins/blob/stable/core/src/main/resources/hudson/model/AbstractBuild/index.jelly
On 12.11.2013, at 09:47, Thomas Åkerlund <[email protected]> wrote:
> Hi!
>
> I have written a plugin that extends Builder. I have then created an
> extention point for other plugins to use. I want to reference those
> sub-plugins specific jelly file from the "main-plugins" jelly file. I know
> how to do a forEach and get the data etc. What I don't know is how to get the
> path to the specific jelly file in one of the sub-plugins. If I just had the
> installation path to the plugin I could probably solve it that way.
>
> So for example, if the AnsiColor plugin was a sub-plugin to my plugin I would
> want there to be a method in the AnsiColor plugin that would return the file
> path:
> D:\Software\Jenkins\Jenkins
> Home\plugins\ansicolor\WEB-INF\lib\classes.jar\hudson\plugins\ansicolor\AnsiColorBuildWrapper\sublayout.jelly
>
> Any suggestions or solutions are appreciated!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
