JBehave
  1. JBehave
  2. JBEHAVE-375

Add unpack-view-resources goal to Maven Plugin

    Details

    • Type: Improvement Improvement
    • Status: Resolved Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.1
    • Component/s: Maven Plugin
    • Labels:
      None
    • Number of attachments :
      0

      Description

      A goal to unpack the resources to the view directory. The main advantage over the maven dependency plugin is the ability to derived the view directory location from the configured StoryReporterBuilder accessible via the Embedder.

      The resources are configured as normal project artifacts and can be filtered based on the resource dependency type and artifactIds, via properties resourceType and resourceArtifacIds
      (which default to "zip" and

      {"jbehave-core", "jbehave-site-resources"}

      ).

      Resource content can optionally be filtered based on the resourceIncludes/Excludes properties.

        Activity

        Mauro Talevi made changes -
        Field Original Value New Value
        Status Open [ 1 ] In Progress [ 3 ]
        Mauro Talevi made changes -
        Summary Add unpack-resources goal to Maven Plugin Add unpack-view-resources goal to Maven Plugin
        Description A goal to unpack the resources to the view directory. The main advantage over the maven dependency plugin is the ability to derived the directory location from the configured StoryReporterBuilder accessible via the Embedder.

        The resources are configured as normal project artifacts and can be filtered based on the resource dependency type (by defaults all zip artifacts are allowed). Different types are configurable via the resourceTypes property.

        Resource content can optionally be filtered based on the resourceIncludes/Excludes properties.
        A goal to unpack the resources to the view directory. The main advantage over the maven dependency plugin is the ability to derived the view directory location from the configured StoryReporterBuilder accessible via the Embedder.

        The resources are configured as normal project artifacts and can be filtered based on the resource dependency type and artifactIds, via properties resourceType and resourceArtifacIds
        (which default to "zip" and {"jbehave-core", "jbehave-site-resources"}).

        Resource content can optionally be filtered based on the resourceIncludes/Excludes properties.
        Mauro Talevi made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Mauro Talevi
            Reporter:
            Mauro Talevi
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: