Result for 24E4280C29B7075C9D1FF9CFEA0B4E7B807E9163

Query result

Key Value
FileNameant.spec
FileSize40412
MD5751EEEFC642DB7AA360F20D377B2B03C
SHA-124E4280C29B7075C9D1FF9CFEA0B4E7B807E9163
SHA-256569E9DA2932CBCC6C5EFEF8667127C36797DB2B0B55AE04BA53A965D5C89CE54
SSDEEP768:5CSMiEufQjtPKDJqOta/9rKWqSCOtR+hCWHFn5oeRkk3kvzTdcNh3XzryRrV:5a7tPKDJqOta/9rKWqSCOqhCWHFn5oe4
TLSHT1E303E8333A445872E781F5D1B739BB60EB3590B8715C20B5B1CC6B78234599AF1BE0BA
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
MD51636BEFCCFBFD771D3C8F832FE674EE9
PackageArchnoarch
PackageDescriptionApache 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.
PackageNameant
PackageRelease10.1
PackageVersion1.8.2
SHA-1646F4165ACBBA364D6FC587AEB9224613FA518F2
SHA-256B6229AE90A304124F0ABD75FF2861C731461248330A84500EE1C79F1886500BA