BibSonomy ::  user :: gresch ::

gnizr™ (gə-nīzər) is an open source application for social bookmarking and web mashup. It is easy to use gnizr to create a personalized del.icio.us-like portal for a group of friends and colleagues to store, classify and share information, and to mash-it-up with information about location. It's free.

Spring out of the box provides little support for loading property attributes based on environments and/or server contexts. Many projects work around this by creating custom ant builds. With Configleon you can build one war file that can be deployed to every location. Configleon really shines is in it's ability to cascade the property attributes. This allows the common attributes to be defined in a global file and then overridden at the environment and server context. If we consider the development of a web application, it typically starts in a local environment. The application will then be deployed to various environments including dev, qa, test, and production. Within a given environment, you may be deploying the same application to different server contexts. For example, say we are deploying the JMesa example web application to the test environment. But we also have two different versions of the application. One is deployed to mycompany.com/jmesa and the other is deployed to mycompany.com/jmesa2. In this example that same war file can use different properties based on both environment and context. In this example, the environment is test and the server context is jmesa and jmesa2.

Although computers have transformed how we listen to, obtain, compose, and notate music, they have not fundamentally changed how we research and analyze music. Though many computer databases have been created for musicology, they are not well adapted for sophisticated music queries. For instance, melodies can be found if exact matches exist. But melodic variations such as the repetition of a phrase or a change in embellishment are extremely common, yet cause searches to fail. More complex investigations, such as finding all melodies that imply a particular underlying harmony, can barely begin to be created with existing software packages. The lack of relevant software for analyzing music hampers scientific attempts to understand what we listen for and how we process what we hear; these activities are little understood despite music’s nearly universal presence in our daily lives. The music21 project at M.I.T. will give to the music community the set of tools it needs to conduct sophisticated musical and statistical analysis using modern programming techniques. The software framework, written in Python, manipulates music as a collection of symbolic data, such as pitch names and note durations, that can then be classified as higher level musical structures according to the style, region, or period being studied. Music21 focuses specifically on the manipulation of symbolic music data: it leaves to the many preexisting open-source and proprietary software packages the notation and audio playback of scores (the two areas where computer-aided music research is most developed). By focusing on the points of greatest need to musicology, the framework will give rapid results within a short timeframe.

Jetlang provides a high performance java threading library. The library is based upon Retlang. The library is a complement to the java.util.concurrent package introduced in 1.5 and should be used for message based concurrency similar to event based actors in Scala. The library does not provide remote messaging capabilities. It is designed specifically for high performance in-memory messaging. Features¶ * All messages to a particular Fiber are delivered sequentially. Components can easily keep state without synchronizing data access or worrying about thread races. * Single Fiber interface that can be backed by a dedicated thread or a thread pool. * Supports single or multiple subscribers for messages. * Subscriptions for single events or event batching * Single or recurring event scheduling * High performance design optimized for low latency and high scalability * Publishing is thread safe, allowing easy integration with other threading models. * Low Lock Contention - Minimizing lock contention is critical for performance. Other concurrency solutions are limited by a single lock typically on a central thread pool or message queue. Jetlang is optimized for low lock contention. Without a central bottleneck, performance easily scales to the needs of the application. * Powerful Async Request/Reply Support * Single jar with no dependencies except the jdk (1.6+) * Integrates with any JVM language - jruby, scala, clojure, groovy, etc

We are attempting to build a scala compiler plugin to auto-generate avro classes based on some simple definitions. This plugin is for the Scala 2.8 compiler, and for the Avro 1.3.0 runtime.

Eclipse Plug-in for tailing log files and eclipse consoles (e.g. SVN, Java Stack Trace, CDT), including syntax coloring with either a regular expression or a word match. It allows you to have multiple logs open concurrently.

Gerrit is a web based code review system, facilitating online code reviews for projects using the Git version control system. Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer. Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer. This functionality enables a more centralized usage of Git.

So what can you do with Rietveld? The basic workflow is: 1. Developer makes some changes in their Subversion workspace. 2. Developer uploads a patch in the form of svn diff output to Rietveld, using a small script named upload.py. This creates a new issue for them on the Rietveld website. 3. Developer goes to the issue that was just created on the Rietveld site, adds the email addresses of one or more reviewers, and causes Rietveld to send an email to the reviewer(s). 4. Reviewer navigates to the issue on the Rietveld site, browses the side-by-side diffs linked from there. A side-by-side diff shows the old and new version of the source code side by side, with deleted text on the left marked with a light red background, and inserted text on the right marked with a light green background. (Two different shades of red and green each are used, to highlight the differences at a finer-grain level than blocks of lines. This helps find one-character changes and clarifies diffs that just reflow a lot of text.) 5. Reviewer inserts inline comments directly into the side-by-side diffs, by double-clicking lines on which they want to comment. Inline comments are initially created in draft mode, which means that only the comment author can see (and edit) them. 6. Reviewer publishes comments, making them visible to everyone else, and sending an email to the developer (and to other reviewers) summarizing the inline comments with a little bit of context. At this point, the developer can reply to inline comments directly on the Rietveld website using exactly the same mechanism as used by the reviewer. Replies simply become additional inline draft comments. The developer can also revise their code and upload a new version of the patch. The new version is attached to the same issue, and reviewers can choose to view the diffs afresh, or view the delta between the new and the old version of the patch. The latter feature is particularly helpful for large code reviews that require several iterations to reach agreement between developer and reviewer: the reviewer doesn't have to re-review stuff that didn't change between revisions and was already approved.

ProtoJ is a pure java build, installation and deployment library that hands control over to you. There's no third-party ProtoJ application directory to maintain, no environment variables to set up and absolutely no other required software. Simply add the ProtoJ library to your project and get ready to experience the joy of a friction-free development cycle. So why not give ProtoJ a try right now, it really is as easy as 1-2-3: 1. Download the ProtoJ executable jar file. 2. Create a new "basic" project by executing java -jar protoj-exe-jdk5-1.9.2.jar -sample basic. 3. Try a few commands from the basic/bin directory: ./basic.sh compile archive hello-basic. When you're feeling more adventurous take a look at the jboss demonstration that demonstrates how ProtoJ can be used to build, store persistent configurations and launch a jboss project with considerable ease. You may be amazed at how easy this is to accomplish: not because ProtoJ is rocket science, but because it is based on java rather than xml. Features to Enhance Any Project ProtoJ abandons build scripts. It's "unique selling point" is that all use-cases are accessible in-code through the api, with just one call to Java in just one starter script! If you ever wished you could get rid of your build scripts then look no further: ProtoJ is targeted at you!!! ProtoJ is part of your project. You don't have to hide away use-cases related to the build inside some xml file, to be handled by some other tool merely at the start of your project life-cycle. Compilation and jar creation for example belong to your project just as much as your core business use-cases and are accessible at build-time through to run-time. ProtoJ plays nicely with maven. ProtoJ uses a traditional lib directory and support for filling it up from a maven repository is provided right out of the box. And going in the other direction, you can easily deploy your project artifacts to a maven repository so that they can be shared with other ivy or maven projects. Or indeed with other ProtoJ projects! ProtoJ plays nicely with aspectj. Aspectj compiler support can be enabled with just a single method call, as can support for load-time-weaving. Then just drop your .aj files alongside your .java files and they will be picked up by the ajc compiler without any additional aspectj installation. ProtoJ is available on all major platforms. Each release of ProtoJ is subjected to rigorous testing on Linux (Ubuntu), Unix (Mac OS X) and Windows (XP) and also on Java 5 and Java 6. If you work with any other platform then you can easily check for compatibility by following the instructions in the BuildingFromSource page.

Jazzmaster is an application framework developed by Eiichiro Uchiumi (Eiichiro.org) and can be performed on JDK 5 or later Java platform. Using Jazzmaster framework, you can construct the application from the small one which is processed on a command line to the large one like enterprise application on the paradigm of SOA (Service-Oriented Architecture). The application which is built by composing the immediately-modularized services on the Jazzmaster framework certainly improves the flexibility of changeability and the development agility, according to becoming if the scale grows. Jazzmaster is composed of the following modules: * Core * AspectJ integration

Scalaris is a scalable, transactional, distributed key-value store. It can be used for building scalable Web 2.0 services. Scalaris uses a structured overlay with a non-blocking Paxos commit protocol for transaction processing with strong consistency over replicas. Scalaris is implemented in Erlang.

Usemon is a monitoring system for usage trends, response time and dependency analysis of plain Java applications or big multi-clustered Java Enterprise applications running in production. The proof of Usemon's stability and usefulness is confirmed by the fact that one of the worlds largest telecom operators is running Usemon in a clustered WebSphere environment with over 90 enterprise applications.

Impala 1.0M5 introduces a number of API and configuration improvements, making the framework easier to configure and extend, and usable in a wider range of environments. Following 1.0M5, only minor changes in internal APIs are now expected prior to the 1.0 final release. The 1.0M5 release makes it much easier to configure Impala-based applications by supporting a property-based configuration. While Impala is still very heavily based on the Spring framework, 1.0M5 now also makes it possible to plug in other runtime frameworks into Impala's dynamic module loading mechanism. The full list of issues for milestone 1.0M5 is here: http://code.google.com/p/impala/issues/list?q=label:Milestone-Release1.0M5&can=1. Note that there are a number of package name and configuration changes in this release. If you are upgrading from an earlier release, you will probably wish to check the backward incompatible changes for 1.0M5 and an example migration sequence for this release. If you're interested in getting involved in the Impala project, please take a look at this page: http://code.google.com/p/impala/wiki/GetInvolved.

The Firewater Framework lets you create sophisticated REST based web APIs for your Java and Flash/Flex based web applications. Features include: * Spring based declarative architecture (zero code web services) * extensible framework * supports GET, PUT, POST, OPTIONS and DELETE HTTP methods and matches incoming URL patterns * supports JDBC back-ends with templated SQL mappings * supports secured web services using Acegi Spring Security * supports paging, full-text search, sorting and filtering * flexible cacheing strategy based on OSCache * custom Spring schema for easy configuration