The caldav4j Maven repository currently resides in trunk, which means that it
is unnecessarily lugged around in every branch and tag.
Consider moving the repository to become a sibling of trunk instead.
Alternatively, an even better solution is to use Sonatype's OSS repository so
that caldav4j is automatically synced with Maven's central repository:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage
+Guide
Original issue reported on code.google.com by markhob...@gmail.com on 17 Feb 2011 at 1:04
Original issue reported on code.google.com by
markhob...@gmail.com
on 17 Feb 2011 at 1:04