]
Brett Meyer updated ARTIF-709:
------------------------------
Summary: Allow artifact expansion to be dynamically configurable during runtime (was:
Allow artifact expansion to be enabled/disabled during each upload)
Allow artifact expansion to be dynamically configurable during
runtime
----------------------------------------------------------------------
Key: ARTIF-709
URL:
https://issues.jboss.org/browse/ARTIF-709
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
Expansion is useful in some cases (especially API jars, etc.). However, in others,
it's actually pretty harmful. Ex: pushing in a project's ZIP distro, a large WAR
with all its dependency JARs, etc. Currently, Artificer would get overwhelmed with the
amount of info to pull out.
Suggestion:
1.) Expansion disabled by default
2.) Enable with checkbox on web UI, argument on CLI, argument on Java client, etc.
3.) If *not* expanded, the relationship builders should still kick in. So, the contents
would still be parsed. If it contains, for example, a WSDL that imports an XSD or a Java
class that impls an API interface, the relationships should still be created. But those
relationships would point to the archive itself, rather than an expanded/derived artifact.