[I'm not sure which project to file this issue under; it's really linuxfoundation.org infrastructure related, not "odlparent" (code) specific... is this more of a helpdesk@ than a BZ kinda thing? Or can we have a LF JIRA about this instead of this BZ?]

In the context of ODLPARENT-116 for ODL to be able to use the external null annotations (EEA; see e.g. http://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Ftasks%2Ftask-using_external_null_annotations.htm) coming together from the http://lastnpe.org in the build of some ODL projects, I would have to frequently cut releases of https://github.com/lastnpe/eclipse-null-eea-augments/tree/master/libraries and often deploy to Maven central (as I have on https://repo1.maven.org/maven2/org/lastnpe/eea/, once).

However, this is likely going to be a major PITA, especially in the early days and during ongoing dev cycles (it will be different as the EEA repo becomes more mature later, and when we cut ODL releases with it later as well).

Therefore, in an ideal world it would be neat if http://nexus.opendaylight.org could proxy some (TBD) external Maven repo where I would continuously deploy (CD, e.g. using travis-ci.org) SNAPSHOT EEA JARs to from https://github.com/lastnpe/eclipse-null-eea-augments/tree/master/libraries (e.g. on Bintray.com, or wherever).

Requires https://github.com/lastnpe/eclipse-null-eea-augments/issues/14