for example, for declarative service, the scr/pom.xml currently uses the
latest felix-parent (version 6)
->
<parent>
<groupId>org.apache.felix</groupId>
<artifactId>felix-parent</artifactId>
<version>6</version>
<relativePath />
</parent>
and the felix-parent version 6 uses apache parent 21 (which is the latest
release):
->
<parent>^M
<groupId>org.apache</groupId>^M
<artifactId>apache</artifactId>^M
<version>21</version>^M
<relativePath />^M
</parent>^M
and in the apache parent 21, I see this:
->
<plugin>^M
<groupId>org.apache.maven.plugins</groupId>^M
<artifactId>maven-gpg-plugin</artifactId>^M
<version>1.6</version>^M
<configuration>^M
<gpgArguments>^M
<arg>--digest-algo=SHA512</arg>^M
</gpgArguments>^M
</configuration>^M
</plugin>^M
so, it should be at fine at least for the scr, i guess ?
cheers
pierre
On Wed, Oct 17, 2018 at 10:20 PM Raymond Auge <[email protected]>
wrote:
> Perhaps you're right. Perhaps that parent is just not applied to the
> projects I've released. I'll try it next time.
>
> Thanks Carsten.
>
> - Ray
>
> On Wed, Oct 17, 2018 at 4:03 PM Carsten Ziegeler <[email protected]>
> wrote:
>
> > I thought if we use the latest Apache pom as a parent than this is
> > solved. Isn't that the case?
> >
> > Carsten
> >
> > Am 17.10.2018 um 16:45 schrieb Raymond Auge:
> > > Hey everyone,
> > >
> > > We really need to fix the build to do sha512 and remove MD5.
> > >
> > > Anyone know the magic or can point me to an example where this is
> > > configured I'd appreciate it.
> > >
> > > Thanks,
> > >
> >
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > [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)
>
