I think it's reasonable that a Maven GAV might have several associated with it, using different artifact classifiers. For now, the only concrete use case I have generates exactly one, but I don't think I'd want it restricted that way. On 11/02/2015 10:08 AM, Mike McLean wrote: > --- > docs/schema.sql | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/docs/schema.sql b/docs/schema.sql > index d5ffa87..df9f36d 100644 > --- a/docs/schema.sql > +++ b/docs/schema.sql > @@ -755,6 +755,7 @@ insert into archivetypes (name, description, > extensions) values ('vhd', 'Hyper-V > insert into archivetypes (name, description, extensions) values ('wsf', > 'Windows script file', 'wsf'); > insert into archivetypes (name, description, extensions) values ('box', > 'Vagrant Box Image', 'box'); > insert into archivetypes (name, description, extensions) values > ('raw-xz', 'xz compressed raw disk image', 'raw.xz'); > +insert into archivetypes (name, description, extensions) values > ('groovy', 'Groovy script file', 'groovy gvy'); > > > -- Do we want to enforce a constraint that a build can only generate one > > _______________________________________________ koji-devel mailing list koji-devel(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/koji-devel