Hope, you are managing to get what you want done.

I thought it was worth pointing out that the header.xsl file is only
the veru first section of the build report. The build report is
actually built up from many such sections:

   header.xsl
   compiler.xsl
   modifications.xsl

Just to name a few.

When the build is performed, the various tasks write progress/test/
build data to xml files. During the publishing stage these files can
be collated into the one main build log file (also an xml file) by
using the merge task in the publisher section.

You can then write a xsl file to parse the main build log and
dynamically pull out and render the information that is of importance
to your.

I missed a useful link: http://www.w3schools.com/xsl/

XPath is the method by which you reference the elements in the xml log
file. XSL (or XSLT) is the language used to write the dynamic style
sheets for presenting the information.

For examples, just browse through the existing xsl files, starting
with the header.xsl. See if you can work out what is does.

You will also need to know about CSS as this is used to define the
global look and feel.

Regards,
Shaun



On 23 Jan, 13:41, CinnamonDonkey <[email protected]>
wrote:
> Reading:
>
>    http://www.w3schools.com/XPath/default.asp
>    http://www.w3schools.com/css/default.asp
>    http://www.w3schools.com/HTML/default.asp
>
> Helped me big time! I was in the same situation last week.
>
> Hope this helps,
> Regards,
> Shaun
>
> On 23 Jan, 13:17, "Terry Hunt" <[email protected]> wrote:
>
> > Hi,
>
> > I am really green at xsl, like I have never worked with them, but U want
> > to add the value of the external link from my ccnet.config to appear in
> > my build report.  I know that header.xsl is the file that generates this
> > report, but I have not been able to make this happen.  Has anyone done
> > this that might could send me a sample? or am I barking up the wrong
> > tree :)
>
> > Thanks,
> > Terry
>
> > This e-mail message and any attachments are for the sole use
> > of the intended recipient(s) and may contain confidential
> > information. If you are not an intended recipient, or an
> > intended recipient's authorized agent, you are hereby notified
> > that any dissemination, distribution or copying of this e-mail
> > message or any attachments is strictly prohibited. If you have
> > received this message in error, please notify the sender by
> > reply e-mail and delete this e-mail message and any attachments
> > from your computer system.

Reply via email to