Download JAR files tagged by deployed with all dependencies
oxalis-integration-test from group no.difi.oxalis (version 4.0.0-RC2)
Oxalis integration test.
Compiles and packages everything, after which the web container
is started in the pre-integration-test phase, the .war file is deployed
and the tests are executed in the integration-test phase.
After the tests have been executed, the web container is stopped in
the post-integration-test phase.
The reason for using failsafe is the fact that Surefire would fail the build
in the integration-test phase, without taking down the server in the
post-integration-test phase.
This implementation uses Tomcat, but you may change this to your liking.
See http://cargo.codehaus.org/Maven2+plugin for more information.
Artifact oxalis-integration-test
Group no.difi.oxalis
Version 4.0.0-RC2
Last update 01. March 2017
Organization Norwegian Agency for Public Management and eGovernment (Difi)
URL https://github.com/difi/oxalis
License not specified
Dependencies amount 7
Dependencies oxalis-as2, oxalis-inbound, oxalis-outbound, oxalis-statistics, httpclient, jcl-over-slf4j, logback-classic,
There are maybe transitive dependencies!
Group no.difi.oxalis
Version 4.0.0-RC2
Last update 01. March 2017
Organization Norwegian Agency for Public Management and eGovernment (Difi)
URL https://github.com/difi/oxalis
License not specified
Dependencies amount 7
Dependencies oxalis-as2, oxalis-inbound, oxalis-outbound, oxalis-statistics, httpclient, jcl-over-slf4j, logback-classic,
There are maybe transitive dependencies!
jeuron-project from group org.jeuron (version 0.4.0)
The Jeuron Application Platform is a lightweight framework to assemble software components intended to support multiple project and deployment scenarios while also providing an environment for testing and debugging. The platform is comprised of a set of packages which provide transport, messaging, configuration, and execution services designed to create a configurable, scalable, and distributed application environment. The low resource model permits the platform to be instantiated during each build cycle and to be deployed at all levels of the application hierarchy such as application servers, web servers, and mobile or wired workstations.
Group: org.jeuron Artifact: jeuron-project
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact jeuron-project
Group org.jeuron
Version 0.4.0
Last update 25. April 2014
Organization not specified
URL Not specified
License GNU Lesser General Public License
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.jeuron
Version 0.4.0
Last update 25. April 2014
Organization not specified
URL Not specified
License GNU Lesser General Public License
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
jeuron from group org.jeuron (version 0.4.0)
Artifact jeuron
Group org.jeuron
Version 0.4.0
Last update 24. April 2014
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.jeuron
Version 0.4.0
Last update 24. April 2014
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
deployment-client from group de.schlichtherle.glassfish (version 4.0)
This is an endorsed version of the original Deployment Client for
Oracle GlassFish Open Source Edition.
The purpose of the endorsement is to provide a shaded JAR which has the
OSGI meta data removed because it causes the original Deployment Client
to fail when used within a module running within a GlassFish container
due to some class loader configuration conflicts between the container
and the deployed module.
This issue has been reported to the GlassFish project at
https://java.net/jira/browse/GLASSFISH-20856 .
It is hoped that it can get fixed so that this workaround project can
get deprecated soon.
0 downloads
Artifact deployment-client
Group de.schlichtherle.glassfish
Version 4.0
Last update 21. October 2013
Organization not specified
URL https://bitbucket.org/christian_schlichtherle/glassfish-deployment-client
License CDDL + GPLv2 with classpath exception
Dependencies amount 50
Dependencies common-util, core, hk2-locator, javax.inject, cglib, hk2-utils, glassfish-api, scattered-archive-api, nucleus-grizzly-all, grizzly-framework, grizzly-rcm, grizzly-portunif, grizzly-http, grizzly-http-server, grizzly-config, admin-cli, hk2, hk2-api, osgi-resource-locator, config-types, hk2-config, tiger-types, bean-validator, hk2-runlevel, class-model, mimepull, jettison, stax-api, launcher, logging, admin-util, config-api, security-services, security, ssl-impl, ldapbp-repackaged, jackson-core-asl, simple-glassfish-api, javax.enterprise.deploy-api, deployment-common, internal-api, management-api, gmbal, pfl-basic, pfl-tf, pfl-asm, pfl-dynamic, pfl-basic-tools, pfl-tf-tools, asm-all-repackaged,
There are maybe transitive dependencies!
Group de.schlichtherle.glassfish
Version 4.0
Last update 21. October 2013
Organization not specified
URL https://bitbucket.org/christian_schlichtherle/glassfish-deployment-client
License CDDL + GPLv2 with classpath exception
Dependencies amount 50
Dependencies common-util, core, hk2-locator, javax.inject, cglib, hk2-utils, glassfish-api, scattered-archive-api, nucleus-grizzly-all, grizzly-framework, grizzly-rcm, grizzly-portunif, grizzly-http, grizzly-http-server, grizzly-config, admin-cli, hk2, hk2-api, osgi-resource-locator, config-types, hk2-config, tiger-types, bean-validator, hk2-runlevel, class-model, mimepull, jettison, stax-api, launcher, logging, admin-util, config-api, security-services, security, ssl-impl, ldapbp-repackaged, jackson-core-asl, simple-glassfish-api, javax.enterprise.deploy-api, deployment-common, internal-api, management-api, gmbal, pfl-basic, pfl-tf, pfl-asm, pfl-dynamic, pfl-basic-tools, pfl-tf-tools, asm-all-repackaged,
There are maybe transitive dependencies!
laf from group net.sf.squirrel-sql.plugins (version 3.5.0)
This plugin gives SQuirreLSQL client the ability to configure alternate LaFs provided by the plugin
as well as others that the user can provide. All dependencies listed with a groupId of
net.sf.squirrel-sql and artifactId starting with squirrelsql-lf- are externally available
open-source
look and feels whose project maintainers have decided to not use maven, or those which were built and
maintained only before the introduction of maven. Maven's central repository policy requires any
pom that is deployed there to reference only artifacts which are also hosted in central. And a
project may only use the groupId that is related to that project. So, this only leaves us with one
option which is to host these external third-party artifacts using our groupId. The hope is that
someday these projects will start using maven and the need for this will no longer be.
2 downloads
Artifact laf
Group net.sf.squirrel-sql.plugins
Version 3.5.0
Last update 06. May 2013
Organization not specified
URL http://www.squirrelsql.org/
License GNU Lesser
Dependencies amount 14
Dependencies fw, squirrel-sql, ilf-gpl, kunstoff-laf, looks, napkinlaf, nimrod-laf, skinlf, skinlf-theme-packs, substance, swingsetthemes, tinylaf, toniclf, JTattoo,
There are maybe transitive dependencies!
Group net.sf.squirrel-sql.plugins
Version 3.5.0
Last update 06. May 2013
Organization not specified
URL http://www.squirrelsql.org/
License GNU Lesser
Dependencies amount 14
Dependencies fw, squirrel-sql, ilf-gpl, kunstoff-laf, looks, napkinlaf, nimrod-laf, skinlf, skinlf-theme-packs, substance, swingsetthemes, tinylaf, toniclf, JTattoo,
There are maybe transitive dependencies!
ferris-dyndns-jmce from group org.ferris (version 0.0.5)
Dyndns JMCE is an application deployed to a JMCE server whose purpose is to
login to a Dyndns account because if that's not done on a regular basis
the account gets deleted.
MAVEN: mvn [-DskipTests] clean site package
NOTES: After unzipping the binary on the JMCE server, make sure
to copy the ferris-dyndns-jmce-private-0.0.1.jar to /bin
so the app has the username/passwords it needs.
0.0.2: Changed project name from ferris-jmce-dyndns to ferris-dyndns-jmce
Removed java.util.logging.Logger for Log4j
Split into muli-module project
0.0.3: Update screen scrape based on changes to the dyndns website.
0.0.4: Update screen scrape (again) based on changes to the dyndns website.
Changed parent to "ferris-standard-project"
0.0.5: - Update screen scrape (again) based on changes to the dyndns website.
- Update pom.xml configuration to be in line with new parent pom.
- Update project site
Artifact ferris-dyndns-jmce
Group org.ferris
Version 0.0.5
Last update 15. September 2011
Organization not specified
URL http://ferris.sourceforge.net/dyndns-jmce
License not specified
Dependencies amount 10
Dependencies activation, mail, ferris-util, jta, commons-collections, quartz, log4j, commons-io, ferris-dyndns-jmce-private, ferris-net,
There are maybe transitive dependencies!
Group org.ferris
Version 0.0.5
Last update 15. September 2011
Organization not specified
URL http://ferris.sourceforge.net/dyndns-jmce
License not specified
Dependencies amount 10
Dependencies activation, mail, ferris-util, jta, commons-collections, quartz, log4j, commons-io, ferris-dyndns-jmce-private, ferris-net,
There are maybe transitive dependencies!
prolobjectlink-jpi from group io.github.prolobjectlink (version 1.1)
Java Prolog Interface (JPI) is an Application Provider Interface (API) for interaction between Java and Prolog programming languages. Is a bidirectional interface that communicate Java applications with Prolog program or database and Prolog procedures with Java class and methods.
JPI is an abstraction layer over concrete prolog drivers over Prolog Engines. This API define all mechanism to interact with any Prolog Engine and maintain the application independent to a specific underlying engine. JPI have several connectors to open source prolog engines like SWI, YAP, XSB native engines and tuProlog, jTrolog, jLog Java based prolog engines.
JPI study all related Java-Prolog integration libraries and take the betters features from each solution with the propose to achieve a common integration interface. The last feature allows switch the under laying Prolog Engine driver and the application code still be the same.
JPI run over any Java Virtual Machine that support Java SE 5 or above. The project was tested over HotSpot, Open J9 and JRockit Virtual Machines over Operating Systems like Windows (7,8,10), Linux (Debian, Ubuntu) and Mac OS X. Can be deployed on Servlets Containers like Jetty, Tomcat or Glassfish Application Server.
JPI can be include in any Java Project using the commonest Java Integration Development Enviroment (IDE) like Eclipse, Netbeans, IntelijIDEA and so on.
JPI is developed and maintained by Prolobjectlink Project an open source initiative for build logic based applications using Prolog like fundamental Logic Programming Language in the persistence layer and application programming.
Group: io.github.prolobjectlink Artifact: prolobjectlink-jpi
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact prolobjectlink-jpi
Group io.github.prolobjectlink
Version 1.1
Last update 02. June 2022
Organization Prolobjectlink Project
URL https://prolobjectlink.github.io/${project.name}
License MIT
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group io.github.prolobjectlink
Version 1.1
Last update 02. June 2022
Organization Prolobjectlink Project
URL https://prolobjectlink.github.io/${project.name}
License MIT
Dependencies amount 0
Dependencies No dependencies
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!
EasyConfig from group net.sf.ssg.tools (version 0.1)
EasyConfig provides simple way to overview and apply settings to file or folder based collections of files.
Synonyms to "setting" are property, attribute, value while throughout application "setting" is used.
The settings are groupped in "configuration" that is collection of settings from various sources.
Main design concepts are:
* minimalistic way to describe configuration
* pluggable support for data types (validation), setting sources, source handlers
Sample use case:
An application is deployed in multiple locations.
We need to quickly check key settings/parameters and optionally modify some of them.
These values are located in different places:
- in files directly in file structure
- in files inside archive files (optionally nested archives)
- values in DB tables
- values accessible via URLs
- other sources (just guessed: SSH/telnet connection+some command(s), UPnP devices, proprietary protocols, etc)
We gather info from any supported (extendable) source and can modify and apply changes if supported by source
(e.g. we can't update value that is count of rows in DB table, but we can read that value).
Artifact EasyConfig
Group net.sf.ssg.tools
Version 0.1
Last update 01. February 2013
Organization not specified
URL http://sourceforge.net/p/easyconfig
License The Apache Software License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group net.sf.ssg.tools
Version 0.1
Last update 01. February 2013
Organization not specified
URL http://sourceforge.net/p/easyconfig
License The Apache Software License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
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!
Page 36 from 36 (items total 360)