I've noticed this in another email: Do note that Eclipse doesn't really use Maven Central but > https://repo.eclipse.org/content/groups/releases/ >
Take a look there too. I guess if this repo is the canonical source for those JARs we should use it. We have the hash to make sure it's the right binary. #maven-repository: eclipse > Is this a good idea? If the ant task is updated to use this, why not? How would it affect to the cached binaries? These are in .hgexternalcache anyhow... I doubt we'll have conflicts (same hash, no?). Should I downgrade binaries to previous versions and leave this for a > future enhancement? No, don't downgrade binaries. We are not beholden to Maven Central. --emi On Sun, Oct 15, 2017 at 12:29 PM, Antonio <[email protected]> wrote: > Hi all, > > > Modules "o.eclipse.core.**" contain binaries that are either hard or > impossible to find in Maven central. Some times the versions are not > exactly equal, and I'm not sure if we should downgrade to a previous > version or upgrade to a newest one. We're talking of old binaries > (2012/2013 in certain cases) that are possibly gone forever. > > Would it be possible to fetch these binaries from the > https://repo.eclipse.org/ maven repository instead? I think this has many > more versions that maven.central. (Don't know if this is the official > Eclipse maven repo, though). > > We could add some sort of key in external/binaries-list in order to select > a Maven repository. In order not to interfere with the existing contents we > could use a comment-tag to specify the repository. Something like: > > #maven-repository: eclipse > > Is this a good idea? How would it affect to the cached binaries? Should I > downgrade binaries to previous versions and leave this for a future > enhancement? > > Thanks, > Antonio >
