[ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.... ] Brett Meyer edited comment on ARTIF-214 at 7/7/15 12:17 PM: ------------------------------------------------------------ Alternative: store the text file, but not as an artifact. Archive artifacts would have both their real content, as well as a "content list" stored. Both would be available through separate endpoints. The latter would also be available through a new UI tab. In general, I'm trying to avoid new derived artifact types if they are not useful on their own. In this case, it's purely additional metadata for an archive artifact, so I'd prefer to stick to a new field. Thoughts? was (Author: brmeyer): Alternative: store the text file, but not as an artifact. Archive artifacts would have both their real content, as well as a "content list" stored. Both would be available through separate endpoints. The latter would also be available through a new UI tab. -- This message was sent by Atlassian JIRA (v6.3.15#6346)