I'm very excited to announce that Bundlor 1.0.0.RC1 is now available. There have been numerous changes to Bundlor since the M6 release including additions to detection and warning criteria as well as improvements to the ANT and Maven configurations.
This milestone marks feature-complete status for the 1.0.0 release. Baring any major issues, this candidate will be released as 1.0.0.RELEASE shortly.
Detection and Warning Criteria
Bundlor now detects Java types in the following locations:
- Java Types
- Spring Context Files
- Blueprint Service Configuration Files
- Web Application Files
- Contained JARs
- JPA Configuration Files
- Hibernate Configuration Files
- JSP Files
- Log4J Configuration Files
- Static Resources
Bundlor also scans the its generated manifest for the following issues and generates warnings based on them:
- Unlikely Import Version Ranges
- Importing of Exported Packages
- Manifest from Signed JAR
- Imports Unversioned
- Exports Unvesioned
- Missing Bundle-SymbolicName
- Missing Manifest-Version
Standardized and Simplified Configuration
One of the most glaringly bad parts of Bundlor up until the RC1 release was the inconsistency of features and configuration across the various front ends (command-line, ANT, Maven). RC1 has unfortunately had to change the configuration parameters of all of these but the end result is consistency and in many cases simplification of Bundlor's configuration.
Please see the Bundlor documentation for the configuration options for your particular front end.
As stated before, this candidate marks feature-complete status for the 1.0.0 release. I intended to do the final release early in the new year if there are no major issues. I am always on the lookout for new detection and warning criteria so please use the Bundlor JIRA to open new or vote on existing issues.
- Bundlor Adds Support for the Blueprint Service
- Getting Started with Bundlor
- Using Bundlor in Eclipse
- Bundlor Version Expansion and Property Substitution
- Using an OSGi Profile with Bundlor