[ALL] hashes of signatures

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[ALL] hashes of signatures

Matt Benson-3
The release procedures mention the problem of these extraneous files in the
Nexus staging repo. I have noticed during the last couple of [weaver]
release cycles that these files no longer show up and had thought it was
something they had fixed on Nexus. Then I rolled a vote candidate for
Apache BVal and find the files are there on the staging repo. Is anyone
aware of having fixed this issue in the Commons build? I can't find any
config that seems relevant.

Thanks,
Matt
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] hashes of signatures

Stian Soiland-Reyes
In Commons RDF we used this:

                <plugins>
                    <plugin>
   <!-- Avoid making *.asc.asc -->
                        <groupId>org.apache.maven.plugins</groupId>
                        <artifactId>maven-gpg-plugin</artifactId>
                        <configuration>
                            <excludes>
                                <exclude>**/*.asc</exclude>
                                <exclude>**/*.md5</exclude>
                                <exclude>**/*.sha1</exclude>
                            </excludes>
                        </configuration>
                    </plugin>
                </plugins>

is that sufficient in Bval?  If so we can add it to commons-parent.



On 31 October 2016 at 15:58, Matt Benson <[hidden email]> wrote:

> The release procedures mention the problem of these extraneous files in the
> Nexus staging repo. I have noticed during the last couple of [weaver]
> release cycles that these files no longer show up and had thought it was
> something they had fixed on Nexus. Then I rolled a vote candidate for
> Apache BVal and find the files are there on the staging repo. Is anyone
> aware of having fixed this issue in the Commons build? I can't find any
> config that seems relevant.
>
> Thanks,
> Matt



--
Stian Soiland-Reyes
http://orcid.org/0000-0001-9842-9718

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] hashes of signatures

Matt Benson-2
Thanks for repying, but that seems backward: signatures of hashes. I'm
talking about ending up with *.jar.asc.md5 and *.jar.asc.sha1 . :)

Matt

On Mon, Oct 31, 2016 at 11:32 AM, Stian Soiland-Reyes <[hidden email]>
wrote:

> In Commons RDF we used this:
>
>                 <plugins>
>                     <plugin>
>    <!-- Avoid making *.asc.asc -->
>                         <groupId>org.apache.maven.plugins</groupId>
>                         <artifactId>maven-gpg-plugin</artifactId>
>                         <configuration>
>                             <excludes>
>                                 <exclude>**/*.asc</exclude>
>                                 <exclude>**/*.md5</exclude>
>                                 <exclude>**/*.sha1</exclude>
>                             </excludes>
>                         </configuration>
>                     </plugin>
>                 </plugins>
>
> is that sufficient in Bval?  If so we can add it to commons-parent.
>
>
>
> On 31 October 2016 at 15:58, Matt Benson <[hidden email]> wrote:
> > The release procedures mention the problem of these extraneous files in
> the
> > Nexus staging repo. I have noticed during the last couple of [weaver]
> > release cycles that these files no longer show up and had thought it was
> > something they had fixed on Nexus. Then I rolled a vote candidate for
> > Apache BVal and find the files are there on the staging repo. Is anyone
> > aware of having fixed this issue in the Commons build? I can't find any
> > config that seems relevant.
> >
> > Thanks,
> > Matt
>
>
>
> --
> Stian Soiland-Reyes
> http://orcid.org/0000-0001-9842-9718
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] hashes of signatures

Charles Honton
There was an update in parent to prevent excess jars from being attached as artifacts.

https://svn.apache.org/viewvc/view=revision&revision=1755904


I don't believe it's been released.

Chas

> On Oct 31, 2016, at 9:53 AM, Matt Benson <[hidden email]> wrote:
>
> Thanks for repying, but that seems backward: signatures of hashes. I'm
> talking about ending up with *.jar.asc.md5 and *.jar.asc.sha1 . :)
>
> Matt
>
> On Mon, Oct 31, 2016 at 11:32 AM, Stian Soiland-Reyes <[hidden email]>
> wrote:
>
>> In Commons RDF we used this:
>>
>>                <plugins>
>>                    <plugin>
>>   <!-- Avoid making *.asc.asc -->
>>                        <groupId>org.apache.maven.plugins</groupId>
>>                        <artifactId>maven-gpg-plugin</artifactId>
>>                        <configuration>
>>                            <excludes>
>>                                <exclude>**/*.asc</exclude>
>>                                <exclude>**/*.md5</exclude>
>>                                <exclude>**/*.sha1</exclude>
>>                            </excludes>
>>                        </configuration>
>>                    </plugin>
>>                </plugins>
>>
>> is that sufficient in Bval?  If so we can add it to commons-parent.
>>
>>
>>
>>> On 31 October 2016 at 15:58, Matt Benson <[hidden email]> wrote:
>>> The release procedures mention the problem of these extraneous files in
>> the
>>> Nexus staging repo. I have noticed during the last couple of [weaver]
>>> release cycles that these files no longer show up and had thought it was
>>> something they had fixed on Nexus. Then I rolled a vote candidate for
>>> Apache BVal and find the files are there on the staging repo. Is anyone
>>> aware of having fixed this issue in the Commons build? I can't find any
>>> config that seems relevant.
>>>
>>> Thanks,
>>> Matt
>>
>>
>>
>> --
>> Stian Soiland-Reyes
>> http://orcid.org/0000-0001-9842-9718
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] hashes of signatures

Matt Benson-2
Hi Chas,
  I saw that change but the hashes of signatures to which I am referring
applied to all uploaded artifacts, not just the source archives. :)

Matt

On Mon, Oct 31, 2016 at 1:06 PM, Chas Honton <[hidden email]> wrote:

> There was an update in parent to prevent excess jars from being attached
> as artifacts.
>
> https://svn.apache.org/viewvc/view=revision&revision=1755904
>
>
> I don't believe it's been released.
>
> Chas
>
> > On Oct 31, 2016, at 9:53 AM, Matt Benson <[hidden email]> wrote:
> >
> > Thanks for repying, but that seems backward: signatures of hashes. I'm
> > talking about ending up with *.jar.asc.md5 and *.jar.asc.sha1 . :)
> >
> > Matt
> >
> > On Mon, Oct 31, 2016 at 11:32 AM, Stian Soiland-Reyes <[hidden email]>
> > wrote:
> >
> >> In Commons RDF we used this:
> >>
> >>                <plugins>
> >>                    <plugin>
> >>   <!-- Avoid making *.asc.asc -->
> >>                        <groupId>org.apache.maven.plugins</groupId>
> >>                        <artifactId>maven-gpg-plugin</artifactId>
> >>                        <configuration>
> >>                            <excludes>
> >>                                <exclude>**/*.asc</exclude>
> >>                                <exclude>**/*.md5</exclude>
> >>                                <exclude>**/*.sha1</exclude>
> >>                            </excludes>
> >>                        </configuration>
> >>                    </plugin>
> >>                </plugins>
> >>
> >> is that sufficient in Bval?  If so we can add it to commons-parent.
> >>
> >>
> >>
> >>> On 31 October 2016 at 15:58, Matt Benson <[hidden email]> wrote:
> >>> The release procedures mention the problem of these extraneous files in
> >> the
> >>> Nexus staging repo. I have noticed during the last couple of [weaver]
> >>> release cycles that these files no longer show up and had thought it
> was
> >>> something they had fixed on Nexus. Then I rolled a vote candidate for
> >>> Apache BVal and find the files are there on the staging repo. Is anyone
> >>> aware of having fixed this issue in the Commons build? I can't find any
> >>> config that seems relevant.
> >>>
> >>> Thanks,
> >>> Matt
> >>
> >>
> >>
> >> --
> >> Stian Soiland-Reyes
> >> http://orcid.org/0000-0001-9842-9718
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>