-
That should say:
"The mstor library doesn't explicitly create any *named* threads..".
2009-12-18 23:58:35 UTC in mstor
-
Hi,
The mstor library doesn't explicitly create any threads (Daemon or otherwise), so it could be something in the javamail library itself.
That said, I just tried running one of the unit tests in mstor and I couldn't see any threads named "Spool" or "Expriri" being created. Is it possible that this is caused by another library/framework you are using (e.g. Apache James)?
regards,
ben.
2009-12-18 23:56:24 UTC in mstor
-
Hi Michael,
My apologies, I didn't notice your question (I think the sourceforge email notification of forum posts has become particularly flakey recently..)
As noted by Alex, I think most of the changes in the new RFC shouldn't have a huge impact on ical4j, but I will definitely make (and accept) any changes required to support the new standard.
I can't provide a specific timeline for...
2009-12-14 22:33:26 UTC in iCal4j
-
Hi Patrik,
I don't have any experience with Nexus, but I would think that you should try adding the modularity repositories to your maven settings.xml (assuming Nexus will use those settings).
I'm not aware of anything special required in the repository structure to support this.
regards,
ben.
2009-12-13 09:05:25 UTC in iCal4j
-
Hi maya,
As Ken suggested, it looks like the JTDS library isn't compatible with Java versions prior to Java 5.
Also note that I've just removed references to Integer.valueOf(int) from most of the unit tests, with the only remaining reference in a test that uses regex anyway (Java 5 only).
regards,
ben.
2009-12-13 09:02:30 UTC in iCal4j
-
fortuna committed patchset 1136 of module iCal4j to the iCal4j CVS repository, changing 4 files.
2009-12-13 08:55:26 UTC in iCal4j
-
Hi,
This error usually means the file doesn't use the correct line terminators (i.e. CRLF). You can try some compatibility hints to work around this (i.e. relaxed parsing, relaxed unfolding, etc):
http://wiki.modularity.net.au/ical4j/index.php?title=Compatibility
regards,
ben.
2009-12-08 09:48:42 UTC in iCal4j
-
fortuna committed patchset 135 of module ical4j-connector to the iCal4j CVS repository, changing 2 files.
2009-12-05 05:55:14 UTC in iCal4j
-
Hi,
I'm pretty sure this exception is caused by a bug that was fixed in beta5, for handling recurrences on anniversary-style dates (i.e. events with no end date or duration).
If you can't upgrade to the latest iCal4j your best option would be to add a DTEND or DURATION property to your events.
regards,
ben
ps. I suspect your example probably shouldn't validate anyway, as you are...
2009-12-05 02:34:12 UTC in iCal4j
-
fortuna committed patchset 1135 of module iCal4j to the iCal4j CVS repository, changing 1 files.
2009-11-28 03:22:22 UTC in iCal4j
