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 wrote:
> There was an update in parent to prevent excess jars from being
There was an update in parent to prevent excess jars from being attached as
artifacts.
https://svn.apache.org/viewvc/view=revision=1755904
I don't believe it's been released.
Chas
> On Oct 31, 2016, at 9:53 AM, Matt Benson wrote:
>
> Thanks for repying, but that
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
wrote:
> In Commons RDF we used this:
>
>
>
In Commons RDF we used this:
org.apache.maven.plugins
maven-gpg-plugin
**/*.asc
**/*.md5
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
Here's an approach we used in Jena with partial success:
https://github.com/apache/jena/tree/master/apache-jena-osgi/jena-osgi-test
Uses PaxExam - https://ops4j1.jira.com/wiki/display/paxexam/Pax+Exam
On 31 October 2016 at 15:22, Matt Sicker wrote:
> Oh, yes, rc2 is
Oh, yes, rc2 is cancelled. I forgot to clean up.
And yes, help is appreciated. I haven't had a chance to look back at this,
but one of the things we wanted to accomplish with this bug fix was to also
introduce a pattern for black box testing Commons libraries in OSGi.
On 31 October 2016 at
Hi, Matt,
Was this DBCP Release Candidate vote cancelled..? I noticed it is still in
https://repository.apache.org/content/repositories/orgapachecommons-1196/
https://dist.apache.org/repos/dist/dev/commons/dbcp/DBCP_2_2_RC2/
BTW - do you need some help with
OK, I built 'LUDecomposition' back to match the original Jama version and
fixed a few things on the way. Performance is consistently much better and I
did not notice any differences in numerical accuracy. While this appears to
be the same algorithm, I have not figured out why (though I can see