Skip navigation
david.karr
david.karr Calculating status...
Currently Being Moderated

How to get Vault plugin to report failure when the targetURL connection fails?

Apr 30, 2012 7:24 PM

Tags: #vault #targeturl

We're seeing a situation with the Vault plugin where when the call to the "targetURL" results in a server error, it reports that in the build output, but the plugin doesn't report a failure, so it looks like the build was successful. If you're not paying attention, you'll miss the Vault plugin failure.  It doesn't matter why the call to the targetURL fails, it's just a symptom on the server.  What's the issue here is that when that fails, the plugin should also fail, but it doesn't.

1680 Views   2 Replies   Latest reply: Justin Edelson, May 2, 2012 3:17 PM
 
Replies
  • david.karr
    Currently Being Moderated
    1. david.karr,
    May 1, 2012 10:25 AM   in reply to david.karr
    Report

    If it matters, here's some build output to show the vault plugin failing, but it not causing the build to fail.

     

    [INFO] [executor:install {execution: default-cli}]

    [INFO] [vault:install {execution: virtual-execution}]

    [INFO] Installing ... (....zip) to http://localhost:7001/crx/packmgr/service.jsp

    [ERROR] Request to http://localhost:7001/crx/packmgr/service.jsp failed, response=Internal Server Error

    [INFO] --------------------------------------------------------------------- ---

    [INFO] BUILD SUCCESSFUL

    [INFO] --------------------------------------------------------------------- ---

    [INFO] Total time: 22 seconds

    [INFO] Finished at: Mon Apr 30 16:19:29 PDT 2012

     
    |
    Mark as:
  • Justin Edelson
    264 posts
    Nov 24, 2010
    Currently Being Moderated
    2. Justin Edelson,
    May 2, 2012 3:17 PM   in reply to david.karr
    Report

    This feature was added last year using the configuration property name failOnError. You need to change to the new content-package-maven-plugin, the successor to the maven-vault-plugin.

     

    For backwards-compatibility reasons, the default is false.

     

    Something like this should work:

    <plugin>

        <groupId>com.day.jcr.vault</groupId>

        <artifactId>content-package-maven-plugin</artifactId>

        <version>0.0.13</version>

        <configuration>

            <failOnError>true</failOnError>

        ...other config...

        </configuration>

    </plugin>

     

    With the exception of some fairly esoteric goals which were only used internally, the content-package-maven-plugin is entirely backwards compatible with the maven-vault-plugin.

     

    Regards,

    Justin

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points