Download JAR files tagged by making with all dependencies
sirix-parent from group io.sirix (version 0.9.3)
Sirix is a temporal storage system effectively and efficiently storing snapshots of
time varying (currently semi-structured) data taking full advantage of flash based drives as for
instance SSDs. We not only provide several ways of navigating the tree-structure of a single
revision, we also support navigation in time. Furthermore we provide a novel storage technique
called sliding snapshot to circumvent intermitant full dump snapshots to fast track their
in-memory reconstruction and thus we avoiding write peaks and having to read long chains of page
fragments/increments/deltas. Sirix uses copy-on-write (COW) as well as an append-only storage
making it an ideal candidate for flash based drives while not dropping support for erstwhile
disks.
Group: io.sirix Artifact: sirix-parent
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact sirix-parent
Group io.sirix
Version 0.9.3
Last update 29. July 2019
Organization not specified
URL https://sirix.io
License New BSD
Dependencies amount 14
Dependencies jcommander, aspectjrt, slf4j-api, perfidix, xmlunit, logback-classic, logback-core, guice, gson, guava, guava-testlib, jsr305, brackit, caffeine,
There are maybe transitive dependencies!
Group io.sirix
Version 0.9.3
Last update 29. July 2019
Organization not specified
URL https://sirix.io
License New BSD
Dependencies amount 14
Dependencies jcommander, aspectjrt, slf4j-api, perfidix, xmlunit, logback-classic, logback-core, guice, gson, guava, guava-testlib, jsr305, brackit, caffeine,
There are maybe transitive dependencies!
git-commit-id-plugin from group at.molindo (version 2.1.10-alpha-1)
git-commit-id-plugin is a plugin quite similar to
https://fisheye.codehaus.org/browse/mojo/tags/buildnumber-maven-plugin-1.0-beta-4 for example but as buildnumber
only supports svn (which is very sad) and cvs (which is even more sad).
This plugin makes basic repository information available through maven resources. This can be used to display
"what version is this?" or "who has deployed this and when, from which branch?" information at runtime - making
it easy to find things like "oh, that isn't deployed yet, I'll test it tomorrow" and making both testers and
developers life easier.
The data currently exported is like this (that's the end effect from the GitRepositoryState Bean):
{
"branch" : "testing-maven-git-plugin",
"commitTime" : "06.01.1970 @ 16:16:26 CET",
"commitId" : "787e39f61f99110e74deed68ab9093088d64b969",
"commitUserName" : "Konrad Malawski",
"commitUserEmail" : "[email protected]",
"commitMessageFull" : "releasing my fun plugin :-) + fixed some typos + cleaned up directory structure + added
license etc",
"commitMessageShort" : "releasing my fun plugin :-)",
"buildTime" : "06.01.1970 @ 16:17:53 CET",
"buildUserName" : "Konrad Malawski",
"buildUserEmail" : "[email protected]"
}
Note that the data is exported via maven resource filtering and is really easy to use with spring -
which I've explained in detail in this readme https://github.com/ktoso/maven-git-commit-id-plugin
Artifact git-commit-id-plugin
Group at.molindo
Version 2.1.10-alpha-1
Last update 28. December 2015
Organization not specified
URL http://www.blog.project13.pl
License GNU Lesser General Public License 3.0
Dependencies amount 8
Dependencies maven-plugin-api, maven-project, jackson-databind, guice, joda-time, guava, annotations, org.eclipse.jgit,
There are maybe transitive dependencies!
Group at.molindo
Version 2.1.10-alpha-1
Last update 28. December 2015
Organization not specified
URL http://www.blog.project13.pl
License GNU Lesser General Public License 3.0
Dependencies amount 8
Dependencies maven-plugin-api, maven-project, jackson-databind, guice, joda-time, guava, annotations, org.eclipse.jgit,
There are maybe transitive dependencies!
mydas from group uk.ac.ebi.mydas (version 1.0.2)
This project aims to offer an easy-to-extend Java DAS server framework.
It offers several advantages:
* Implementing data sources is very easy but also flexible and powerful.
* Data caching is built into the system, with access to the caching
mechanism made available to the data sources.
* All aspects of the server are highly configurable, including
selecting options where the DAS 1.53 specification offers
choices to the implementor.
* The latest Java technologies have been used throughout the
system to optimise performance and simplify data source development.
* Wherever possible the same terminology is used in the API as in
the DAS specification and XML - again, making data source
development more easy.
* The server allows XSLT transforms of the DAS XML to be configured
to provide a simple DAS client view (limited to the single DAS
source).
More details of the DAS protocol, DAS servers and DAS clients can
be found at http://www.biodas.org/wiki/Main_Page.
The first version of this server is a complete implementation of
Distributed Sequence Annotation System (DAS) Version 1.53.
If you are interested in learning more about DAS 1.53, the
specification is highly recommended as a concise and complete
description of the DAS protocol that can be obtained from:
http://biodas.org/documents/spec.html
Artifact mydas
Group uk.ac.ebi.mydas
Version 1.0.2
Last update 19. August 2007
Organization not specified
URL http://code.google.com/p/mydas/
License The Apache Software License 2.0
Dependencies amount 7
Dependencies commons-collections, servlet-api, log4j, xpp3, xercesImpl, oscache, commons-logging,
There are maybe transitive dependencies!
Group uk.ac.ebi.mydas
Version 1.0.2
Last update 19. August 2007
Organization not specified
URL http://code.google.com/p/mydas/
License The Apache Software License 2.0
Dependencies amount 7
Dependencies commons-collections, servlet-api, log4j, xpp3, xercesImpl, oscache, commons-logging,
There are maybe transitive dependencies!
ironpdf from group com.ironsoftware (version 2024.4.1)
IronPDF Java library offers an extensive compatibility range, making it a go-to solution for a wide array of developers. It fully supports JVM languages like Java, Scala, and Kotlin, making it incredibly versatile. This Java PDF library is also compatible with Java 8 and above, providing optimum performance across multiple platforms. It's been designed with a wide range of users in mind Here's a look at what it supports: JVM Languages: Java, Scala, Kotlin.Platforms: Java 8 and above.Operating Systems: Microsoft Windows, Linux, Docker, Azure, AWS.IDEs: Jetbrains IntelliJ IDEA, Eclipse. You can deploy IronPDF Java across various platforms, including Microsoft Windows, Linux, Docker, Azure, and AWS. It is also fully compatible with popular IDEs like Jetbrains IntelliJ IDEA and Eclipse, facilitating smooth project development and management. Your pom.xml file is essentially the backbone of your project when you're using Maven. It's here where you introduce new dependencies that you wish to include. To make IronPDF Java package a part of your Maven project, you simply need to add the following snippets to your pom.xml: Remember to replace '20xx.xx.xxxx' with the latest version of IronPDF. IronPDF Java simplifies the process of creating PDF files. Convert HTML files, HTML strings, or URLs directly to new PDF documents in a few lines of code. The variety of file formats it handles is vast, as it can even transform images into PDF documents and vice versa. Need to use base 64 encoding, base URLs, or custom file paths? No problem! IronPDF Java has got you coveredFor more detail about installing and using IronPDF Java. When you run your project for the first time post-integration, IronPDF's engine binaries will automatically be downloaded. The engine starts its journey when you call any IronPDF function for the first time and takes a breather when your application is either closed or enters an idle state. It is not an open source java PDF library but here's the best part - IronPDF Java is offering a 30-day free trial. So, why wait? Give it a go and boost your PDF operations today.
0 downloads
Artifact ironpdf
Group com.ironsoftware
Version 2024.4.1
Last update 17. April 2024
Organization Iron Software
URL https://ironpdf.com/java/
License Proprietary License
Dependencies amount 8
Dependencies commons-io, commons-lang3, grpc-netty-shaded, grpc-protobuf, grpc-stub, grpc-protobuf, javax.annotation-api, slf4j-api,
There are maybe transitive dependencies!
Group com.ironsoftware
Version 2024.4.1
Last update 17. April 2024
Organization Iron Software
URL https://ironpdf.com/java/
License Proprietary License
Dependencies amount 8
Dependencies commons-io, commons-lang3, grpc-netty-shaded, grpc-protobuf, grpc-stub, grpc-protobuf, javax.annotation-api, slf4j-api,
There are maybe transitive dependencies!
SourceAnalyst from group io.github.leravolcevska (version 1.3.0)
The Source Analyst library is a powerful tool designed to streamline and expedite the tracking of traffic sources for mobile applications. This versatile library is aptly named "Source Analyst" and is an invaluable asset for app developers and marketers seeking to gain deeper insights into the performance of their advertising campaigns. With just one simple function call, Source Analyst empowers you to efficiently investigate the effectiveness of various advertising sources.
Key Features:
Effortless Tracking: Source Analyst simplifies the complex task of tracking the origins of traffic for your mobile app. No need for convoluted setups or extensive coding – one function is all it takes.
Comprehensive Insights: Gain a comprehensive understanding of where your app's users are coming from. Whether it's through social media, search engines, referral links, or other channels, Source Analyst provides you with clear data on traffic sources.
Performance Evaluation: Evaluate the performance of your advertising campaigns with precision. Discover which sources are driving the most valuable users to your app, helping you optimize your marketing efforts effectively.
Time-Saving: Say goodbye to hours spent on manual data collection and analysis. Source Analyst automates the tracking process, freeing up your time to focus on making data-driven decisions.
Customization: Tailor Source Analyst to your specific needs. Customize the library to track the metrics that matter most to your app's success.
Real-time Data: Access real-time data, ensuring that you always have up-to-date insights into your traffic sources.
Integration-Friendly: Seamlessly integrate Source Analyst into your existing mobile app infrastructure, whether you're developing for Android or iOS.
User-Friendly: Source Analyst is designed with user-friendliness in mind. Its intuitive interface and straightforward documentation make it accessible to developers of all levels of expertise.
How It Works:
Using Source Analyst is as easy as calling a single function within your code. Simply integrate the library into your app, and you can begin tracking traffic sources immediately. From there, Source Analyst compiles and presents the data in a clear and organized manner, allowing you to make data-driven decisions with ease.
In a world where understanding the origins of your app's traffic is essential for marketing success, Source Analyst is the go-to solution. Say goodbye to the complexity of tracking sources and embrace the simplicity and effectiveness of Source Analyst for your mobile app.
Harness the power of Source Analyst and unlock a new level of insight into your app's performance today!
Group: io.github.leravolcevska Artifact: SourceAnalyst
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact SourceAnalyst
Group io.github.leravolcevska
Version 1.3.0
Last update 07. September 2023
Organization not specified
URL https://github.com/leravolcevska/SourceAnalyst
License MIT License
Dependencies amount 1
Dependencies kotlin-stdlib-jdk8,
There are maybe transitive dependencies!
Group io.github.leravolcevska
Version 1.3.0
Last update 07. September 2023
Organization not specified
URL https://github.com/leravolcevska/SourceAnalyst
License MIT License
Dependencies amount 1
Dependencies kotlin-stdlib-jdk8,
There are maybe transitive dependencies!
chips-n-salsa from group org.cicirello (version 6.4.0)
Chips-n-Salsa is a Java library of customizable,
hybridizable, iterative, parallel, stochastic, and self-adaptive
local search algorithms. The library includes implementations of
several stochastic local search algorithms, including simulated
annealing, hill climbers, as well as constructive search algorithms
such as stochastic sampling. Chips-n-Salsa now also includes genetic
algorithms as well as evolutionary algorithms more generally. The
library very extensively supports simulated annealing. It includes
several classes for representing solutions to a variety of optimization
problems. For example, the library includes a BitVector class that
implements vectors of bits, as well as classes for representing
solutions to problems where we are searching for an optimal vector
of integers or reals. For each of the built-in representations, the
library provides the most common mutation operators for generating
random neighbors of candidate solutions, as well as common crossover
operators for use with evolutionary algorithms. Additionally, the
library provides extensive support for permutation optimization
problems, including implementations of many different mutation
operators for permutations, and utilizing the efficiently implemented
Permutation class of the JavaPermutationTools (JPT) library.
Chips-n-Salsa is customizable, making extensive use of Java's generic
types, enabling using the library to optimize other types of representations
beyond what is provided in the library. It is hybridizable, providing
support for integrating multiple forms of local search (e.g., using a hill
climber on a solution generated by simulated annealing), creating hybrid
mutation operators (e.g., local search using multiple mutation operators),
as well as support for running more than one type of search for the same
problem concurrently using multiple threads as a form of algorithm portfolio.
Chips-n-Salsa is iterative, with support for multistart metaheuristics,
including implementations of several restart schedules for varying the run
lengths across the restarts. It also supports parallel execution of multiple
instances of the same, or different, stochastic local search algorithms for
an instance of a problem to accelerate the search process. The library
supports self-adaptive search in a variety of ways, such as including
implementations of adaptive annealing schedules for simulated annealing,
such as the Modified Lam schedule, implementations of the simpler annealing
schedules but which self-tune the initial temperature and other parameters,
and restart schedules that adapt to run length.
0 downloads
Artifact chips-n-salsa
Group org.cicirello
Version 6.4.0
Last update 28. July 2023
Organization Cicirello.Org
URL https://chips-n-salsa.cicirello.org/
License GPL-3.0-or-later
Dependencies amount 3
Dependencies jpt, rho-mu, core,
There are maybe transitive dependencies!
Group org.cicirello
Version 6.4.0
Last update 28. July 2023
Organization Cicirello.Org
URL https://chips-n-salsa.cicirello.org/
License GPL-3.0-or-later
Dependencies amount 3
Dependencies jpt, rho-mu, core,
There are maybe transitive dependencies!
web-grid from group org.apache.oodt (version 1.0)
The OODT grid services (product and profile services) use CORBA or
RMI as their underlying network transport. However, limitations
of CORBA and RMI make them inappropriate for large-scale
deployments. For one, both are procedural mechanisms, providing a
remote interface that resembles a method call. This makes
streaming of data from a service impossible, because there are
limitations to the sizes of data structures that can be passed
over a remote method call. Instead, repeated calls must be made
to retrieve each block of a product, making transfer speeds
horribly slow compared to HTTP or FTP. (Block-based retrieval of
profiles was never implemented, resulting in out of memory
conditions for large profile results, which is another problem.)
Second, both CORBA and RMI rely on a central name registry. The
registry makes an object independent of its network location,
enabling a client to call it by name (looking up its last known
location in the registry). However, this requires that server
objects be able to make outbound network calls to the registry
(through any outbound firewall), and that the registry accept
those registrations (through any inbound firewall). This required
administrative action at institutions hosting server objects and
at the institution hosting the registry. Often, these firewall
exceptions would change without notice as system adminstrators
changed at each location (apparently firewall exceptions are
poorly documented everywhere). Further, in the two major
deployments of OODT (PDS and EDRN), server objects have almost
never moved, nullifying any benefit of the registry. This
project, OODT Web Grid Services, avoids the prolems of CORBA and
RMI by using HTTP as the transport mechanism for products and
profiles. Further, it provides a password-protected mechanism to
add new sets of product and profile query handlers, enabling
seamless activation of additional capabilities.
Group: org.apache.oodt Artifact: web-grid
Show all versions Show documentation
Show all versions Show documentation
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact web-grid
Group org.apache.oodt
Version 1.0
Last update 21. June 2016
Organization not specified
URL Not specified
License not specified
Dependencies amount 7
Dependencies apache-jena-libs, oodt-commons, oodt-product, oodt-profile, oodt-xmlquery, xalan, xercesImpl,
There are maybe transitive dependencies!
Group org.apache.oodt
Version 1.0
Last update 21. June 2016
Organization not specified
URL Not specified
License not specified
Dependencies amount 7
Dependencies apache-jena-libs, oodt-commons, oodt-product, oodt-profile, oodt-xmlquery, xalan, xercesImpl,
There are maybe transitive dependencies!
beast-tool from group es.upm.dit.gsi (version 0.9.9)
BEhavioural Agents Simple Testing Tool - BEAST Tool
The aim of this project is the development of a system which allows Behavior Driven Development (BDD) in Multi-Agent Systems (MAS), to make testing practices more accessible and intuitive to everybody.
In one hand, in order to let tests be writable by newcomers and experts alike, system must allow the redaction of tests in plain text, because client does not need to have knowledge of our code. This plain text will be traduced to software later.
The definition of test will be realized with the terminology Given-When-Then, which allows trace an easy guide of the behavior of a given scenario when something happened.
In the other hand, due to the complexity of MAS, making unit testing of an agent that needs the interaction with others is almost impossible until the whole system is finished. This implies to leave testing issues to the end of the project, generating big troubles in case of malfunction. Consequently, its necessary to carry out a tool to allow the creation of mock agents and to perform tests during the whole development process. Therefore another objective of our systems is to include a mocking tool which permits testing continuously.
Definitively, our tool allows the testing of any MAS in the development process, increasing its modularity and decreasing its elaboration and testing cost. These tests will be written in plain text so that anyone would be able to understand them.
For further reading, a paper published in ITMAS2012 workshop can be found in: http://scholar.google.es/citations?view_op=view_citation&hl=es&user=mT3KgXUAAAAJ&citation_for_view=mT3KgXUAAAAJ:Tyk-4Ss8FVUC
0 downloads
Artifact beast-tool
Group es.upm.dit.gsi
Version 0.9.9
Last update 03. June 2014
Organization Grupo de Sistemas Inteligentes - Universidad Politécnica de Madrid
URL http://www.gsi.dit.upm.es/index.php/es/tecnologia/software/221-beast-tool.html
License GNU General Public License, version 2
Dependencies amount 27
Dependencies mockito-all, junit, maven-surefire-plugin, jbehave-web, jaxme2, jbehave-core, log4j, jadex-kernel-bdibpmn, jadex-kernel-micro, jadex-platform-standalone, jadex-runtimetools, jadex-applications-micro, jadex-bridge, jadex-kernel-base, jadex-kernel-extension-agr, jadex-tools-bdi, jadex-applib-bdi, jadex-kernel-application, jadex-applications-bdibpmn, jadex-applications-bpmn, jadex-applications-gpmn, jadex-kernel-gpmn, jadex-nuggets, jadex-rules-applications, jadex-tools-bpmn, jadex-tools-comanalyzer, jade,
There are maybe transitive dependencies!
Group es.upm.dit.gsi
Version 0.9.9
Last update 03. June 2014
Organization Grupo de Sistemas Inteligentes - Universidad Politécnica de Madrid
URL http://www.gsi.dit.upm.es/index.php/es/tecnologia/software/221-beast-tool.html
License GNU General Public License, version 2
Dependencies amount 27
Dependencies mockito-all, junit, maven-surefire-plugin, jbehave-web, jaxme2, jbehave-core, log4j, jadex-kernel-bdibpmn, jadex-kernel-micro, jadex-platform-standalone, jadex-runtimetools, jadex-applications-micro, jadex-bridge, jadex-kernel-base, jadex-kernel-extension-agr, jadex-tools-bdi, jadex-applib-bdi, jadex-kernel-application, jadex-applications-bdibpmn, jadex-applications-bpmn, jadex-applications-gpmn, jadex-kernel-gpmn, jadex-nuggets, jadex-rules-applications, jadex-tools-bpmn, jadex-tools-comanalyzer, jade,
There are maybe transitive dependencies!
PerScope from group io.github.danielandroidtt (version 1.4.0)
Introducing "PerScope" Library: Simplifying Privacy Policy Event Handling for Android Apps
"PerScope" is a cutting-edge library designed to streamline the processing of privacy policy events within regions where compliance with local legislation is crucial. Specifically crafted for Android applications, this library addresses the intricate task of managing privacy policy-related events while adhering to the legal requirements of the country in which the app is deployed.
In today's digital landscape, ensuring user privacy and data protection is of paramount importance. Different countries have varying legal frameworks dictating how user data should be handled, necessitating robust mechanisms to accommodate these differences seamlessly. This is where the "PerScope" library shines.
The key feature that sets "PerScope" apart is its incredible simplicity. With just a single function call, developers can integrate the library into their Android applications and gain immediate access to a comprehensive suite of tools for managing privacy policy events. Whether it's presenting privacy-related notifications, tracking user consents, or adapting the app's behavior based on regional requirements, "PerScope" handles it all efficiently and effectively.
Here's a glimpse of what "PerScope" brings to the table:
Localized Compliance: "PerScope" empowers developers to align their apps with the privacy laws of each region. By intelligently detecting the user's location, the library ensures that the app's behavior remains compliant with the specific privacy regulations of that area.
Event Handling Made Easy: Instead of grappling with complex event management code, developers can integrate the "PerScope" function, drastically reducing development time and effort. The library takes care of the intricate event handling process seamlessly.
Dynamic Adaptation: With the ability to dynamically adapt the app's features based on the user's consent and the local legal requirements, "PerScope" ensures a personalized and compliant user experience.
Notification Presentation: "PerScope" assists in presenting privacy-related notifications to users, making it easier to inform them about data collection practices and obtain necessary consents.
Smooth Integration: The library is designed to be easily integrated into existing Android applications, minimizing disruptions to the development process.
In a nutshell, "PerScope" is a developer's go-to solution for managing privacy policy events within Android apps. Its single-function approach, combined with its capacity to handle a complex and critical aspect of app development, makes it an indispensable tool for app creators aiming to provide a user-centric, privacy-respecting experience while complying with regional legislation. Stay on the right side of the law and prioritize user privacy with the power of "PerScope."
Group: io.github.danielandroidtt Artifact: PerScope
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact PerScope
Group io.github.danielandroidtt
Version 1.4.0
Last update 27. August 2023
Organization not specified
URL https://github.com/DanielAndroidTT/PerScope
License MIT License
Dependencies amount 1
Dependencies kotlin-stdlib-jdk8,
There are maybe transitive dependencies!
Group io.github.danielandroidtt
Version 1.4.0
Last update 27. August 2023
Organization not specified
URL https://github.com/DanielAndroidTT/PerScope
License MIT License
Dependencies amount 1
Dependencies kotlin-stdlib-jdk8,
There are maybe transitive dependencies!
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
- 58
- 59
- 60
- 61
- 62
- 63
- 64
- 65
- 66
- 67
- 68
- 69
- 70
- 71
- 72
- 73
- 74
- 75
- 76
- 77
- 78
- 79
- 80
- 81
- 82
- 83
- 84
- 85
- 86
- 87
- 88
- 89
- 90
- 91
- 92
- 93
- 94
- 95
- 96
- 97
- 98
- 99
- 100
- 101
- 102
- 103
- 104
- 105
- 106
- 107
- 108
- 109
- 110
- 111
- 112
- 113
- 114
- 115
- 116
- 117
- 118
- 119
- 120
- 121
- 122
- 123
- 124
- 125
- 126
- 127
- 128
- 129
- 130
- 131
- 132
- 133
- 134
- 135
- 136
- 137
- 138
- 139
Page 139 from 139 (items total 1389)