Download JAR files tagged by script with all dependencies
indic-transliteration from group com.github.sanskrit-coders (version 1.6)
A collection of scala and java classes for some basic character level processing for the Sanskrit and other Indic (kannada, telugu, etc..) languages, contributed by the open source sanskrit-coders projects and friends.
Some notable facilities:
* Transliterate text from one script or encoding scheme to another.
* Some grammar simulation.
Examples: see https://github.com/sanskrit-coders/indic-transliteration
Contributions and suggestions are invited at https://github.com/sanskrit-coders/indic-transliteration . (Sister projects there may also be of interest.)
Group: com.github.sanskrit-coders Artifact: indic-transliteration
Show all versions Show documentation Show source
Show all versions Show documentation Show source
21 downloads
Artifact indic-transliteration
Group com.github.sanskrit-coders
Version 1.6
Last update 17. November 2017
Organization not specified
URL https://github.com/sanskrit-coders/indic-transliteration
License Apache License 2.0
Dependencies amount 3
Dependencies scala-library, logback-classic, logback-core,
There are maybe transitive dependencies!
Group com.github.sanskrit-coders
Version 1.6
Last update 17. November 2017
Organization not specified
URL https://github.com/sanskrit-coders/indic-transliteration
License Apache License 2.0
Dependencies amount 3
Dependencies scala-library, logback-classic, logback-core,
There are maybe transitive dependencies!
sanskritnlp from group com.github.sanskrit-coders (version 1.2)
A collection of scala and java classes for some basic natural language processing (NLP) for the Sanskrit language, contributed by the open source SanskritNLP project and friends.
Some notable facilities:
* Transliterate text from one script or encoding scheme to another.
* Deal with babylon dictionaries.
* Use bots to write to wiki projects (wiktionary, wikisource etc..).
* Basic metre identification.
* Some grammar simulation.
Contributions and suggestions are invited at https://github.com/sanskrit-coders/sanskritnlpjava . (Sister projects there may also be of interest.)
Group: com.github.sanskrit-coders Artifact: sanskritnlp
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact sanskritnlp
Group com.github.sanskrit-coders
Version 1.2
Last update 15. May 2017
Organization not specified
URL https://github.com/sanskrit-coders/sanskritnlpjava
License Apache License 2.0
Dependencies amount 9
Dependencies scala-library, scala-xml, indic-transliteration, json4s_2.11, json4s-native_2.11, logback-classic, logback-core, jwbf, jstl,
There are maybe transitive dependencies!
Group com.github.sanskrit-coders
Version 1.2
Last update 15. May 2017
Organization not specified
URL https://github.com/sanskrit-coders/sanskritnlpjava
License Apache License 2.0
Dependencies amount 9
Dependencies scala-library, scala-xml, indic-transliteration, json4s_2.11, json4s-native_2.11, logback-classic, logback-core, jwbf, jstl,
There are maybe transitive dependencies!
janbanery-core from group pl.project13.janbanery (version 1.2)
Kanbanery (https://kanbanery.com) is a simple but powerful Agile project management system,
to be precise it focuses around the idea of Kanban, a somewhat near idea to SCRUM but with less strict rules.
The heart of each Kanban flow is the Kanban board, IceBox and Archive - there are all easy accessible via this
API.
Janbanery wraps around the RESTful API delivered by Kanbanery while adding some more features like mass
operations
or filtering of results. In the end, it's very easy and pleasant to implement your own Kanbanery client be it on
the desktop, mobile (android) or as for example Gradle / SBT script to take full advantage of kanbanery's
features.
Artifact janbanery-core
Group pl.project13.janbanery
Version 1.2
Last update 09. May 2011
Organization not specified
URL http://www.blog.project13.pl
License Apache License 2.0
Dependencies amount 7
Dependencies async-http-client, gson, guava, joda-time, slf4j-api, logback-classic, logback-core,
There are maybe transitive dependencies!
Group pl.project13.janbanery
Version 1.2
Last update 09. May 2011
Organization not specified
URL http://www.blog.project13.pl
License Apache License 2.0
Dependencies amount 7
Dependencies async-http-client, gson, guava, joda-time, slf4j-api, logback-classic, logback-core,
There are maybe transitive dependencies!
janbanery from group pl.project13.janbanery (version 1.2)
Kanbanery (https://kanbanery.com) is a simple but powerful Agile project management system,
to be precise it focuses around the idea of Kanban, a somewhat near idea to SCRUM but with less strict rules.
The heart of each Kanban flow is the Kanban board, IceBox and Archive - there are all easy accessible via this
API.
Janbanery wraps around the RESTful API delivered by Kanbanery while adding some more features like mass
operations
or filtering of results. In the end, it's very easy and pleasant to implement your own Kanbanery client be it on
the desktop, mobile (android) or as for example Gradle / SBT script to take full advantage of kanbanery's
features.
Group: pl.project13.janbanery Artifact: janbanery
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact janbanery
Group pl.project13.janbanery
Version 1.2
Last update 09. May 2011
Organization not specified
URL http://www.blog.project13.pl
License Apache License 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group pl.project13.janbanery
Version 1.2
Last update 09. May 2011
Organization not specified
URL http://www.blog.project13.pl
License Apache License 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
jardiff from group jardiff (version 0.2)
A tool to help visualise API differences between two different versions of
a project. Jardiff takes two jar files and outputs all the public API changes
as xml, html or plain text. Currently this is command line driven, though
we are working on an ant plugin. It requires java 1.4 to run.
<h2>Background</h2>
At OSjava, we were using a shell script to work out API differences between
our release versions. This unfortunately doesn't scale very well to larger
projects, the main reason for jardiff was to do the same in a much shorter
time (From memory it was taking minutes to get the API diff from two fairly
small jars). In it's current state, jardiff can generate the api differences
between rt.jar for java 1.4 and java 1.5 in under 20 seconds, so it should
scale to even the largest of projects.
Artifact jardiff
Group jardiff
Version 0.2
Last update 21. February 2006
Organization OSJava
URL http://www.osjava.org/jardiff/
License not specified
Dependencies amount 5
Dependencies asm, asm-commons, commons-cli, ant, ant-trax,
There are maybe transitive dependencies!
Group jardiff
Version 0.2
Last update 21. February 2006
Organization OSJava
URL http://www.osjava.org/jardiff/
License not specified
Dependencies amount 5
Dependencies asm, asm-commons, commons-cli, ant, ant-trax,
There are maybe transitive dependencies!
idaithalam from group io.virtualan (version 1.7.0)
Idaithalam is a low code Test automation Framework, developed using Java and Cucumber. It leverages Behavior Driven Development (BDD). Tester can create test cases/scripts in simple Excel with API Spec. Excel is a simplified way to create Json based test scripts in Idaithalam. Test cases can be created quickly and tested in minutes.
As a tester, you need to create Excel and pass it to Idaithalam Framework.
First, generate the Json based test scripts(Virtualan Collection) from Excel. During test execution, this test script collection can be directly utilized.
Then it generates Feature files from the Virtualan Collection and its executed.
Lastly, It generates test report in BDD/Cucumber style.
This provide complete testing support for REST APIs, GraphQL, RDBMS DB and Kafka Event messages
#idaithalam #apitesting #testautomation #restapitesting #insprintautomation #rdbmstesting #graphqltesting #kafkamessagetesting #eventvalidation #messagevalidation #cucumber #bdd
Virtualan Collection is a JSON based TestScripts generated from Excel
API testing can be automated using Excel, POSTMAN collection and VIRTUALAN
- Utilized for API testing.
- Utilized Contract testing.
- Utilized Production Checkout.
- Agile Testing - Progressive Regression can be done for each sprint. Reduce lot of manual effects.
0 downloads
Artifact idaithalam
Group io.virtualan
Version 1.7.0
Last update 23. May 2022
Organization not specified
URL https://www.virtualan.io
License Apache License 2.0
Dependencies amount 12
Dependencies cucumblan-api, cucumblan-db, cucumblan-message, jackson-databind, commons-lang3, commons-io, cucumber-reporting, compiler, gherkin-formatter, slf4j-simple, log4j-core, swagger-inflector,
There are maybe transitive dependencies!
Group io.virtualan
Version 1.7.0
Last update 23. May 2022
Organization not specified
URL https://www.virtualan.io
License Apache License 2.0
Dependencies amount 12
Dependencies cucumblan-api, cucumblan-db, cucumblan-message, jackson-databind, commons-lang3, commons-io, cucumber-reporting, compiler, gherkin-formatter, slf4j-simple, log4j-core, swagger-inflector,
There are maybe transitive dependencies!
intelligentgraph from group com.inova8 (version 0.9.4)
The IntelligentGraph SAIL offers an extended capability for embedded calculation support within any RDF graph. When enabled as an RDF4J SAIL, it offers calculation functionality as part of the RDF4J engine, on top of any RDF4J repository, using a variety of script engines including JavaScript, Jython, and Groovy. It preserves the SPARQL capability of RDF4J, but with additional capabilities for calculation debugging and tracing.
IntelligentGraph includes the PathQL query language. Just as a spreadsheet cell calculation needs to access other cells, an IntelligentGraph calculation needs to access other nodes within the graph. Although full access to the underlying graph is available to any of the scripts, PathQL provides a succinct, and efficient method to access directly or indirectly related nodes. PathQL can either return just the contents of the referenced nodes, or the contents and the path to the referenced nodes.
PathQL can also be used standalone to query the IntelligentGraph-enabled RDF database. This supplements, rather than replaces, SPARQL and GraphQL, as it provides graph-path querying rather than graph-pattern querying capabilities to any IntelligentGraph-enabled RDF database.
The principles of IntelligentGraph are described here: https://inova8.com/bg_inova8.com/intelligent-graph-knowledge-graph-embedded-analysis/
The full PathQL syntax is described here: https://inova8.com/bg_inova8.com/pathpatternql-intelligently-finding-knowledge-as-a-path-through-a-maze-of-facts/
Using Jupyter as an IDE to IntelligentGraph and RDF4J, shown here: https://inova8.com/bg_inova8.com/intelligentgraph-getting-started/
IntelligentGraph source is here in GitHub: https://github.com/peterjohnlawrence/com.inova8.intelligentgraph
IntelligentGraph Docker containers are available here: https://hub.docker.com/repository/docker/inova8/intelligentgraph
0 downloads
Artifact intelligentgraph
Group com.inova8
Version 0.9.4
Last update 26. April 2022
Organization inova8
URL https://www.inova8.com
License The Apache License, Version 2.0
Dependencies amount 6
Dependencies commons-cli, rdf4j-runtime, antlr4-runtime, seeq-sdk, jcl-over-slf4j, jericho-html,
There are maybe transitive dependencies!
Group com.inova8
Version 0.9.4
Last update 26. April 2022
Organization inova8
URL https://www.inova8.com
License The Apache License, Version 2.0
Dependencies amount 6
Dependencies commons-cli, rdf4j-runtime, antlr4-runtime, seeq-sdk, jcl-over-slf4j, jericho-html,
There are maybe transitive dependencies!
sourcetohtml from group com.sourcetohtml (version 0.8.1)
This project aims to build a command line tool that can create
HTML view with syntax highlighted source code.
It uses Jedit syntax highlighting engine and support all languages that are supported in JEdit.
Which are currently: ActionScript, Ada 95, ANTLR, Apache HTTPD, APDL, AppleScript, ASP, Aspect-J, Assembly, AWK, B formal method, Batch, BBj, BCEL, BibTeX, C, C++, C#, CHILL, CIL, COBOL, ColdFusion, CSS, CVS Commit, D, DOxygen, DSSSL, Eiffel, EmbPerl, Erlang, Factor, Fortran, Foxpro, FreeMarker, Fortran, Gettext, Groovy, Haskell, HTML, Icon, IDL, Inform, INI, Inno Setup, Informix 4GL, Interlis, Io, Java, JavaScript, JCL, JHTML, JMK, JSP, Latex, Lilypond, Lisp, LOTOS, Lua, Makefile, Maple, ML, Modula-3, MoinMoin, MQSC, NetRexx, NQC, NSIS2, Objective C, ObjectRexx, Occam, Omnimark, Parrot, Pascal, Patch, Perl, PHP, Pike, PL-SQL, PL/I, Pop11, PostScript, Povray, PowerDynamo, Progress 4GL, Prolog, Properties, PSP, PV-WAVE, Pyrex, Python, REBOL, Redcode, Relax-NG, RelationalView, Rest, Rib, RPM spec, RTF, Ruby, Ruby-HTML, RView, S+, S#, SAS, Scheme, SDL/PL, SGML, Shell Script, SHTML, Smalltalk, SMI MIB, SQR, Squidconf, SVN Commit, Swig, TCL, TeX, Texinfo, TPL, Transact-SQL, UnrealScript, VBScript, Velocity, Verilog, VHDL, XML, XSL, ZPT
Artifact sourcetohtml
Group com.sourcetohtml
Version 0.8.1
Last update 31. March 2009
Organization not specified
URL http://www.sourcetohtml.com
License GNU GENERAL PUBLIC LICENSE, version 3
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group com.sourcetohtml
Version 0.8.1
Last update 31. March 2009
Organization not specified
URL http://www.sourcetohtml.com
License GNU GENERAL PUBLIC LICENSE, version 3
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 47 from 3 (items total 480)