On Wed, 2015-07-01 at 14:37 -0700, Paul Rogers wrote: > > > > Download it. Seriously, nobody ever builds that kind of stuff from > > source unless they're actually modifying the library in question. > > When > > I decided long ago not to use anybody else's binaries if I could help > it. I want my system to be auditable. For a long time I had to use > Adobe's Flash & Oracle's JRE, but no longer.
Sure, and that's why we use LFS. But things like this - Java bytecode being platform independent and all, it's likely that any given release of a library like Junit is compiled exactly *once*, by the person creating a release to upload to the Maven repo. It's not going to be recompiled by different distros, for different target architectures. It's going to be built once by the project maintainer, published to the repo, and then the developers move on to developing the next version. > All statically linked into the downloaded package I believe, bloating > them and affecting performance. Nope. There's no such thing as static-linking in the Java world. At most, an unnecessary jar file sitting in the classpath will be a slight overhead in that it needs to be searched when loading classes. > > what it is, Junit is usually one of the first things on that list. > > So does that mean in order to get a proper LO build I have to figure > out > some way of getting a recognizable jar for? I've never built LO, so I can't give a definitive answer to that. But JUnit is just a testing framework (it's utterly ubiquitous in Java development), so if you're not running unit tests for LO, it's unlikely to be important. > As you know I don't know much about java and its component parts. I > thought about doing that. That's why I went to my CentOS-6 system. > I thought if a jar is like a tar, I could find out what's in the > expected junit.jar, match that against the snapshot, and try a > symlink if they match. But CentOS doesn't have the file either. So > I built without junit, and am still uncertain about the consequences > of doing that. A jar is a zip file with some extra metadata and structure, full of compiled Java class files. It's basically the Java equivalent of a shared library file (a .so or .dll). If you really want to find a copy of junit.jar, the link below is about as official as you'll get... supposedly there are around 10 million Java developers in the world, and that's where most of them will be getting it from. http://central.maven.org/maven2/junit/junit/4.12/junit-4.12.jar Simon. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
