Download JAR files tagged by active with all dependencies
netbeans-editor-pin from group com.raelity.jvi (version 2.1.2)
This plugin provides a registered action, toolbar button and menu actions
which can clear the REUSE flag <b>preventing a file from being
replaced</b>.
<br/><br/>
The toolbar button, which looks like a "push pin", provides a visual
indication that the currently active editor is REUSEable; the button is
only enabled when the active editor is REUSEable.
<br/><br/>
In some situations the IDE/platform opens a file with the REUSE flag
(see NetBeans API doc Line.ShowOpenType); files opened like this can be
automatically replaced in an editor window by other files.
<br/><br/>
IDE REUSE examples: single stepping into a file, clicking on a stacktrace
for goto source, jVi tag-stack operations.
Artifact netbeans-editor-pin
Group com.raelity.jvi
Version 2.1.2
Last update 22. January 2023
Organization Raelity Engineering
URL http://raelity.com
License Mozilla Public License Version 1.1
Dependencies amount 5
Dependencies org-openide-awt, org-openide-windows, org-openide-util, org-openide-util-ui, org-openide-util-lookup,
There are maybe transitive dependencies!
Group com.raelity.jvi
Version 2.1.2
Last update 22. January 2023
Organization Raelity Engineering
URL http://raelity.com
License Mozilla Public License Version 1.1
Dependencies amount 5
Dependencies org-openide-awt, org-openide-windows, org-openide-util, org-openide-util-ui, org-openide-util-lookup,
There are maybe transitive dependencies!
spring-maven-plugin from group org.kuali.maven.plugins (version 3.1.0)
This plugin provides integration between Spring and Maven.
Plugin goals support loading a Spring context XML file as part of the Maven build lifecycle.
The XML file can be on the local file system or be accessible via any URL Spring's resource loading mechanism can understand.
Spring's "classpath:context.xml" style notation is supported.
Annotated Java classes can also be used to load a Spring context.
Maven properties are injected into the Spring context (both XML and annotation style) as a java.util.Properties bean named "mavenProperties".
Maven properties are also registered as a top level PropertySource so that Spring's placeholder resolution framework automatically considers them.
See Project Reports -> Plugin Documentation for details on plugin goals.
By default, the profile "maven" is set as an active Spring profile along with any other active Maven profiles.
Group: org.kuali.maven.plugins Artifact: spring-maven-plugin
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact spring-maven-plugin
Group org.kuali.maven.plugins
Version 3.1.0
Last update 12. March 2014
Organization not specified
URL http://${kuali.site.hostname}/maven/plugins/${project.artifactId}/${project.version}
License not specified
Dependencies amount 2
Dependencies kuali-util, kuali-maven,
There are maybe transitive dependencies!
Group org.kuali.maven.plugins
Version 3.1.0
Last update 12. March 2014
Organization not specified
URL http://${kuali.site.hostname}/maven/plugins/${project.artifactId}/${project.version}
License not specified
Dependencies amount 2
Dependencies kuali-util, kuali-maven,
There are maybe transitive dependencies!
org.semanticweb.hermit from group com.hermit-reasoner (version 1.3.8.4)
HermiT is reasoner for ontologies written using the Web
Ontology Language (OWL). Given an OWL file, HermiT can determine whether or
not the ontology is consistent, identify subsumption relationships between
classes, and much more.
This is the maven build of HermiT and is designed for people who wish to use
HermiT from within the OWL API. It is now versioned in the main HermiT
version repository, although not officially supported by the HermiT
developers.
The version number of this package is a composite of the HermiT version and
an value representing releases of this packaged version. So, 1.3.7.1 is the
first release of the mavenized version of HermiT based on the 1.3.7 release
of HermiT.
This package includes the Jautomata library
(http://jautomata.sourceforge.net/), and builds with it directly. This
library appears to be no longer under active development, and so a "fork"
seems appropriate. No development is intended or anticipated on this code
base.
Group: com.hermit-reasoner Artifact: org.semanticweb.hermit
Show all versions Show documentation Show source
Show all versions Show documentation Show source
10 downloads
Artifact org.semanticweb.hermit
Group com.hermit-reasoner
Version 1.3.8.4
Last update 24. January 2014
Organization not specified
URL http://hermit-reasoner.com/
License LGPL
Dependencies amount 7
Dependencies commons-logging, owlapi-distribution, axiom-api, axiom-c14n, axiom-impl, axiom-dom, automaton,
There are maybe transitive dependencies!
Group com.hermit-reasoner
Version 1.3.8.4
Last update 24. January 2014
Organization not specified
URL http://hermit-reasoner.com/
License LGPL
Dependencies amount 7
Dependencies commons-logging, owlapi-distribution, axiom-api, axiom-c14n, axiom-impl, axiom-dom, automaton,
There are maybe transitive dependencies!
excalibur-monitor from group org.apache.excalibur.components (version 2.2.1)
Avalon Excalibur's resource management code allows you to be notified when a resource has changed. There
are two methods of resource management: active and passive. Passive resource management acts as a holder
for resources, and after the resource has been modified through it's normal API, notification goes to all
listeners. Active resource management does the same, but it also polls the resources periodically to see
if the resource was modified through an external method. Active resource management is perfect for
monitoring files because they can be modified by external programs, and your program will be notified when
the change occurs instead of constantly polling it.
0 downloads
Artifact excalibur-monitor
Group org.apache.excalibur.components
Version 2.2.1
Last update 15. February 2007
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies avalon-framework-api, excalibur-sourceresolve,
There are maybe transitive dependencies!
Group org.apache.excalibur.components
Version 2.2.1
Last update 15. February 2007
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies avalon-framework-api, excalibur-sourceresolve,
There are maybe transitive dependencies!
org.semanticweb.hermit from group net.sourceforge.owlapi (version 1.4.5.519)
HermiT is reasoner for ontologies written using the Web Ontology Language (OWL). Given an OWL file, HermiT can determine whether or not the ontology is consistent, identify subsumption relationships between classes, and much more.
This is the maven build of HermiT and is designed for people who wish to use HermiT from within the OWL API. It is now versioned in the main HermiT version repository, although not officially supported by the HermiT developers.
The version number of this package is a composite of the HermiT version and a value representing the OWLAPI release it is compatible with. Note that the group id for the upstream HermiT is com.hermit-reasoner, while this fork is released under net.sourceforge.owlapi.
This fork exists to allow HermiT users to use newer OWLAPI versions than the ones supported by the original HermiT codebase.
This package includes the Jautomata library (http://jautomata.sourceforge.net/), and builds with it directly. This library appears to be no longer under active development, and so a "fork" seems appropriate. No development is intended or anticipated on this code base.
Group: net.sourceforge.owlapi Artifact: org.semanticweb.hermit
Show all versions Show documentation Show source
Show all versions Show documentation Show source
61 downloads
Artifact org.semanticweb.hermit
Group net.sourceforge.owlapi
Version 1.4.5.519
Last update 18. February 2020
Organization not specified
URL http://hermit-reasoner.com/
License LGPL
Dependencies amount 9
Dependencies commons-logging, owlapi-distribution, axiom-api, axiom-c14n, axiom-impl, axiom-dom, automaton, java-getopt, trove4j,
There are maybe transitive dependencies!
Group net.sourceforge.owlapi
Version 1.4.5.519
Last update 18. February 2020
Organization not specified
URL http://hermit-reasoner.com/
License LGPL
Dependencies amount 9
Dependencies commons-logging, owlapi-distribution, axiom-api, axiom-c14n, axiom-impl, axiom-dom, automaton, java-getopt, trove4j,
There are maybe transitive dependencies!
balea-core from group io.magidc (version 1.0.1)
Balea creates a proxy of javax.sql.DataSource, providing dynamic routing to multiple container based databases following a On Demand Data Source Access architecture.
Docker is used as manager to create, start or stop database containers on demand and link correspondent data volumes. Thanks to this approach is possible to distribute data across multiple databases keeping active only the necessary ones in each moment maximizing the use of system resources.
The distribution and management of data is hidden under the hood, any process that uses this data source interface (i.e. Hibernate) will perceive it as a single source of data.
It makes possible for standard SQL database like Postgresql or MySQL to be maintained, backed up or versioned with simple file system operations as the data volumes are attached dynamically to the managed Docker containers.
Docker integration allows also to manage database containers in remote hosts.
Artifact balea-core
Group io.magidc
Version 1.0.1
Last update 23. July 2019
Organization not specified
URL https://github.com/magidc/balea-core
License Apache License, Version 2.0
Dependencies amount 1
Dependencies docker-java,
There are maybe transitive dependencies!
Group io.magidc
Version 1.0.1
Last update 23. July 2019
Organization not specified
URL https://github.com/magidc/balea-core
License Apache License, Version 2.0
Dependencies amount 1
Dependencies docker-java,
There are maybe transitive dependencies!
HermiT from group com.github.ansell.hermit (version 1.3.8.2-ansell)
HermiT is reasoner for ontologies written using the Web
Ontology Language (OWL). Given an OWL file, HermiT can determine whether or
not the ontology is consistent, identify subsumption relationships between
classes, and much more.
This is the maven build of HermiT and is designed for people who wish to use
HermiT from within the OWL API. It is not officially supported by the HermiT
development team, but was built initially for use with the Clojure-OWL
library. It is built using the HermiT source tree without modification.
There have been some additions to the test source tree to account for
differences between the maven and ant environment; these are small and
(hopefully) maintainable.
The version number of this package is a composite of the HermiT version and
an value representing releases of this packaged version. So, 1.3.7.1 is the
first release of the mavenized version of HermiT based on the 1.3.7 release
of HermiT.
This package includes the Jautomata library
(http://jautomata.sourceforge.net/), and builds with it directly. This
library appears to be no longer under active development, and so a "fork"
seems appropriate. No development is intended or anticipated on this code
base.
Artifact HermiT
Group com.github.ansell.hermit
Version 1.3.8.2-ansell
Last update 03. September 2013
Organization not specified
URL http://hermit-reasoner.com/
License LGPL
Dependencies amount 12
Dependencies owlapi-api, owlapi-impl, owlapi-parsers, owlapi-rio, sesame-rio-turtle, sesame-rio-ntriples, sesame-rio-rdfxml, axiom-api, axiom-c14n, axiom-impl, axiom-dom, automaton,
There are maybe transitive dependencies!
Group com.github.ansell.hermit
Version 1.3.8.2-ansell
Last update 03. September 2013
Organization not specified
URL http://hermit-reasoner.com/
License LGPL
Dependencies amount 12
Dependencies owlapi-api, owlapi-impl, owlapi-parsers, owlapi-rio, sesame-rio-turtle, sesame-rio-ntriples, sesame-rio-rdfxml, axiom-api, axiom-c14n, axiom-impl, axiom-dom, automaton,
There are maybe transitive dependencies!
HockeySDK from group net.hockeyapp.android (version 5.2.0)
HockeySDK-Android implements support for using HockeyApp in your Android application. The following features are currently supported:
Collect crash reports:If your app crashes, a crash log is written to the device's storage. If the user starts the app again, they will be asked asked to submit the crash report to HockeyApp. This works for both beta and live apps, i.e. those submitted to Google Play or other app stores. Crash logs contain viable information for you to help resolve the issue. Furthermore, you as a developer can add additional information to the report as well.
Update Alpha/Beta apps: The app will check with HockeyApp if a new version for your alpha/beta build is available. If yes, it will show a dialog to users and let them see the release notes, the version history and start the installation process right away. You can even force the installation of certain updates.
User Metrics: Understand user behavior to improve your app. Track usage through daily and monthly active users. Monitor crash impacted users. Measure customer engagement through session count. Add custom tracking calls to learn which features your users are actually using. This feature requires a minimum API level of 14 (Android 4.x Ice Cream Sandwich).
Feedback: Besides crash reports, collecting feedback from your users from within your app is a great option to help with improving your app. You act on and answer feedback directly from the HockeyApp backend.
Authenticate: Identify and authenticate users against your registered testers with the HockeyApp backend.
Group: net.hockeyapp.android Artifact: HockeySDK
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 HockeySDK
Group net.hockeyapp.android
Version 5.2.0
Last update 21. May 2019
Organization not specified
URL https://github.com/bitstadium/hockeysdk-android
License MIT
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group net.hockeyapp.android
Version 5.2.0
Last update 21. May 2019
Organization not specified
URL https://github.com/bitstadium/hockeysdk-android
License MIT
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
pact-jvm-server_2.12 from group au.com.dius (version 3.6.15)
Pact server
===========
The pact server is a stand-alone interactions recorder and verifier, aimed at clients that are non-JVM or non-Ruby based.
The pact client for that platform will need to be implemented, but it only be responsible for generating the `JSON`
interactions, running the tests and communicating with the server.
The server implements a `JSON` `REST` Admin API with the following endpoints.
/ -> For diagnostics, currently returns a list of ports of the running mock servers.
/create -> For initialising a test server and submitting the JSON interactions. It returns a port
/complete -> For finalising and verifying the interactions with the server. It writes the `JSON` pact file to disk.
## Running the server
### Versions 2.2.6+
Pact server takes the following parameters:
```
Usage: pact-jvm-server [options] [port]
port
port to run on (defaults to 29999)
--help
prints this usage text
-h <value> | --host <value>
host to bind to (defaults to localhost)
-l <value> | --mock-port-lower <value>
lower bound to allocate mock ports (defaults to 20000)
-u <value> | --mock-port-upper <value>
upper bound to allocate mock ports (defaults to 40000)
-d | --daemon
run as a daemon process
-v <value> | --pact-version <value>
pact version to generate for (2 or 3)
-k <value> | --keystore-path <value>
Path to keystore
-p <value> | --keystore-password <value>
Keystore password
-s <value> | --ssl-port <value>
Ssl port the mock server should run on. lower and upper bounds are ignored
--debug
run with debug logging
```
### Using trust store 3.4.0+
Trust store can be used. However, it is limited to a single port for the time being.
### Prior to version 2.2.6
Pact server takes one optional parameter, the port number to listen on. If not provided, it will listen on 29999.
It requires an active console to run.
### Using a distribution archive
You can download a [distribution from maven central](http://search.maven.org/remotecontent?filepath=au/com/dius/pact-jvm-server_2.11/2.2.4/).
There is both a ZIP and TAR archive. Unpack it to a directory of choice and then run the script in the bin directory.
### Building a distribution bundle
You can build an application bundle with gradle by running (for 2.11 version):
$ ./gradlew :pact-jvm-server_2.11:installdist
This will create an app bundle in `build/2.11/install/pact-jvm-server_2.11`. You can then execute it with:
$ java -jar pact-jvm-server/build/2.10/install/pact-jvm-server_2.11/lib/pact-jvm-server_2.11-3.2.11.jar
or with the generated bundle script file:
$ pact-jvm-server/build/2.11/install/pact-jvm-server_2.11/bin/pact-jvm-server_2.11
By default will run on port `29999` but a port number can be optionally supplied.
### Running it with docker
You can use a docker image to execute the mock server as a docker container.
$ docker run -d -p 8080:8080 -p 20000-20010:20000-20010 uglyog/pact-jvm-server
This will run the main server on port 8080, and each created mock server on ports 20000-20010. You can map the ports to
any you require.
## Life cycle
The following actions are expected to occur
* The client calls `/create` to initialise a server with the expected `JSON` interactions and state
* The admin server will start a mock server on a random port and return the port number in the response
* The client will execute its interaction tests against the mock server with the supplied port
* Once finished, the client will call `/complete' on the Admin API, posting the port number
* The pact server will verify the interactions and write the `JSON` `pact` file to disk under `/target`
* The mock server running on the supplied port will be shutdown.
## Endpoints
### /create
The client will need `POST` to `/create` the generated `JSON` interactions, also providing a state as a query parameter
and a path.
For example:
POST http://localhost:29999/create?state=NoUsers&path=/sub/ref/path '{ "provider": { "name": "Animal_Service"}, ... }'
This will create a new running mock service provider on a randomly generated port. The port will be returned in the
`201` response:
{ "port" : 34423 }
But you can also reference the path from `/sub/ref/path` using the server port. The service will not strip
the prefix path, but instead will use it as a differentiator. If your services do not have differences
in the prefix of their path, then you will have to use the port method.
### /complete
Once the client has finished running its tests against the mock server on the supplied port (in this example port
`34423`) the client will need to `POST` to `/complete` the port number of the mock server that was used.
For example:
POST http://localhost:29999/complete '{ "port" : 34423 }'
This will cause the Pact server to verify the interactions, shutdown the mock server running on that port and writing
the pact `JSON` file to disk under the `target` directory.
### /
The `/` endpoint is for diagnostics and to check that the pact server is running. It will return all the currently
running mock servers port numbers.
For example:
GET http://localhost:29999/
'{ "ports": [23443,43232] }'
2 downloads
Artifact pact-jvm-server_2.12
Group au.com.dius
Version 3.6.15
Last update 29. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 4
Dependencies pact-jvm-consumer_2.12, logback-core, logback-classic, scopt_2.12,
There are maybe transitive dependencies!
Group au.com.dius
Version 3.6.15
Last update 29. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 4
Dependencies pact-jvm-consumer_2.12, logback-core, logback-classic, scopt_2.12,
There are maybe transitive dependencies!
pact-jvm-server from group au.com.dius (version 4.0.10)
Pact server
===========
The pact server is a stand-alone interactions recorder and verifier, aimed at clients that are non-JVM or non-Ruby based.
The pact client for that platform will need to be implemented, but it only be responsible for generating the `JSON`
interactions, running the tests and communicating with the server.
The server implements a `JSON` `REST` Admin API with the following endpoints.
/ -> For diagnostics, currently returns a list of ports of the running mock servers.
/create -> For initialising a test server and submitting the JSON interactions. It returns a port
/complete -> For finalising and verifying the interactions with the server. It writes the `JSON` pact file to disk.
## Running the server
### Versions 2.2.6+
Pact server takes the following parameters:
```
Usage: pact-jvm-server [options] [port]
port
port to run on (defaults to 29999)
--help
prints this usage text
-h <value> | --host <value>
host to bind to (defaults to localhost)
-l <value> | --mock-port-lower <value>
lower bound to allocate mock ports (defaults to 20000)
-u <value> | --mock-port-upper <value>
upper bound to allocate mock ports (defaults to 40000)
-d | --daemon
run as a daemon process
-v <value> | --pact-version <value>
pact version to generate for (2 or 3)
-k <value> | --keystore-path <value>
Path to keystore
-p <value> | --keystore-password <value>
Keystore password
-s <value> | --ssl-port <value>
Ssl port the mock server should run on. lower and upper bounds are ignored
--debug
run with debug logging
```
### Using trust store 3.4.0+
Trust store can be used. However, it is limited to a single port for the time being.
### Prior to version 2.2.6
Pact server takes one optional parameter, the port number to listen on. If not provided, it will listen on 29999.
It requires an active console to run.
### Using a distribution archive
You can download a [distribution from maven central](http://search.maven.org/remotecontent?filepath=au/com/dius/pact-jvm-server_2.11/2.2.4/).
There is both a ZIP and TAR archive. Unpack it to a directory of choice and then run the script in the bin directory.
### Building a distribution bundle
You can build an application bundle with gradle by running (for 2.11 version):
$ ./gradlew :pact-jvm-server_2.11:installdist
This will create an app bundle in `build/2.11/install/pact-jvm-server_2.11`. You can then execute it with:
$ java -jar pact-jvm-server/build/2.10/install/pact-jvm-server_2.11/lib/pact-jvm-server_2.11-3.2.11.jar
or with the generated bundle script file:
$ pact-jvm-server/build/2.11/install/pact-jvm-server_2.11/bin/pact-jvm-server_2.11
By default will run on port `29999` but a port number can be optionally supplied.
### Running it with docker
You can use a docker image to execute the mock server as a docker container.
$ docker run -d -p 8080:8080 -p 20000-20010:20000-20010 uglyog/pact-jvm-server
This will run the main server on port 8080, and each created mock server on ports 20000-20010. You can map the ports to
any you require.
## Life cycle
The following actions are expected to occur
* The client calls `/create` to initialise a server with the expected `JSON` interactions and state
* The admin server will start a mock server on a random port and return the port number in the response
* The client will execute its interaction tests against the mock server with the supplied port
* Once finished, the client will call `/complete' on the Admin API, posting the port number
* The pact server will verify the interactions and write the `JSON` `pact` file to disk under `/target`
* The mock server running on the supplied port will be shutdown.
## Endpoints
### /create
The client will need `POST` to `/create` the generated `JSON` interactions, also providing a state as a query parameter
and a path.
For example:
POST http://localhost:29999/create?state=NoUsers&path=/sub/ref/path '{ "provider": { "name": "Animal_Service"}, ... }'
This will create a new running mock service provider on a randomly generated port. The port will be returned in the
`201` response:
{ "port" : 34423 }
But you can also reference the path from `/sub/ref/path` using the server port. The service will not strip
the prefix path, but instead will use it as a differentiator. If your services do not have differences
in the prefix of their path, then you will have to use the port method.
### /complete
Once the client has finished running its tests against the mock server on the supplied port (in this example port
`34423`) the client will need to `POST` to `/complete` the port number of the mock server that was used.
For example:
POST http://localhost:29999/complete '{ "port" : 34423 }'
This will cause the Pact server to verify the interactions, shutdown the mock server running on that port and writing
the pact `JSON` file to disk under the `target` directory.
### /
The `/` endpoint is for diagnostics and to check that the pact server is running. It will return all the currently
running mock servers port numbers.
For example:
GET http://localhost:29999/
'{ "ports": [23443,43232] }'
0 downloads
Artifact pact-jvm-server
Group au.com.dius
Version 4.0.10
Last update 18. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group au.com.dius
Version 4.0.10
Last update 18. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Page 20 from 21 (items total 202)