OpenNTF Javascript Aggregator project
Java JavaScript Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
jaggr-assembly
jaggr-blueprint
jaggr-core
jaggr-sample-dojo
jaggr-sample
jaggr-service
src/site
.gitignore
.project
KEYS
LICENSE
NOTICE
README.md
pom.xml

README.md

Build Status

The JavaScript Aggregator is an OSGi servlet that provides aggregation and code minification services to AMDs loaders that supports the loader extension API. Features include:

  • JavaScript minification using the Google Closure compiler
  • Code trimming using has.js feature detection
  • Require list expansion to reduce the cascade of requests resulting from dependency discovery as modules are loaded on the client
  • CSS Optimizations
  • i18n resource consolidation
  • Caching of previously built/minified output for quicker response on subsequent requests

The Aggregator supports the Eclipse plugin extension architecture to allow the addition of support for:

  • New types of resource repository locations on the server
  • New types of module builders/minifiers
  • New AMD loaders

See the wiki for more details.

###OPENNTF### This project is an OpenNTF project, and is available under the Apache License V2.0. All other aspects of the project, including contributions, defect reports, discussions, feature requests and reviews are subject to the OpenNTF Terms of Use.

###HELP### For help with this project, please visit the discussion forum or ask a question on Stack Overflow with the tag jaggr. Remember to check the wiki.

###UPGRADING###

####1.3.0#### Major changes since 1.2 can be found at [What's new in Version 1.3] (https://github.com/OpenNTF/JavascriptAggregator/wiki/What%27s-new-in-Version-1.3).

There are some interface changes affecting resource factories. See the above link for details. Some extensions may need to be updated and re-compiled in order to
run using the new interfaces.

####1.2.0#### This is a major upgrade. Read what it brings.

We've created a new bundle, jaggr-core, to house all non-osgi specific code. This is now where the vast majority of jaggr code is located. Bundle dependencies may need to be updated.

Besides the name changes, there are some interface changes affecting aggregator extensions. Extensions developed for previous versions of the aggregator won't run on 1.2 without changes.

Developers running from within eclipse should use a java7 jre/jdk for development and running the bundles out of the eclipse workspace. Maven will generate java6 compatible jars from the command line.

####1.1.8#### The changes described below don't affect casual users. Only implementors of JAGGR extensions that deal with calculation of expanded dependencies are affected:

  • com.ibm.jaggr.service.deps.IDependencies.getExpandedDependencies() has been removed. Use com.ibm.jaggr.service.util.DependencyList instead.
  • com.ibm.jaggr.service.util.DependencyList constructor arguments have changed.

####1.1.1####

  • Resources defined in the server-side amd config file that use a "namedbundleresource" scheme url should leave the authority section of the uri blank and have the bundle name be the first segment in the path. (ex: namedbundleresource:///bundle.name/path/to/file)
  • Interface change in IResource (added IResource resolve(String relative);) will affect any third-party resource providers.