Well, for now, I guess you can just do your release and if it is done, just copy only the .sha1 and .asc but not the .md5 to dist :-).
I'm not even sure they are generated by us - I somewhat remember them being generated by the repository.a.o automagically... regards, Karl On Mon, Jul 9, 2018 at 5:07 PM Raymond Auge <[email protected]> wrote: > > Hey all, > > How do we change our poms to prevent obsolete md5 generation? > > Karl just went through a cleanup of these and I don't want to make more > cleanup work :) > > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> > (@Liferay) > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance) -- Karl Pauls [email protected]
