nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Percivall <>
Subject Re: Incorporation of other Maven repositories
Date Fri, 06 Nov 2015 15:18:23 GMT
As no issues were brought up, I'm going to assume that everyone is ok with adding Bintray JCenter
as a repo. I plan on using it in a patch for 0.4.0 in which I'm refactoring InvokeHttp. The
patch is dependent on a lib to add digest authentication that is only hosted there.

- - - - - - 
Joseph Percivall

On Tuesday, November 3, 2015 4:52 PM, Matthew Burgess <> wrote:
Bintray JCenter ( is also moderated and
claims to be "the repository with the biggest collection of Maven artifacts
in the world". I think Bintray itself proxies out to Maven Central, but it
appears that for JCenter you choose to sync your artifacts with Maven

I imagine trust is still a per-organization or per-artifact issue, but
Bintray claims to be even safer and more trustworthy than Maven Central
(source:  For
my (current) work and home projects, I still resolve from Maven Central, but
I have been publishing my own artifacts to Bintray.


From:  Aldrin Piri <>
Reply-To:  <>
Date:  Tuesday, November 3, 2015 at 12:34 PM
To:  <>
Subject:  Incorporation of other Maven repositories

I am writing to see what the general guidance and posture is on
incorporating additional repositories into the build process.

Obviously, Maven Central provides a very known quantity.  Are there other
repositories that are viewed with the same level of trust?  If so, is there
a listing? If not, do we vet new sources as they bring libraries that aid
our project and how is this accomplished?

Incorporating other repos brings up additional areas of concern,
specifically availability but also some additional security considerations
to the binaries that are being retrieved.

Any thoughts on this front would be much appreciated.

View raw message