Why work out of archive path?

[logankoester]

I believe I have a common use case...

1. Prepare Compile my project code to a .gitignored' output/ directory
2. Test Build Docker image (Dockerfile copies output/ into the image) and run tests
3. Deploy Push the Docker image on success

However, this plugin operates in a separate archive path, so everything that was compiled in the Prepare phase is inaccessible to Docker when it tries to build the image.

What is the rationale for doing it this way?

[knownasilya]

None specifically I think. There just wasn't a use case presented. 👍

How do you see this working? Specifying a path for the archive with a default to what it is now?

[logankoester]

@knownasilya I've got it working the way I like in #11. Feedback welcome, but let's move the discussion to that thread.