incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Svante Schubert <>
Subject Re: OSGi metadata for ODFDOM
Date Mon, 19 Sep 2011 18:49:19 GMT
Hi Jeremias,

thanks for the quick patch.
Is there any way to check if an OSGi is a valid OSGi? Can we add some
regression test?

Just a quick note on the current sources.

Even before the patch, ODFDOM does not build due to a Javadoc memory
issue. It can be fixed by editing
    /trunk/odfdom/pom.xml (the same file Jeremias edited):

Change the Java version from JDK 5 to JDK 6. We switched to JDK 6 to new
encryption / security features.

Reduce the memory for the JavaDoc plugin and update the version:

After this the build should run smoothly.

The following is redundant and should be removed:
The directory

All .hgeol files

Best regards,

Am 19.09.2011 17:28, schrieb Jeremias Maerki:
> I've chatted with Svante earlier today and we happened to talk briefly about
> OSGi. I'm using ODFDOM in an OSGi system, so I'm interested that the JAR
> includes OSGi metadata from the start. Since the issue tracker isn't
> available, yet, I'm posting my patch here.
> I expect the OSGi part to change slightly as you'll move from
> org.odftoolkit to org.apache but that should be a no-brainer even for
> someone without knowledge about OSGi.
> While doing the change, I noticed that odfdom-jar-with-dependencies.jar
> loses the Manifest data compared to odfdom.jar. That is so even without
> my changes. Please note that the single JAR would need different OSGi
> metadata. It can't just be copied over to the assembly. Well, it
> probably can but it beats the purpose of the assembly since it would
> still look for Xerces outside of it own bundle.
> Jeremias Maerki (ICLA on file)

View raw message