[ https://issues.jboss.org/browse/ARTIF-709?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-709: ------------------------------ Description: Expansion is useful and necessary, especially for relationship definitions. However, in some contexts, it can expand too much. Ex: uploading a large WAR, how do we differentiate between 3rd party dependency JARs (probably shouldn't be expanded) and application-provided JARs (should be expanded)? The answer could be some sort of UI interactivity that allows users to configure the expansion (nested lists with checkboxes?) prior to persisting... was: 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. -- This message was sent by Atlassian JIRA (v6.3.15#6346)