Am 2016-08-17 um 21:57 schrieb Paul Benedict:
Yes, it is valid for a ZIP to contain class files. However, I don't believe
Maven should create a bias here for Java. The ZIP file type, in its
objective form, has nothing to do with Java. It just so happens Java chose
to support that file type as a source of classes.
As as a consequence, a ZIP file could be either of the two use cases in a
project.... and MNG-6080 explains how to handle that:
(1) default handling is to treat ZIP files as a mere container
I agree here. No assumptions shall be made since this is a generic
container but it does not mean that it doesn't has be to a second-class
type of artifact in the system.
On Wed, Aug 17, 2016 at 2:37 PM, Michael Osipov <micha...@apache.org> wrote:
Am 2016-08-17 um 19:20 schrieb Paul Benedict:
I'm in in the thought process of MNG-6080 and MNG-5567, and I have an idea
to run by the dev folks here:
A ZIP file is a type of resource. A resource artifact gets a new scope to
remain in the reactor but does not contribute to the compiling process or
runtime environment. It's up to the build to determine how to consume it
(via some other mechanism like input into a plugin). But is a ZIP artifact
really any different from any other kind of non-functional artifact? What
about text files, markdown files, or any other kind of non-code resource
you want to share and use?
One such thought of mine was people who want to deploy OSS license files.
Instead of keeping a static copy in a project for distribution bundling,
it
could be part of a project dependency and added. I am pretty sure there
are
Maven plugins specifically built for this -- but are these plugin to
workaround the absence of native functionality?
So the big philosophical question is...
If a ZIP file is just a resource, then perhaps it's not a new Maven "zip"
type that should be supported... it should be a new Maven "resource" type
that can be any kind of file.
Thoughts?
As per definition, ZIP files can also contain class files. Perfectly
valid. Additionally, a lot of people are wating for MNG-1683 just like you
and me. I would require to solve this issue first before we continue
discussion.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
