Download JAR files tagged by because with all 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!
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!
algorithms from group de.cit-ec.tcs.alignment (version 3.1.1)
This module defines the interface for AlignmentAlgorithms as well as some helper classes. An
AlignmentAlgorithm computes an Alignment of two given input sequences, given a Comparator that
works in these sequences.
More details on the AlignmentAlgorithm can be found in the respective interface. More information
on Comparators can be found in the comparators module.
The resulting 'Alignment' may be just a real-valued dissimilarity between the input sequence or
may incorporate additional information, such as a full Alignment, a PathList, a PathMap or a
CooptimalModel. If those results support the calculation of a Gradient, they implement the
DerivableAlignmentDistance interface.
In more detail, the Alignment class represents the result of a backtracing scheme, listing all
Operations that have been applied in one co-optimal Alignment.
A classic AlignmentAlgorithm does not result in a differentiable dissimilarity, because the
minimum function is not differentiable. Therefore, this package also contains utility functions
for a soft approximation of the minimum function, namely Softmin.
For faster (parallel) computation of many different alignments or gradients we also provide the
ParallelProcessingEngine, the SquareParallelProcessingEngine and the ParallelGradientEngine.
0 downloads
Artifact algorithms
Group de.cit-ec.tcs.alignment
Version 3.1.1
Last update 26. October 2018
Organization not specified
URL http://openresearch.cit-ec.de/projects/tcs
License The GNU Affero General Public License, Version 3
Dependencies amount 3
Dependencies comparators, parallel, lombok,
There are maybe transitive dependencies!
Group de.cit-ec.tcs.alignment
Version 3.1.1
Last update 26. October 2018
Organization not specified
URL http://openresearch.cit-ec.de/projects/tcs
License The GNU Affero General Public License, Version 3
Dependencies amount 3
Dependencies comparators, parallel, lombok,
There are maybe transitive dependencies!
data-distribution-api-vivo_1_08 from group edu.cornell.library.scholars (version 1.1.1)
---------------------------------------------------------------------------
Version for VIVO 1.8
This uses the source and test code from the Version for VIVO 1.10, edited to
make it compatible with VIVO 1.8. It also borrows some code from VIVO 1.10
itself, changes the package name to avoid conflicts, and adds it here.
* Vitro 1.8 uses Jena 2, not Jena 3, and Commons Lang 2, not 3, so modify
the "import" statements in the Data Distribution code accordingly.
* Vitro 1.8 does not have a "...webapp.utils.sparqlrunner" package, so
borrow the source from Vitro 1.10, move it to a different package (just
for compatibility with the 1.9 version), modify it to use Jena 2 and
Commons Lang 2, and modify the Data Distribution API code to use this
sparqlrunner package.
* Vitro 1.9 has an earlier version of "...webapp.utils.configuration"
package, so borrow the source from Vitro 1.10, move it to a different
package so it won't conflict with the 1.9 version, modify it to use
Jena 2 and Commons Lang 2, and modify the Data Distribution API code to
use this configuration package.
Make these modifications, compile, JAR it up, and deploy.
---------------------------------------------------------------------------
Because VIVO 1.8 is not available as a Maven package, we have extracted the
class files, JARed them up, and stored them in a file-based repository
within this project.
But that doesn't include any transitive dependencies, so any package that
this code requires must be explicitly listed as a dependency.
---------------------------------------------------------------------------
Group: edu.cornell.library.scholars Artifact: data-distribution-api-vivo_1_08
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact data-distribution-api-vivo_1_08
Group edu.cornell.library.scholars
Version 1.1.1
Last update 25. April 2018
Organization not specified
URL Not specified
License not specified
Dependencies amount 9
Dependencies vivo_classes, jena-core, jena-arq, commons-logging, commons-io, commons-lang, jackson-core, jackson-databind, jackson-annotations,
There are maybe transitive dependencies!
Group edu.cornell.library.scholars
Version 1.1.1
Last update 25. April 2018
Organization not specified
URL Not specified
License not specified
Dependencies amount 9
Dependencies vivo_classes, jena-core, jena-arq, commons-logging, commons-io, commons-lang, jackson-core, jackson-databind, jackson-annotations,
There are maybe transitive dependencies!
sirix-core from group com.github.johanneslichtenberger.sirix (version 0.1.0)
Sirix is a versioned, treebased storage system. It provides
an ID-less diff-algorithm to import differences between two versions. Furthermore
an ID-based diff-algorithm facilitates the comparison of versions stored within
Sirix. A GUI with several visualizations for comparing these versions visually is
available to aid an analyst. Versions are stored using well known versioning strategies (full, incremental, differential).
The architecture is especially well suited for flash-disks because of a COW-principle. In the future we aim to provide throughout security as
well as a replaced page-structure to speedup our architecture. A brackit(.org) binding will
enable XQuery and the XQuery Update Facility. Temporal XPath axis and possibly diff-functions will help analysts to gain quick knowledge from the stored data.
0 downloads
Artifact sirix-core
Group com.github.johanneslichtenberger.sirix
Version 0.1.0
Last update 27. September 2012
Organization not specified
URL Not specified
License not specified
Dependencies amount 1
Dependencies snappy-java,
There are maybe transitive dependencies!
Group com.github.johanneslichtenberger.sirix
Version 0.1.0
Last update 27. September 2012
Organization not specified
URL Not specified
License not specified
Dependencies amount 1
Dependencies snappy-java,
There are maybe transitive dependencies!
sirix-parent from group com.github.johanneslichtenberger.sirix (version 0.1.1)
Sirix is a versioned, treebased storage system. It provides
an ID-less diff-algorithm to import differences between two versions (currently XML-documents). Furthermore
an ID-based diff-algorithm facilitates the comparison of versions stored within
Sirix. A GUI with several visualizations for comparing these versions visually is
available to aid an analyst. Versions are stored using well known versioning strategies (full, incremental, differential).
The architecture is especially well suited for flash-disks because of a COW-principle. In the future we aim to provide throughout security as
well as a replaced page-structure to speedup our architecture. A brackit(.org) binding will
enable XQuery and the XQuery Update Facility. Temporal XPath axis and possibly diff-functions will help analysts to gain quick knowledge from the stored data.
Group: com.github.johanneslichtenberger.sirix Artifact: sirix-parent
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact sirix-parent
Group com.github.johanneslichtenberger.sirix
Version 0.1.1
Last update 27. September 2012
Organization not specified
URL https://github.com/JohannesLichtenberger/sirix
License New BSD
Dependencies amount 9
Dependencies je, aspectjrt, slf4j-api, perfidix, xmlunit, logback-classic, guice, gson, guava,
There are maybe transitive dependencies!
Group com.github.johanneslichtenberger.sirix
Version 0.1.1
Last update 27. September 2012
Organization not specified
URL https://github.com/JohannesLichtenberger/sirix
License New BSD
Dependencies amount 9
Dependencies je, aspectjrt, slf4j-api, perfidix, xmlunit, logback-classic, guice, gson, guava,
There are maybe transitive dependencies!
maven-glassfishbuild-extension from group org.glassfish.build (version 3.2.2)
GlassFish build depends on properly functioning several custom lifecycle mappings and
artifact handlers. Because these are necessary to resolve dependencies and to run
"gf:run" goal and etc., it is critical that these extensions be made available to
Maven early on during Maven execution.
This definition was originally in maven-glassfish-plugin, which was integrated
into Maven POM through <plugin>/<extensions>true marking, but after
a series of debugging to resolve artifact resolution failure problems, it turns
out that that doesn't cause Maven to load components early enough.
I tried to circumbent the prolem by also registering the maven-glassfish-plugin
as an extension module (via <build>/<extensions/<extension>), but that
apparently confuses Maven to no end --- I get build errors like this:
[INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar': Unable to find the mojo 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar' in the plugin 'org.apache.maven.plugins:maven-jar-plugin'
This is obviously one of the problematic areas of Maven, so to avoid doing hack
over hack, I'm simply moving the component definitions to its own module.
Group: org.glassfish.build Artifact: maven-glassfishbuild-extension
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact maven-glassfishbuild-extension
Group org.glassfish.build
Version 3.2.2
Last update 14. September 2011
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.glassfish.build
Version 3.2.2
Last update 14. September 2011
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
maven-glassfish-extension from group org.glassfish.build (version 10.0-alpha-4)
GlassFish build depends on properly functioning several custom lifecycle mappings and
artifact handlers. Because these are necessary to resolve dependencies and to run
"gf:run" goal and etc., it is critical that these extensions be made available to
Maven early on during Maven execution.
This definition was originally in maven-glassfish-plugin, which was integrated
into Maven POM through <plugin>/<extensions>true marking, but after
a series of debugging to resolve artifact resolution failure problems, it turns
out that that doesn't cause Maven to load components early enough.
I tried to circumbent the prolem by also registering the maven-glassfish-plugin
as an extension module (via <build>/<extensions/<extension>), but that
apparently confuses Maven to no end --- I get build errors like this:
[INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar': Unable to find the mojo 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar' in the plugin 'org.apache.maven.plugins:maven-jar-plugin'
This is obviously one of the problematic areas of Maven, so to avoid doing hack
over hack, I'm simply moving the component definitions to its own module.
0 downloads
Artifact maven-glassfish-extension
Group org.glassfish.build
Version 10.0-alpha-4
Last update 30. April 2008
Organization not specified
URL Not specified
License not specified
Dependencies amount 1
Dependencies maven-core,
There are maybe transitive dependencies!
Group org.glassfish.build
Version 10.0-alpha-4
Last update 30. April 2008
Organization not specified
URL Not specified
License not specified
Dependencies amount 1
Dependencies maven-core,
There are maybe transitive dependencies!
jsgen from group com.github.jochenw (version 1.2)
Jsgen is a Java Source Generation Framework: That means, it should be a valuable tool, if you intend to write a custom generator for Java
sources.
As such, it is the successor of a previous framework, called JaxMeJS (http://jaxme.sourceforge.net/JaxMeJS/docs/index.html).
The predecessor came into being as a standalone project. It was incorporated into the bigger JaxMe project, when the latter
was adopted by the Apache Webservices project. And it was buried as part of the bigger project, when the latter was moved to the
Apache Attic (http://svn.apache.org/repos/asf/webservices/archive/jaxme/).
That was fine for quite some time, because the latest released version (JaxMeJS 0.5.2) did its job quite well.
Over the years, however, the Java language has evolved, and the lack of support for features like Generics, or
Annotations, became a burden. Hence the Successor: Jsgen picks up, where JaxMeJS ended. It is, however, a complete
rewrite with several additional features, that the author considers to be important for modern Java applications:
1. It supports Generics.
2. It supports Annotations.
3. The builder pattern has been adopted. Almost all important classes are implemented as builders.
This should make writing the actual source generators much more concise, and maintainable, than
it used to be before.
4. The code style is configurable. Code styles allow you to concentrate on the actual work.
The resulting Jave source will look nicely formatted, anyways. As of this writing, you
can select between two builtin code styles:
- The default code style is basically the authors personal free style, roughly comparable to the default
code style of the Eclipse Java IDE.
- As an alternative, there is also a Maven code style, which is widely used in the Open Source communities.
Compared to the default style, it is less concise, if not even a bit verbose. On the other hand, it is
widely adopted by projects in the vicinity of {{{https://maven.apache.org}Apache Maven}}.
5. Import lists are created, and sorted, automatically.
Artifact jsgen
Group com.github.jochenw
Version 1.2
Last update 10. November 2019
Organization not specified
URL https://jochenw.github.io/jsgen
License Apache License, Version 2.0
Dependencies amount 1
Dependencies jsr305,
There are maybe transitive dependencies!
Group com.github.jochenw
Version 1.2
Last update 10. November 2019
Organization not specified
URL https://jochenw.github.io/jsgen
License Apache License, Version 2.0
Dependencies amount 1
Dependencies jsr305,
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!
Page 19 from 20 (items total 191)