ShrinkWrap: How to replace a file in an artifact resolved with MavenDependencyResolver.

gistfile1.java

public static WebArchive getTestPreparedArchive() {
    WebArchive war = ShrinkWrap.create(WebArchive.class, "service.war")
            .addClasses(MyClass1.class, MyClass2.class); // add classes needed for the test

    // Resolve the needed dependency independently, so we can replace the production persistence.xml inside the archive
    Collection<JavaArchive> archives = DependencyResolvers.use(MavenDependencyResolver.class)
            .artifact("se.diabol.persistence:Persistence_Framework:jar:0.1-SNAPSHOT").resolveAs(JavaArchive.class);

    // Resolve the actual archive
    JavaArchive p = null;
    for (JavaArchive jar : archives) {
        if (jar.getName().equals("Persistence_Framework-0.1-SNAPSHOT.jar")) {
            p = jar;
            break;
        }
    }
    if (p == null)
        throw new IllegalStateException("Could not resolve desired artifact");

    // Replace production persistence.xml with test context version
    p.delete("/META-INF/persistence.xml");
    p.add(new ClassLoaderAsset("test-persistence.xml"), "/META-INF/persistence.xml");

    // Add the manipulated dependency to the test archive
    war.addAsLibrary(p);
    return war;
}

Cool, now thats good news! What I was trying to say was, in this case I do not need transitive dependencies, but sometimes I do, depending on what I'm testing. It would be convenient if I could delete an asset and add a new one (as the persistence.xml in this case) directly from the DSL, without having to create intermediate/temporary objects.