Okay cool. The same will apply for the following modules:
o.eclipse.mylyn.commons.core o.eclipse.mylyn.commons.net o.eclipse.mylyn.commons.repositories.core o.eclipse.mylyn.commons.xmlrpc o.eclipse.mylyn.tasks.core o.eclipse.mylyn.wikitext.confluence.core o.eclipse.mylyn.wikitext.core o.eclipse.mylyn.wikitext.markdown.core o.eclipse.mylyn.wikitext.textile.core Each of these have a single dependency thats no longer in maven. I'll make a note of them in their respective comments sections. Regards John On 11 October 2017 at 13:39, Emilian Bold <[email protected]> wrote: > There is no need for such a list. We can easily extract external > binaries without Maven coordinates. > > Right now we can just rely on http://hg.netbeans.org/binaries/ but > going forward we'll have to find another place where to store our > dependencies. Perhaps publish them ourselves to Maven Central under > org.netbeans.external or some other groupId? > > --emi > > > On Wed, Oct 11, 2017 at 3:36 PM, John McDonnell > <[email protected]> wrote: >> Looking at the module o.eclipse.mylyn.bugzilla.core and I cannot find >> the external binary: >> >> org.eclipse.mylyn.bugzilla.core_3.17.0.v20150828-2026.jar >> >> I've checked https://search.maven.org and the last/only version of >> this is: 2.0.0-v20070627-1400 >> >> I can't seem to find the binary to download, except maybe if I use >> eclipse and an update centre there to see if I can download the binary >> which isn't great. >> >> Any ideas what to do when you cant find the binary? - Are we >> maintaining a list of such items etc? >> >> Regards >> >> John -- John
