Re: [cross-project-issues-dev] eclipse-signing-maven-plugin - Could not

[Igor Fedorenko <ifedorenko@xxxxxxxxxxxx>]

I "deployed" the new eclipse jarsigner plugin to [1]. This is not ideal,
but I plan to keep this download directory 'forever', so it should be
good enough solution for the time being.

I've also enabled this for m2e project, which has both pom-first build
[2] and manifest-first build [3]. Depending on kind of build you
have, you should be able to just copy&paste relevant profile to your
parent pom.

If anyone has questions about the new jarsigner plugin, I'll be happy to
answer them either here, or, probably better, on cbi-dev mailing list.

[1] http://download.eclipse.org/technology/m2e/maven/
[2] 
https://git.eclipse.org/c/m2e/m2e-core.git/tree/m2e-maven-runtime/pom.xml?id=2c0d905fb262e8e1f7b886538118cba4a9e34c01#n128
[3] 
https://git.eclipse.org/c/m2e/m2e-core.git/tree/pom.xml?id=2c0d905fb262e8e1f7b886538118cba4a9e34c01#n210

--
Regards,
Igor

On 12-08-15 9:49 AM, Matthias Sohn wrote:
> let us know when this new signing plugin is available
>
> --
> Matthias
>
> 2012/8/15 Igor Fedorenko <ifedorenko@xxxxxxxxxxxx
> <mailto:ifedorenko@xxxxxxxxxxxx>>
>
>     Short term it maybe faster to deploy eclipse-signing-maven-plugin to one
>     of existing maven forgers, like oss.sonatype.org
>     <http://oss.sonatype.org> we run, and use it from
>     there. At least this is what I plan to do for the new signing plugin I
>     wrote for cbi build.
>
>     --
>     Regards,
>     Igor
>
>
>     On 12-08-15 9:15 AM, Markus Tiede wrote:
>
>         Hello,
>
>         The Jubula team is currently blocked building our Juno SR1 RC1
>         artifacts
>         on hudson.eclipse.org <http://hudson.eclipse.org> due to a
>         problem with the
>         eclipse-signing-maven-plugin: "Could not setup plugin ClassRealm /
>         ZipException: error in opening zip file"...
>
>         I reopened and commented the following ticket to track the status of
>         this issue (which seems to have re-occurred multiple times in
>         the recent
>         past for different projects):
>         https://bugs.eclipse.org/bugs/__show_bug.cgi?id=382238#c8
>         <https://bugs.eclipse.org/bugs/show_bug.cgi?id=382238#c8>
>
>         Does anyone know how to  resolve this issue for the short term?
>
>         With best regards,
>         MarkusT
>         _________________________________________________
>         cross-project-issues-dev mailing list
>         cross-project-issues-dev@__eclipse.org
>         <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>         https://dev.eclipse.org/__mailman/listinfo/cross-__project-issues-dev
>         <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>
>
>     _________________________________________________
>     cross-project-issues-dev mailing list
>     cross-project-issues-dev@__eclipse.org
>     <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>     https://dev.eclipse.org/__mailman/listinfo/cross-__project-issues-dev <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>
>
>
>
>
> --
> Matthias
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev