Uploaded image for project: 'ShrinkWrap'
  1. ShrinkWrap
  2. SHRINKWRAP-329

Arquillian should fail-fast when adding the same resource twice to an archive made with ExplodedImporter.class

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 1.1.0-alpha-1
    • None
    • None
    • None

    Description

      This didn't fail fast for me:

          @Deployment
    public static WebArchive createDeployment() {
        WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class, "guvnor-webapp-5.3.0-SNAPSHOT.war")
                .importDirectory(new File("target/guvnor-webapp-5.3.0-SNAPSHOT/")) // already contains WEB-INF/classes/META-INF/beans.xml
                .as(WebArchive.class)
                .addAsResource(new File("target/test-classes/META-INF/test-beans.xml"), "WEB-INF/classes/META-INF/beans.xml")
                ...
        return webArchive;
    }

      Surprisingly, the second beans.xml didn't even overwrite the first one either. The second beans.xml was just ignored.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. SHRINKWRAP-388 Adding an Asset to already existing ArchivePath is silently ignored

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. SHRINKWRAP-416 Should not be able to overwrite an existing directory

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ARQ-585 Support for adding a beans-test.xml without discarding the original beans.xml or seam-beans.xml

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              arubinge@redhat.com Andrew Rubinger (Inactive)
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: