Parents (Total: 3)

The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	D77668C53A843343D20BFEECCEBA5C39
PackageArch	noarch
PackageDescription	[b"Ant is a platform-independent build tool for java. It's used by apache\njakarta and xml projects.", b"Ant e' un tool indipendente dalla piattaforma creato per faciltare la\ncompilazione di programmi java.\nAllo stato attuale viene utilizzato dai progetti apache jakarta ed\napache xml.", b'Ant est un outil de compilation multi-plateformes pour java. Il est\nutilis\xc3\xa9 par les projets apache-jakarta et apache-xml.']
PackageMaintainer	Fedora Project
PackageName	ant
PackageRelease	3.fc15
PackageVersion	1.8.2
SHA-1	FADDB8B51D2629340E9348BE61D872169A63C0BA
SHA-256	97972209D49785D14785C017B1D5BBE339D01BEFF8305074F62D293D0ABA3F6B

Key	Value
MD5	F33F7191168B299F2E8BC750A3BB43CE
PackageArch	noarch
PackageDescription	Apache Ant is a Java-based build tool. In theory, it is kind of like Make, but without Make's wrinkles. Why another build tool when there is already make, gnumake, nmake, jam, and others? Because all those tools have limitations that Ant's original author could not live with when developing software across multiple platforms. Make-like tools are inherently shell-based--they evaluate a set of dependencies then execute commands, not unlike what you would issue in a shell. This means that you can easily extend these tools by using or writing any program for the OS that you are working on. However, this also means that you limit yourself to the OS, or at least the OS type, such as Unix, that you are working on. Makefiles are inherently evil as well. Anybody who has worked on them for any time has run into the dreaded tab problem. "Is my command not executing because I have a space in front of my tab???" said the original author of Ant way too many times. Tools like Jam took care of this to a great degree, but still have yet another format to use and remember. Ant is different. Instead of a model where it is extended with shell-based commands, Ant is extended using Java classes. Instead of writing shell commands, the configuration files are XML-based, calling out a target tree where various tasks are executed. Each task is run by an object that implements a particular task interface. Granted, this removes some of the expressive power that is inherent by being able to construct a shell command such as `find . -name foo -exec rm {}`, but it gives you the ability to be cross-platform--to work anywhere and everywhere. If you really need to execute a shell command, Ant has an <exec> task that allows different commands to be executed based on the OS used.
PackageName	ant-antlr
PackageRelease	8.1
PackageVersion	1.8.2
SHA-1	3946084BBDF036CB43DCE1439EB1E15001C1970A
SHA-256	11C3B9DC4B6710AC8F123CA267DBE8CFFD0669121C9ECC661D5B15ADF602A97E

Key	Value
MD5	1636BEFCCFBFD771D3C8F832FE674EE9
PackageArch	noarch
PackageDescription	Apache Ant is a Java-based build tool. In theory, it is kind of like Make, but without Make's wrinkles. Why another build tool when there is already make, gnumake, nmake, jam, and others? Because all those tools have limitations that Ant's original author could not live with when developing software across multiple platforms. Make-like tools are inherently shell-based--they evaluate a set of dependencies then execute commands, not unlike what you would issue in a shell. This means that you can easily extend these tools by using or writing any program for the OS that you are working on. However, this also means that you limit yourself to the OS, or at least the OS type, such as Unix, that you are working on. Makefiles are inherently evil as well. Anybody who has worked on them for any time has run into the dreaded tab problem. "Is my command not executing because I have a space in front of my tab???" said the original author of Ant way too many times. Tools like Jam took care of this to a great degree, but still have yet another format to use and remember. Ant is different. Instead of a model where it is extended with shell-based commands, Ant is extended using Java classes. Instead of writing shell commands, the configuration files are XML-based, calling out a target tree where various tasks are executed. Each task is run by an object that implements a particular task interface. Granted, this removes some of the expressive power that is inherent by being able to construct a shell command such as `find . -name foo -exec rm {}`, but it gives you the ability to be cross-platform--to work anywhere and everywhere. If you really need to execute a shell command, Ant has an <exec> task that allows different commands to be executed based on the OS used.
PackageName	ant
PackageRelease	10.1
PackageVersion	1.8.2
SHA-1	646F4165ACBBA364D6FC587AEB9224613FA518F2
SHA-256	B6229AE90A304124F0ABD75FF2861C731461248330A84500EE1C79F1886500BA