On Mon, Jul 9, 2018 at 11:19 AM, Karl Pauls <[email protected]> wrote:
> 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... > Yup, I wasn't sure if we could eliminate the wasted cycles. But you're right, I can just omit them from dist.. but I cannot from the release repo. But it's not a big deal. - Ray > > 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] > -- *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)
