So what's the preferred practice for jdks and similar items that required manual download?
It seems that manually placing them in the target directory like .local/easybuild/sources/j/java is potentially error prone and not immediately obvious. It would be better to have a way to say "find this upstream in the cwd of where I'm calling eb, or this explicit path" or something similar. Is there such a direction? ~jpr On 03/23/2016 02:29 AM, Martin wrote: > To my knowledge Ward is correct. You might search the interwebs for > various solutions to the URL. I usually simply download it but I found > the actual culprit is that easybuild doesn't manage the sources in > terms of it doesn't place them in the sources directory configured if > it can find it in the current directory. > > On Tue, Mar 22, 2016 at 3:47 PM Ward Poelmans <ward.poelm...@ugent.be > <mailto:ward.poelm...@ugent.be>> wrote: > > On 22-03-16 15:40, John-Paul Robinson wrote: > > Hi, > > > > How are folks dealing with staging jdk downloads for ebs that > require > > them. Given the Oracle process for accessing the jdks require > logins, > > we find it necessary to manually place the jdk file in the > > .local/easybuild/sources/j/java directory. > > > > Is this the reality of downloads that require authn or is there some > > feature to do this more cleanly? > > I thought that it is possible to do it automatically but it's not > legal > to do it? > > Ward > > -- > -- > http://www.xing.com/profile/Martin_Marcher > http://www.linkedin.com/in/martinmarcher > Mobil: +43 / 660 / 62 45 103 > UID: ATU68801424
