Download JAR files tagged by local with all dependencies
localOutlierFactor from group nz.ac.waikato.cms.weka (version 1.0.4)
A filter that applies the LOF (Local Outlier Factor) algorithm to compute an outlier score for each instance in the data. Can use multiple cores/cpus to speed up the LOF computation for large datasets. Nearest neighbor search methods and distance functions are pluggable.
For more information, see:
Markus M. Breunig, Hans-Peter Kriegel, Raymond T. Ng, Jorg Sander (2000). LOF: Identifying Density-Based Local Outliers. ACM SIGMOD Record. 29(2):93-104.
Group: nz.ac.waikato.cms.weka Artifact: localOutlierFactor
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact localOutlierFactor
Group nz.ac.waikato.cms.weka
Version 1.0.4
Last update 23. July 2013
Organization University of Waikato, Hamilton, NZ
URL http://weka.sourceforge.net/doc.packages/localOutlierFactor
License GNU General Public License 3
Dependencies amount 1
Dependencies weka-dev,
There are maybe transitive dependencies!
Group nz.ac.waikato.cms.weka
Version 1.0.4
Last update 23. July 2013
Organization University of Waikato, Hamilton, NZ
URL http://weka.sourceforge.net/doc.packages/localOutlierFactor
License GNU General Public License 3
Dependencies amount 1
Dependencies weka-dev,
There are maybe transitive dependencies!
mocca-core from group de.ovgu.dke.mocca (version 0.1.2)
MOCCA is the Message-Oriented Command and Context Architecture,
providing a GLUE middle-ware that allows sending commands to a
peer which are executed by state-less handlers in a specific
context. In contrast to the Request-Response scheme the message
flow is not fixed by the framework. This allows to implement
different communication paradigms (including Request-Response).
The whole system can be seen as an automaton with Messages that
trigger state transitions in the local Contexts.
This library contains the core components, including the
GLUE-based implementation.
0 downloads
Artifact mocca-core
Group de.ovgu.dke.mocca
Version 0.1.2
Last update 16. April 2013
Organization not specified
URL https://projects.dke-research.de/redmine/projects/mocca/
License The Apache Software License, Version 2.0
Dependencies amount 3
Dependencies glue-core, glue-util, jcip-annotations,
There are maybe transitive dependencies!
Group de.ovgu.dke.mocca
Version 0.1.2
Last update 16. April 2013
Organization not specified
URL https://projects.dke-research.de/redmine/projects/mocca/
License The Apache Software License, Version 2.0
Dependencies amount 3
Dependencies glue-core, glue-util, jcip-annotations,
There are maybe transitive dependencies!
jmdns from group com.github.rickyclarkson (version 3.4.2-r353-1)
JmDNS is a Java implementation of multi-cast DNS and can be used for service registration and discovery in local area networks. JmDNS is fully compatible with Apple's Bonjour.
The project was originally started in December 2002 by Arthur van Hoff at Strangeberry. In November 2003 the project was moved to SourceForge, and the name was changed from JRendezvous to JmDNS for legal reasons.
Many thanks to Stuart Cheshire for help and moral support.
Artifact jmdns
Group com.github.rickyclarkson
Version 3.4.2-r353-1
Last update 19. February 2013
Organization JmDNS
URL http://sourceforge.net/projects/jmdns/
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group com.github.rickyclarkson
Version 3.4.2-r353-1
Last update 19. February 2013
Organization JmDNS
URL http://sourceforge.net/projects/jmdns/
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
jmdns from group javax.jmdns (version 3.4.1)
JmDNS is a Java implementation of multi-cast DNS and can be used for service registration and discovery in local area networks. JmDNS is fully compatible with Apple's Bonjour.
The project was originally started in December 2002 by Arthur van Hoff at Strangeberry. In November 2003 the project was moved to SourceForge, and the name was changed from JRendezvous to JmDNS for legal reasons.
Many thanks to Stuart Cheshire for help and moral support.
Artifact jmdns
Group javax.jmdns
Version 3.4.1
Last update 25. August 2011
Organization JmDNS
URL http://sourceforge.net/projects/jmdns/
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group javax.jmdns
Version 3.4.1
Last update 25. August 2011
Organization JmDNS
URL http://sourceforge.net/projects/jmdns/
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
mydtt-plus-spring-boot-starter from group io.github.weasley-j (version 1.3.5)
MyDtt-Plus is a starter of spring-boot, It is an object-oriented Java framework that helps developers increase
productivity, "Domain Driven Table" is the concept of DTT, It makes you focus more on domain objects rather than
tables. Aims to make it easy to automatically create DB tables based on your Java model with annotation driven.
It's also support the ability of create table automatically for MyBatis what Hibernate can do and optionally
export SQL to local fileļ¼Each table can be added database name concat with table name and fully comments, It can
work with ORM frameworks such as MyBatis-Plus and MyBatis with little learning and usage costs. It's worth
mentioning that DTT can be MyBatis-Plus is integrated in a 0-code way, just like JPA. However, MyDtt-Plus and
MyBatis-Plus may be easier to expand and use than JPA. In addition to supporting the functions of JPA, DDT
provides multi-table associated SQL DDL based on MyBatis operation, DTT support databases server for MYSQL,
ORACLE, DB2, SQLSERVER, MARIADB, POSTGRESQL and embedded database for H2, HSQL, DERBY.
Group: io.github.weasley-j Artifact: mydtt-plus-spring-boot-starter
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact mydtt-plus-spring-boot-starter
Group io.github.weasley-j
Version 1.3.5
Last update 20. August 2022
Organization not specified
URL https://github.com/Weasley-J/mydtt-plus-spring-boot-starter
License GNU GENERAL PUBLIC LICENSE, Version 3
Dependencies amount 16
Dependencies spring-boot-starter-validation, spring-boot-starter-aop, spring-boot-starter, hutool-all, commons-lang3, commons-io, therapi-runtime-javadoc, jackson-databind, jackson-annotations, jackson-datatype-jsr310, spring-boot-starter-jdbc, velocity-engine-core, mybatis, mybatis-spring, mybatis-plus-core, jsqlparser,
There are maybe transitive dependencies!
Group io.github.weasley-j
Version 1.3.5
Last update 20. August 2022
Organization not specified
URL https://github.com/Weasley-J/mydtt-plus-spring-boot-starter
License GNU GENERAL PUBLIC LICENSE, Version 3
Dependencies amount 16
Dependencies spring-boot-starter-validation, spring-boot-starter-aop, spring-boot-starter, hutool-all, commons-lang3, commons-io, therapi-runtime-javadoc, jackson-databind, jackson-annotations, jackson-datatype-jsr310, spring-boot-starter-jdbc, velocity-engine-core, mybatis, mybatis-spring, mybatis-plus-core, jsqlparser,
There are maybe transitive dependencies!
com.sap.conn.jco.sapjco3 from group com.github.easonjim (version 3.0.11)
The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system.
It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java
to SAP System as well as SAP System to Java calls.
- All SAP Connectors are licensed without additional license fees as part of the respective solution or component license.
However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems /
SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed.
- The redistribution of any connector is not allowed.
- All SAP users accessing application functionality through the relevant connector are required to be licensed under a
respective solution or component license.
To use the SAP JCo with the jco-jar project, you need to either install the SAP JCo jar downloaded from SAP to your local
Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b):
(a) mvn install:install-file -DgroupId=com.github.easonjim -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.11 -Dpackaging=jar -Dfile=path/to/sapjco3.jar
(b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=com.github.easonjim -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.11 -Dpackaging=jar -Dfile=path/to/sapjco3.jar
0 downloads
Artifact com.sap.conn.jco.sapjco3
Group com.github.easonjim
Version 3.0.11
Last update 22. May 2019
Organization easonjim@github
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group com.github.easonjim
Version 3.0.11
Last update 22. May 2019
Organization easonjim@github
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
com.sap.conn.jco.sapjco3 from group org.hibersap (version 3.0.0)
The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system.
It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java
to SAP System as well as SAP System to Java calls.
- All SAP Connectors are licensed without additional license fees as part of the respective solution or component license.
However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems /
SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed.
- The redistribution of any connector is not allowed.
- All SAP users accessing application functionality through the relevant connector are required to be licensed under a
respective solution or component license.
To use the SAP JCo with the Hibersap project, you need to either install the SAP JCo jar downloaded from SAP to your local
Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b):
(a) mvn install:install-file -DgroupId=org.hibersap -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.15 -Dpackaging=jar -Dfile=path/to/sapjco3.jar
(b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=org.hibersap -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.15 -Dpackaging=jar -Dfile=sapjco3.jar
Artifact com.sap.conn.jco.sapjco3
Group org.hibersap
Version 3.0.0
Last update 08. March 2017
Organization akquinet tech@spree GmbH
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hibersap
Version 3.0.0
Last update 08. March 2017
Organization akquinet tech@spree GmbH
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
sapjco3 from group org.hibersap (version 3.0)
The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system.
It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java
to SAP System as well as SAP System to Java calls.
- All SAP Connectors are licensed without additional license fees as part of the respective solution or component license.
However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems /
SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed.
- The redistribution of any connector is not allowed.
- All SAP users accessing application functionality through the relevant connector are required to be licensed under a
respective solution or component license.
To use the SAP JCo with the Hibersap project, you need to either install the SAP JCo jar downloaded from SAP to your local
Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b):
(a) mvn install:install-file -DgroupId=org.hibersap -DartifactId=sapjco3 -Dversion=3.0.12 -Dpackaging=jar -Dfile=path/to/sapjco3.jar
(b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=org.hibersap -DartifactId=sapjco3 -Dversion=3.0.12 -Dpackaging=jar -Dfile=sapjco3.jar
4219 downloads
Artifact sapjco3
Group org.hibersap
Version 3.0
Last update 06. March 2015
Organization akquinet tech@spree GmbH
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hibersap
Version 3.0
Last update 06. March 2015
Organization akquinet tech@spree GmbH
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
hibersap-sapjco3 from group org.hibersap (version 3.0-RC01)
The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system.
It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java
to SAP System as well as SAP System to Java calls.
- All SAP Connectors are licensed without additional license fees as part of the respective solution or component license.
However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems /
SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed.
- The redistribution of any connector is not allowed.
- All SAP users accessing application functionality through the relevant connector are required to be licensed under a
respective solution or component license.
To use the SAP JCo with the Hibersap project, you need to either install the SAP JCo jar downloaded from SAP to your local
Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b):
(a) mvn install:install-file -DgroupId=org.hibersap -DartifactId=sapjco3 -Dversion=3.0 -Dpackaging=jar -Dfile=path/to/sapjco3.jar
(b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=org.hibersap -DartifactId=sapjco3 -Dversion=3.0 -Dpackaging=jar -Dfile=sapjco3.jar
87 downloads
Artifact hibersap-sapjco3
Group org.hibersap
Version 3.0-RC01
Last update 09. April 2014
Organization akquinet tech@spree GmbH
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hibersap
Version 3.0-RC01
Last update 09. April 2014
Organization akquinet tech@spree GmbH
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
org.pojava.datetime from group org.pojava (version 3.0.0)
POJava DateTime is a simple, light-weight Java-based API for parsing and manipulating dates.
It parses dates from most languages and formats out of the box without having to specify which
format is expected. Defaults such as time zones, and whether to interpret an internationally
ambiguous date like "03/06/2014" as DMY order or MDY order are inferred by system time zone
and locale and stored in a default config object that can be replaced or overridden. Multiple
languages for month names are supported without any additional configuration needed.
The net effect the default parser for a server in Paris would have a different automatic
configuration from a server in New York. Throw a random local date at either, and it'll
parse it as expected. If your server supports customers from multiple locales and time zones,
then each can be specified when parsing a date/time to resolve any ambiguities.
Artifact org.pojava.datetime
Group org.pojava
Version 3.0.0
Last update 11. March 2014
Organization not specified
URL http://www.pojava.org
License The Apache Software License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.pojava
Version 3.0.0
Last update 11. March 2014
Organization not specified
URL http://www.pojava.org
License The Apache Software License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
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
Page 119 from 120 (items total 1199)