Simon Spero

Nods (former sunsite/iBiblio employee from back in the day). Will run the extract and do a PR when the database server and swap drives forgive me :) I will try...

Based on what I'm observing, in the OSGI case, the modularity and module metadata seems to be better when the metadata is assembled by the build tool, from source code...

There are some mistakes in some of the comments above, (which supports the issue title). ``` :Library rdfs:subClassOf [ a owl:Restriction ; owl:allValuesFrom :Book ; owl:onProperty :holds ] ; ```...

It's difficult to generalize, since the packageinfo files have to be put in with the source code. Since a export header parameter with an explicit version overrides packageinfo and annotations,...

The packageinfo files are in the source tree because they're source files, and provide metadata for the package. You can also use a package annotation on package-info.java, which puts a...

A key point is that these files that are not modified for each release. They are only changed when the package version changes, which only happens when the API changes...

There is a troublesome problem in the data (the character codes are not legal MARC-8, and cannot be represented in XML (even when escaped). Since one of the bogus characters...

This seems to be dependent on the Sax Provider being used. For the provider in java 1.6, setting the attribute does not cause duplication. Removing the lines setting the attribute...

Can this issue now be closed?

I don't see the issue listed - do you know what issue # it is? Simon On Wed, Feb 27, 2013 at 5:33 PM, gypsyjoe [email protected] wrote: > Yes. But...