As of now the ical4j source code resides in GitHub repositories here:
The reason for migrating the code is the improved support for community contributions via forks and pull requests. We will probably make use of GitHub's issue tracking also, however we will still try to support any patches/bugs submitted in SourceForge. Also note that SourceForge will still be used for release binaries.
iCal4j 1.0.5 is now available for download from SourceForge.net, in addition to the Maven Central Repository. This release includes a number of bug fixes and enhancements; details are available in the commit log here:
If you identify any regression issues with this release please let us know via the forums, bug tracker or other means. Much appreciated.... read more
iCal4j 1.0.2 contains no code changes from 1.0.1, but includes a change to the Maven group id. The new artifact is now available in the Maven Central repository as follows:
As of the ical4j 1.0.1 release, all ical4j projects have been migrated to individual Mercurial repositories.
This migration to a distributed version control system should create a better environment for developing, forking and providing fixes for ical4j projects.
If you have any concerns let me know in the forums.
This release includes a few minor fixes since the 1.0 release as well as updated timezone definitions. You can see the full list of changes here:
This release fixes a compatibility issue with ical4j 1.0.
See the wiki for details on usage:
The latest release of iCal4j is now available. This release includes a number of bug fixes from the past year. The full list is available from the project website:
Many thanks to everyone for their contributions in the form of patches, fixes and bug reports.
The iCal4j extensions project builds on the standard iCalendar object model to provide support for common extension properties and parameters. See the wiki for further details:
The iCal4j Outlook-compatible timezone defintions are now available as a separate artifact. This release will allow you to use different timezones that MAY provide greater compatiblity with certain versions of Outlook.
See the wiki for details:
The third and final release candidate for iCal4j is now available (the next release will be a 1.0 final).
Unfortunately this release breaks a number of conventions for a release candidate, including changes to the API. Please see the clirr report for details:
The major feature inclusion in this release is support for groovy builders making it simpler to construct object models:... read more
The iCal4j Connector provides support for connecting to iCalendar- and vCard-based stores (e.g. CalDAV/CardDAV).
The initial release provides support primarily for CardDAV collections and some basic operations on such collection.
Please provide feedback or report any issues in the forums.
The second release of ical4j-vcard is now available. This release improves compatibility with earlier versions of the vCard specification.
A full list of changes is available in the changelog:
The second "release candidate" of iCal4j is now available.
The major features of this release:
- Introduction of automatic updates of timezone definitions, via the tzurl.org site.
- A change to the timezone used for representing Date instances (now UTC, was previously the local timezone)
I guess some of the principles regarding a release candidate (and even a beta release) have been broken here, by slight changes to the API and the introduction of extra functionality. However I'm confident these changes shouldn't have an adverse impact on the compatibility with previous releases. Do let me know via the forums if they do.... read more
Announcing the first release of iCal4j vCard. This library provides support for the latest draft specification of the vCard standard.
Includes parsing, object model and generation of vCard objects. Note that this may also support earlier versions of vCard, however if you find it does not please provide feedback via the forums.
The first iCal4j release candidate is now available.
The most notable change in this release is the addition of iTIP validation for Calendars and Components. This may impact any iCalendar objects containing the METHOD property.
Note that I have added relaxed validation (enabled using the RELAXED_VALIDATION Compatibility Hint) where I have noticed samples from other CUAs that don't fully conform to iTIP. You may however find examples that I have not yet catered for, so if you experience a validation issue with iCalendar files generated using other CUAs please let me know via the forums:... read more
The fifth and final beta release of iCal4j is now available.
Notable inclusions are support for enabling compatibility flags via properties file, and numerous bug fixes.
Complete changelog information is available at the project site:
The fourth beta release of iCal4j is now available.
Notable inclusions are support for the VVENUE component, adding durations, and various bug fixes.
Complete changelog information is available at the project site:
The third beta release of iCal4j is now available. Notable inclusions in this release are a UID generator to help with creating unique UID properties, and aliases to support deprecated timezone identifiers.
This release also includes a new method: Component.calculateRecurrenceSet(Period), which is used to identify periods defined by recurrence rules specified in a component. This method is now the basis for both VEvent.getConsumedTime() and the PeriodRule filter rule, which should mean more consistent results from both approaches.... read more
The second beta release of iCal4j is now available.
This release includes a number of bug fixes and performance improvements, however it should retain binary compatibility with the previous beta release.
There are some minor API enhancements, which you can see from the following generated report:
For those waiting for 1.0-beta1 to appear in Maven, it appears I have run into a problem with how they like to manage the master repository.
It seems that now you must have proof of ownership of a domain that corresponds to the maven group id, and as I have chosen group id 'net.fortuna' for ical4j, it appears I need to own the domain 'fortuna.net' before I am allowed to upload my releases.
So for now I will be updating the Wiki to show you how to link directly to my repository to get the latest updates, but I won't be uploading to the master repository just yet.... read more
Announcing the first beta release of iCal4j!
This beta includes a large number of bug fixes from the past four months, and marks the beginning of binary compatibility between releases (i.e. the API should no longer change to the extent that it will break existing code).
Note that this is also the first release based on a Maven build process, which means that there are some minor changes with how the releases are packaged (most notably the JAR filenames now include the version number). Hopefully the transition to Maven will be as smooth as possible, but if you have any suggestions on how to improve compatibility with non-Maven environments please let me know.... read more
Release 0.9.20 of iCal4j is now available. This release includes:
- upgrade to commons logging 1.1
- added commons codec dependency for better attachment encoding support
- updated timezone definitions
- more bug fixes
This will potentially be the final alpha release, with most work now focusing on bug fixes.
A new Wiki for iCal4j has now been established at the following address:
Users are encouraged to contribute any information that may be useful for others working with iCal4j.
Release 0.9.19 of iCal4j is now available.
Highlights of this release include:
- improved performance and memory usage
- object filtering and indexing
- additional convenience methods
- various bug fixes and improved implementation of the RFC2445 specification
Any queries, comments, and/or suggestions may be posted to the SourceForge.net discussion forums.
iCal4j 0.9.18 is now available.
This release includes a number of bug fixes, updated timezone definitions, and a change in the default timezone used for processing floating time (now uses the Java default rather than GMT).
As usual, post any comments, queries or concerns to the forums and they will be addressed as soon as possible.