Hi Nagarajan,

3.9-beta-3 has been released and is synched to Maven Central Repository:

http://jbehave.org/reference/preview/dependencies.html

Cheers

On 20/11/2013 12:45, Nagarajan Ganesan wrote:
Hi Mauro,

We are running as maven build.

Can we add a dependency to this snapshot?

Please provide the dependency details.

Thanks,
Nagarajan


On Thu, Nov 14, 2013 at 5:04 AM, Mauro Talevi <[email protected] <mailto:[email protected]>> wrote:

    The snapshot is already available on
    https://nexus.codehaus.org/content/groups/snapshots-group/

    A release will follow soon.

    On 12/11/2013 13:55, Nagarajan Ganesan wrote:
    Hi Mauro,

    Thanks for the fix.

    When this will be available in maven?

    Thanks,
    Nagarajan




    On Mon, Nov 11, 2013 at 9:19 PM, Mauro Talevi
    <[email protected] <mailto:[email protected]>>
    wrote:

        There was a classloading issue fixed in JBEHAVE-959.

        Please try latest snapshot and here a working example with
        custom FTL resources.

        
https://github.com/jbehave/jbehave-core/blob/master/examples/core/src/main/java/org/jbehave/examples/core/CustomCoreStories.java


        On 11/11/2013 12:41, Nagarajan Ganesan wrote:
        I'm running this as Maven build.

        Please help me.

        Thanks,
        Nagarajan


        On Mon, Nov 11, 2013 at 3:46 PM, Nagarajan Ganesan
        <[email protected] <mailto:[email protected]>> wrote:

            Hi Mauro,

            Thanks for your reply.

            I tried add the different file name as below:


            /viewResources.put("decorateNonHtml", "true");/

            /viewResources.put("reports",
            "ftl/new-reports-with-totals.ftl");/


            It ended with exception file not found for the template.

            I gave the full file path in the property and tried
            still there was a same file not found exception.

            Is it still referring with in the jar for the path
            specified in the viewResources?

            Please help me.

            Thanks,
            Nagarajan.


            On Mon, Nov 11, 2013 at 12:54 PM, Mauro Talevi
            <[email protected]
            <mailto:[email protected]>> wrote:

                The ftl resources is read from the classpath.  As
                such if you change it, you need to ensure it is the
                classpath and is available before the original
                one.   That can be tricky.

                The recommended way is to change the name of the
                modified template, e.g. ftl/company-reports.ftl and
                configure the viewResources properties accordingly.

                On 11/11/2013 08:18, Nagarajan Ganesan wrote:

                Hi All,

                We are jbehave for our BDD testing. Thanks for the
                active support about this.

                I need to use the customized ftl.

                I have made some changes in the file
                /ftl/jbehave-reports-with-totals.ftl /and hence
                trying use the same for HTML report generation.

                I kept this file under my ftl folder of the workspace.

                I referred the TraderStories.java file of the
                Trader example and did like the same in our code.

                Properties viewResources = new Properties();

                viewResources.put("decorateNonHtml", "true");

                viewResources.put("reports",
                "ftl/jbehave-reports-with-totals.ftl");

                Used this viewResources in configuration.

                The problem is that the jbehave refers to the ftl
                file bundled in the jar and not my modified ftl file.

                I do not want to have additional new ftl files. I
                just did some changes in the bundled ftl files and
                kept in my work space. How to make refer to those
                updated templates while generating html reports?

                Please advice. Thanks in advance.

                Thanks,

                Nagarajan.









Reply via email to